Download as PDF, PPTX
Get into bed with qa and keep testing agile
- 1. Get into bedwith QA (and keep testing agile) simply brilliant thinkers making software brilliantly simple
- 2.
- 3. Why am Ihere today?
- 4.
- 5.
- 6.
- 7. - The productwill have problems - The testing will be late - Changes will be more expensive
- 8.
- 9.
- 10.
- 11.
- 12. Individuals and interactionsover processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 13.
- 14.
- 15.
- 16.
- 17. - INDIVIDUALS - INTERACTIONS -COLLABORATION
- 18. - INDIVIDUALS - INTERACTIONS -COLLABORATION
- 19.
- 20.
- 21.
- 22.
- 23. Let’s decide... ● Atwhat points will we all come together? ● How are we going to maintain collaboration?
- 24.
- 25. At what pointswill we all come together going forward? > Daily standups
- 26. At what pointswill we all come together? > Standups ● What did you do yesterday? ● What are you doing today? ● Any blockers in your way?
- 27. At what pointswill we all come together? > Daily standups > Ticket kick offs!
- 28. At what pointswill we all come together? > Ticket kickoffs 1. What is the change? 2. Do we have acceptance criteria? 3. Is the ticket complete? Aka does the ticket have all the relevant information for development and testing to begin work? 4. Will automated/manual test scripts be completed as a part of the work? 5. Have we made any assumptions? 6. Do we need any more detail from the client? 7. Are you comfortable enough in your understanding of the area to start working on the ticket or is a handover required?
- 29. At what pointswill we all come together? > Daily standups > Ticket kick offs! > Storytime
- 30. At what pointswill we all come together? > Storytime “Introducing the Three Amigos” - Ryan Thomas Hewitt
- 31. At what pointswill we all come together? > Storytime Business analysts: Requirements Acceptance criteria Developers: Code Unit tests QA: Scenarios Test cases
- 32. Let’s decide... ● Atwhat points will we all come together? ● How are we going to maintain collaboration?
- 33. How are wegoing to maintain visibility and collaboration through the project life cycle? > Transparency
- 34. How are wegoing to maintain visibility and collaboration through the project life cycle? > Transparency
- 35. How are wegoing to maintain visibility and collaboration through the project life cycle? > Transparency > Owning decisions
- 36. How are wegoing to maintain visibility and collaboration through the project life cycle? > Owning decisions
- 37. How are wegoing to maintain visibility and collaboration through the project life cycle? > Transparency > Owning decisions > Get the most out of retros
- 38. How are wegoing to maintain visibility and collaboration through the project life cycle? > Get the most out of retrospectives
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. Less “my”, more“our”
- 45. Less “my”, more“our”
- 46. KEEP IT UP! Review.Adapt. Collaborate. Repeat.
- 47. Reduced product problems andrisks = Happy team
- 48. Reduced product problems andrisks = Happy team
- 49. A QA Testeris for life… not just for the end of a project
- 50.
- 51.
- 52.