Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the...
Transcript of Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the...
![Page 1: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/1.jpg)
The Software Delivery Experts
Agile, DevOps & QA Conference
![Page 2: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/2.jpg)
A Tester’s Guide to Collaborating with Product
Owners
The Software Delivery Experts
Bob Galen Director of Agile Practices
![Page 3: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/3.jpg)
Introduction
1. Bridge stories
2. Help write Acceptance Tests
3. DoD accountability
4. Be the customer
5. Ask questions
6. Cost of quality
7. Cost of testing
8. Backlog as a plan
9. Take the PO to lunch
Outline – Myths & Realities
![Page 4: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/4.jpg)
Who owns the Backlog?
Simple pattern:
The Product Owner Owns the Product
Backlog
Essential pattern
It Takes a Village to Own the Backlog
![Page 5: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/5.jpg)
1. Product Manager
• Product Roadmap, Collateral, Business Case / ROI
• Driving customer value
2. Project Manager
• Product Backlog (WBS)
• Grooming & look-ahead
• Velocity-based, Release Planning
• Goal setting, Budget
3. Leader
• Trade-offs, product balance
• Stakeholder “management”
• Member of the team; partner with the ScrumMaster
4. Business Analyst
• Story Writing
• Acceptance
• Emergence; Spikes
4 Quadrants of Product Ownership
![Page 6: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/6.jpg)
Ø The key here is guiding the translation and execution of the user story
• Pull the Product Owner into the sprint
• Show incremental code
• Shepherd sign-off
Ø 3 Amigos-based interactions
Ø Nail the Demo
1. Bridge stories from Team to the Product Owner
![Page 7: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/7.jpg)
Ø Coined by George Dinwiddie
Ø Swarming around the User Story by:
• Developer(s)
• Tester(s)
• Product Owner
Ø During “Grooming, Sprint Execution, Until…“Done”
Ø Similar to Ken Pugh’s Triad
1. Bridge stories from Team to the Product Owner
![Page 8: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/8.jpg)
Ø Consider them
• As “mini-contracts” or “mini-UAT”
Ø 3-5 minimal per story
Ø Business constraints
Ø Functional and non-functional
Ø Edge and error cases
Ø Provide hints:
• Design & Tests
2. Help Write Solid Acceptance Tests
![Page 9: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/9.jpg)
2. Help Write Solid Acceptance Tests
![Page 10: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/10.jpg)
Ø It all starts in the Grooming, thinking of the work cross-functionality and with DoD in mind
Ø Continue it in Sprint Planning
Ø Execute consistently; no exceptions
Ø Deliver to “Done”
3. Hold everyone “accountable” to Definition of Done
![Page 11: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/11.jpg)
4-Levels of Criteria
![Page 12: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/12.jpg)
ü The story is well-written: and has a minimum of 5 Acceptance Tests defined
ü The story has been sized to fit the teams velocity & sprint length: 1-13 points
ü The team has vetted the story in several grooming sessions-it’s scope & nature is well understood
ü The story is not “too complete,” around ~70% complete
ü The team understands how to approach the testing of the stories’ functional and non-functional aspects
ü Any dependencies to other stories and/or teams have been “connected” so that the story is synchronized and deliverable
ü The story aligns with the Sprints’ Goal and is end-to-end demonstrable
ü If a “Technical Story” the story has a “Technical PO” to provide guidance and sign-off
Ready-Ready
Prevents teams from taking on
stories that are ill
groomed or defined
Increases
sprint success
![Page 13: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/13.jpg)
Ø Don’t solve “requirements”…solve “customer problems”
Ø Consider usage
Ø KISS
Ø Deliver value; highest impact & priority
Ø End-to-end solutions
4. Represent the Customer
![Page 14: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/14.jpg)
Ø The power of a Minimal Marketable Feature
Ø The power of the Persona
Ø Observe the Customer
Ø Nordstrom Innovation Lab: http://www.youtube.com/watch?v=szr0ezLyQHY
4. Represent the Customer
![Page 15: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/15.jpg)
Ø Ask questions
• Relentlessly, Constantly, Courageously
Ø 5 – Whys
Ø Business value?
Ø Lean investment
• Just enough and just-in-time
Ø Trust your instincts, craft
Ø Does it make sense?
5. Ask questions? Be inquisitive, be curious, explore!
![Page 16: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/16.jpg)
5. Ask questions? Be inquisitive?
![Page 17: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/17.jpg)
Ø Meta-requirements
• Security, Performance, Maintainability
Ø Automation investments
• Agile Automation Triangle
Ø Inspections – pairing
Ø DoD maturity
Ø Avoid rework?
• Yes for product, no for experiments
6. What about the Cost of Quality?
Quality is a TEAM responsibility!
![Page 18: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/18.jpg)
Things to do…
• Features
• Value increments
• Architecture
• Design
• Process
• Quality
• Testing
In a Context-Based fashion…
A Tapestry that Includes Threads for...
• Deployment
• Regulatory
• Dependency
• Risk
• Feedback
• Customer timing
• Tempo
…Guiding us towards customer value
![Page 19: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/19.jpg)
• Risk-based
• Always test what’s available
• Don’t track coverage or time
• Slack time for thinking & creativity
• Balanced across the quadrants
7. What about the Cost of Testing?
![Page 20: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/20.jpg)
Development & Test Automation
• Pyramid-based Strategy: (Unit + Cucumber + Selenium)
• Continuous Integration
• Attack technical infrastructure in the Backlog
• Visual Feedback – Dashboards
• Actively practice ATDD and BDD
3 Pillars of Agile Quality
Software Testing
• Risk-based testing: Functional & Non-Functional
• Test planning @ Release & Sprint levels
• Exploratory Testing
• Visual Feedback – Dashboards
• Standards – Checklists, templates, repositories
• Balance across manual, exploratory & automation
Cross-Functional Team Practices
• Team-based Pairing
• Stop-the-Line Mindset
• Code Reviews & Standards
• Active Done-Ness
• Aggressive Refactoring of Technical Debt
• User Stories, “3 Amigo” based Conversations
• Whole Team Ownership of “Quality” • Building it ‘Right’; Building the ‘Right’ Thing • Healthy – Agile Centric Metrics
• Center of Excellence or Community of Practice • Strategic balance across 3 Pillars: Assessments,
Recalibration, and Continuous Improvement
![Page 21: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/21.jpg)
• Ask for and define a Release Train
• Encourage Planning
• Establish “hardening” activities
• Integration milestones – working code
8. The Backlog is a “Plan” help focus it towards Release!
![Page 22: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/22.jpg)
Ø Iterative model with a release target
• Product centric • Focused on a production push/release
Ø Synchronized Sprints across teams
• Some teams are unsynchronized, but leads to less efficient cross-team (product) interactions
Ø Continuous Integration is the glue
• Including automated unit and feature tests; partial regression
Ø Notion of a “Hardening Sprint”
• Focused more on integration & Regression testing
• Assumption that it’s mostly automated
• Environment promotion
Ø Define a final Hardening Sprint where the product is readied for release
• Documentation, Support, Compliance, UAT, Training
Release Train Management
![Page 23: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/23.jpg)
• Have lunch
• Discuss the competitive landscape, the Market
• Customer challenges
• MoSCoW in operation
• Commitments & Pressure
• Vision & Mission; what does “success” look like?
9. Get to know your Product Owner
![Page 24: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/24.jpg)
Helping the Product Owner to build the “Right Thing”
And
Helping the Team to build “Things Right”
10. Wrapping up...
![Page 25: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/25.jpg)
Ø Final questions or discussion?
Thank you!
Questions?
![Page 26: Agile, DevOps & QA Conference · ü The team understands how to approach the testing of the stories’ functional and non-functional aspects ü Any dependencies to other stories and/or](https://reader036.fdocuments.us/reader036/viewer/2022062506/5f22c6c00055a2292a047e64/html5/thumbnails/26.jpg)
Zenergy Technologies | 336.245.4729 | Zenergytechnologies.com | [email protected]
Bob Galen [email protected]
@bobgalen
Contact Info