A QE unit interview with Lalitkumar Bhamare on aligning actors for a Quality Conscious Software Delivery https://qeunit.com Subscribe to don’t miss any new Quality Engineering content 🔔 Delivery software at the high standard is hard. Companies have to both accelerate their rate and quality of software delivery to remain competitive and develop valuable digital offerings. Quality Engineering is the paradigm to enable companies to respond to these challenges, constraining the overall system to Quality requirements. In this interview, we step back for the big picture of software quality and testing. From his industry experience, Lalitkumar shares a SWOT on Software Quality and a methodology he has built over the years to deliver faster and with quality, “Quality-Conscious Software Delivery” (QCSD). #qualityengineering #qe #quality #qa #testing 00:15 Podcast introduction with Lalitkumar Bhamare 02:00 The main typology of problems face with Quality 05:00 The strengths and weaknesses of Software Quality and Testing 09:00 The opportunities to implement Quality Consciousness 10:24 The threats for the evolution of Quality in organizations 12:40 The valuable practices for Quality 15:00 The Key Takeaway 16:00 Feedback on the Quality Engineering Definition 19:00 Concluding points and references Join the QE Unit to access exclusive and regular content from the community. About Lalitkumar Bhamare Lalit spent 3 years with Barclays Investment Bank as Sr. Test Analyst and led their L&D CoP (for testing), primarily responsible for rolling out the latest testing practices in Barclays, as part of Innov8 (an organization-wide program). Under the TCS-Cisco relationship, he has also worked as founder and director of Technology Excellence Group for Testers. He has worked as a consultant on demand for various project teams across Barclays group, especially to implement CDT in testing projects, along with other things. Lalit thinks that his connection with the global testing community & his volunteer experiences help him contribute back to the organizations he works for. That has helped him to contribute to building an intellectual testing culture at his workplace. He is a skilled Tester, Test Manager, Trainer, Coach and Consultant on demand, all packed in one profile. His creative talent (which reflects his activities) is an additional skill that helps him effectively communicate ideas. You can follow him on twitter @Lalitbhamare and Linkedin. References Daniel Terhorst-North, We need to talk about Testing, https://dannorth.net/2021/07/26/we-need-to-talk-about-testing/ Quality Conscious Software Delivery (QCSD), https://www.talesoftesting.com/qcsd.html. Tales of Testing. Tea time with Testers https://www.teatimewithtesters.com/ State of Testing Report 2021, https://www.infoq.com/articles/2021-state-testing-report/. InfoQ. The Association for Software Testing https://associationforsoftwaretesting.org

A solo episode presenting the concept of Tipping Point and its application in Quality Engineering practices https://qeunit.com Subscribe to follow the next episodes 🔔 Transforming a business towards the creation of continuous value is a considerable effort of organizational change. Quality Engineering is based on practices maximizing results and minimizing effort, meeting the definition of quality. The Tipping Point is a key concept in the management of change. This inflection point is an inflection point that we seek to achieve in transformation towards Quality Engineering. In this video, we share the definition of Tipping Point, exploring examples, the concept, and possible parallels to QE. We end by identifying practices that can be acted upon in your context. #qualityengineering #qe #change #engineering #software 00:00 Introduction and examples of Tipping Point 01:00 The definition of Tipping Point 02:00 Concept and parallel with the QE of Tipping Point 04:40 Tipping point and Quality Engineering 06:40 When is the Tipping Point reached? 07:35 Pointers for more about the Tipping Point Content mentioned Malcolm Gladwell (2002), The Tipping Point: How the Little Things Can Make a Big Difference. Little Brown. Antoine Craske, How to Reach the Tipping Point of Quality Engineering. QE unit. Join the QE Unit community at https://qeunit.com

A QE unit interview with João Proença on defining Quality Engineering from his industry experience https://qeunit.com Subscribe to the channel to get new Quality Engineering content 🔔 What is Quality Engineering? That question raises others like the why, the what, the how. We covered these during a deep dive into Quality Engineering with João Proença. #qualityengineering #qe #quality #moderntesting #testing 00:15 Podcast introduction with João Proença 05:00 Industry experience and challenging of hypergrowth 11:00 What is your definition of Quality Engineering? 15:00 How Quality Engineering is different, what is its added-value? 21:00 Which roles and organizations for Quality Engineering? 25:00 Measurement and metrics in Quality Engineering 30:00 The need for Quality Engineering in the current ecosystem 35:00 How can organization adopt Quality Engineering 40:00 Takeaways, concluding points and inspiring references Join the QE Unit to access exclusive and regular content from the community. About João Proença João Proença comes from Lisbon, Portugal, and is the Principal Quality Engineer in R&D for OutSystems, a company that provides one of the leading low-code development platforms in the world. He has assumed various roles throughout his career in the past 11 years, including quality assurance, development, customer support, and marketing. Finding innovative solutions for complex problems drives him the most, so he is always eager to talk about how professionals are overcoming testing challenges around the world. Outside of IT, João is passionate about songwriting, movies, and football. You’ll see him tweet about all of these topics using the @jrosaproenca handle. References You can find all the reference on the transcript on the QE Unit Website.

A solo episode dedicated to quality negotiation for software projects in the QE Unit https://qeunit.com Subscribe to get the next episodes 🔔 This project is complicated: aggressive dates, multiple rework, and hours that accumulate. We would have liked to be more efficient between our results and our efforts, part of the definition of quality. We can even imagine thinking: “with 30% of the project budget allocated to quality, it would be much easier; a better definition of the requirements, tests giving us rapid upstream feedback”. The reality is far from it. It is not enough to arbitrarily allocate time, especially since business constraints do not allow it. “How to negotiate a project budget allocated to Quality?” was the theme of our round table suggested by Arnaud. The title leaves clues as to practices to put in place. If they seem far from the pure negotiation of a quality budget to you, it is normal; this is not the first subject to address. #qualityengineering #qe #qa #qualityassurance #qualitynegotiation #softwarequality 00:00 Introduction and why hope is not a strategy 02:00 Why have to negotiate? Why negotiate a quality budget? 04:10 Prepare a negotiation upstream of collaborative workshops 05:20 Understand and map the stakeholders 06:30 Align the stakeholders around common interests 08:15 Define the measures of value to be followed in the iterations 09:10 What to do when the negotiation seems closed? 13:10 The negotiation mistakes to avoid 15:15 Negotiation requires understanding, diagnosis and strategy Join the QE Unit at https://qeunit.com

A solo episode dedicated to the decryption, articulation and impact of organizational debt, or OrgDebt, in the QE Unit https://qeunit.com Subscribe to follow the next episodes 🔔 Building software with technical debt is painful. Every change is becoming slower due to the accumulated waste and complexity - until the organization becomes unable to evolve the software. When hitting a wall, organizations destroy the house they have been paying for the last years. They usually start another software effort from zero, transforming the initial investment into an entire waste of money. Technical debt is a widely known concept in engineering. It represents the iceberg of issues organizations accumulate over time from their implementation decisions. Achieving Quality Engineering revolves around the 5 pillars of MAMOS: Methods, Architecture, Management, Organization and Skills. Debt is everywhere, and OrgDebt is a fundamental entropy to contain within Management, Organization and Skills. In this episode, we cover first OrgDebt to then identify how to detect and to prevent it leveraging Quality Engineering: Organizational Debt is more than the sum of shortcuts Lack of shared mission and purpose dispersing the effort Lack of alignment with the overall system is waste Lack of valuable interactions will make you miss the point Lack of necessary capabilities and skills will slow you down Lack of value creation will make the organization hit a wall #qualityengineering #qe #organization #orgdesign #debt #techdebt #orgdebt 00:00 Introduction 01:10 The definition of OrgDebt: organizational debt 02:52 Methods: Debt Methodologies 03:47 Management: Mission, purpose and alignment debt 06:57 Organization: The lack of interactions 08:10 Skills: Lack of skills 09:25 The impact is sooner or later to yell at a wall 11:10 Quality Engineering leaders must act Content mentioned MAMOS, The Quality Engineering Framework, QE Unit, Antoine Craske. Join the community at https://qeunit.com

Hello and welcome to the Quality Engineering (QE) podcast! This episode shares the thinking that led me to create this podcast and the Quality Engineering Unit community, The goal is to share the key concepts that will be shared, media and formats involved, The next episodes will be content dedicated to the theme, Since your feedback is important in adapting the content, please feel free to leave me a rating, comments or contact me directly, Following the podcast will also give me leads of interest, thanks in advance! Good listening, Antoine Craske