ProductSavvy - Scrum and QA
0 likes1,071 views
Scrum is an agile process that focuses on delivering high business value in short iterations. It incorporates QA into the scrum process through: 1) Including testers in sprint planning and estimation. Testing tasks are estimated alongside development tasks. 2) Having testers participate in daily stand-ups to report on testing progress and blockers. 3) Having testers identify lessons learned and best practices from each sprint and drive needs for new test cases. 4) Clearly defining test responsibilities between developers and testers, with developers owning unit testing and testers owning other testing types.
ProductSavvy - Scrum and QA
- 1. 1 QA with SCRUM Jonathan Chashper 30 January 2015
- 2. About Product Savvy We reduce companies’ risk and improve commercial success by helping them deliver Products that Resonate in their Target Market We are doers 2 We are Product Centric We are Agile, Lean, Scrum Evangelists We Love Start-Ups We ‘Get’ Business and Technology We Build Products
- 3. My Backgrounds 20+ Years of in PdM and R&D – ProductSavvy – CEO, Founder – Heavy Start-Up experience Hillcrest Labs AeroScout (purchased by Stanley Black and Decker, ~$250MM) – IDF (8200 Unit) Israel Defense Prize Education: – B.Sc in Computer Science (Israel) – MBA (Kellogg, Northwestern) 1/30/2015© 2006 – 2014 Product 3
- 4. What is Scrum? • Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. 4
- 6. Scrum Roles Product Owner - Defines the features / Road map / Releases of the product Scrum Master - Represents management to the project Team – Programmers, DBAs, Web developers, UX designers, etc. Where is QA?? 6
- 7. QA is Not Part of the Scrum Roles There is no tester in the Scrum Roles definitions Who is testing then??? – Devs? (Unit Testing) – Product Owner? – Customer? How are tests planned? – What is the source? (Product Backlog) – Test Tasks – Documentation 7
- 8. So, how to incorporate QA into Scrum? 8
- 9. Sprint Planning Team selects items from the product backlog they can commit to completing – Include Testers in the Planning Process Sprint backlog is created – Tasks are identified and each is estimated (1-16 hours) – Collaboratively, not done alone by the ScrumMaster – Testing is part of the effort estimation of the Story SW Design is Reviewed QA / Test Planning for the Sprint is Reviewed
- 10. The Daily Scrum Parameters – Daily – 15-minutes – Stand-up Not for problem solving – Whole world is invited – Only team members, ScrumMaster, product owner, can talk Helps avoid other unnecessary meetings Everyone answers 3 questions: – What did you do yesterday? – What will you do today? – Is there anything in your way?
- 11. Daily Scrum – QA Perspective QA Person (s) is part of the team Participates in Daily Scrum – asked the same questions If needed, will work with individual devs to demo / explain defects Only QA Person can mark a Defect as “Done” Only after QA Person completes test tasks a Story is “Done” 11
- 12. Tools Scrum Management Software - VersionOne – Stories – Tasks – Tests – Defects Setup Code Repository - Assembla Setup Dev / Testing / Production environments - Amazon Cloud Unit Testing – Junit Manual / Automated testing – as needed 12
- 14. The Sprint Review Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal – 2-hour prep time rule – No slides Whole team participates Invite the world
- 15. The Sprint Review – QA Perspective QA identifies what went right and what went wrong in current sprint QA identifies lesson learned and best practices QA drives the need for user stories that support testing Reported / Fixed / Rejected bugs – visualization is important 15
- 16. Devs vs. QA - Responsibilities 16 Activity Developers Testers Requirements Testing Partial (What is covered by Unit Testing) Full Acceptance Full Unit Testing Full Functional/Exploratory Testing Full Regression Testing Full Compatibility Testing Full Performance Testing Full Security Testing Full Deployment Testing Full
- 17. QA - Lessons Learned Empower QA People QA Should report to Scrum Master / Product Owner Tests created ahead of Sprint – QA moves faster than dev QA is done during the Sprint, not after Sanity testing defined and performed, often – Unit testing performed by devs, before QA Staging / Testing Environment was created, separated from Dev and of course, Production 17