Supporting DevOps the Smart Way by Melissa Tondi
0 likes137 views
The summary discusses improving quality engineering practices by defining the quality engineering role, re-tuning automation, shifting traditional quality engineering tasks earlier in the development process, re-defining refinement, and updating the definition of "done". Some key points include defining the quality engineering mindset, taking a tiered testing approach with multiple stages of automation and testing, focusing on regression testing throughout development instead of just at the end, and ensuring automation is integrated into the pipeline to make the product shippable. The goal is to improve efficiency, innovation, and culture through a collaborative team approach.
Supporting DevOps the Smart Way by Melissa Tondi
- 2. ● I’m devoted to the Quality (with a capital Q) of the SDLC ● My experience is in the QA/QE and agile spaces ● I spent my career focusing on three tenets: efficiency, innovation, and culture ○ QE and DevOps play nicely with all three!
- 3. ● Defining the QE role ● Re-tuning automation ● Shifting traditional QE/QA right tasks to the left ● Re-defining refining ● Making it shippable What is DevOps? “The collapse and automation of the software delivery supply chain” - Anne Hungate’s reference!
- 4. ● Like DevOps, it’s a Mindset ○ ...even if you’re QA you can still be QE ● Balances technical acumen with user advocacy ○ ...with equal emphasis on both ● Influential throughout the SDLC
- 5. What It Has Been: ● Monolithic ● Focused on everything ● A numbers game What It Should Be: ● Tiered approach ● Multiple runs for multiple dones ● Provides the most valuable information ASAP ● AoA (Automated of Automatable)
- 6. Wrong Tasks: ● Regression at the end ● Automation at “sprint +n” ● Non-automated, scripted testing first ● Redundancy Right Tasks: ● Regression throughout with Dev ○ Share those runs! ● Automation = Shippable ● Unscripted testing first… because ● TDD mindset ○ Share those tests! ● And Dev… ○ Read those tests!
- 7. Old School Refinement: ● The entire project team + lurkers ● … in a room ● Cramming as many stories as possible in one hour New School Refinement: ● Small working groups ● Shorter times ● Everyone represented … yes, even DevOps ● Tiered approach
- 8. Old Definition of “Done”: ● Used to be owned by Product - and focused on the acceptance of User Stories New Definition of “Done”: ● Each practice in the agile team is represented ● Shares their playbook ● Removes guesswork ● Remove silos of Dev, QA, PM, and DevOps
- 9. Make it Shippable ✅ Tech debt is addressed ✅ Automation is green and in the pipeline ✅ Sev 1/2 bugs are closed ✅ All P1/2 tests cases have been passed
- 10. Final thoughts: ● Just because you can, doesn’t mean you should ● Just because you could, might not mean you did
- 11. ➔ Define the QE role ➔ Re-tune automation ➔ Shift left to focus on the right ➔ Re-define refining ➔ Get to a new definition of “done”