Scrum best practices
Download as PPTX, PDF2 likes1,758 views
The document outlines best practices and challenges for Scrum teams, emphasizing the collaborative role of QA within the development team during iterations. It details the necessity of test plans, acceptance criteria, and various testing types, alongside the responsibilities of developers and testers. Additionally, it highlights best practices like using story points for estimation, conducting burndown chart analysis, and incorporating test automation.
Scrum best practices
- 1. Scrum Team Best Practices
- 2. Challenges and Resolutions Is QA part of the development team? Yes Should QA be in the same iteration as development? Yes Who does QA? Scrum Team (All team members) Do we need “test plan”? Yes (Should be created during Sprint Planning) Are acceptance tests enough for a user story? No, Definition of Done (DOD) should be well defined When do we know testing is done? When the defined Acceptance Criteria is met Who defines test cases? Primarily done by QA, and reviewed by Scrum Team Do we need to track bugs? Yes, till closure
- 3. Types of Testing Unit Testing Smoke Testing Functional Testing Integration Testing Performance Testing Regression Testing Load Testing
- 4. Who Does What? What When Who Unit Testing Coding Developer Smoke Testing Drop Developer/Tester Integration Testing Coding Developer/Tester Regression Testing Drop/Test Developer/Tester Acceptance Testing Delivery PO Performance Testing Delivery Tester Load Testing Delivery Tester Inside the sprint Outside the sprint
- 5. Defect Filter Sprint Planning Test Case Review Unit Testing Functional Testing Integration Testing
- 6. Prioritization Sprint Planning (Sprint Backlog) Build Deployment Plan Test Cases Backlog Grooming
- 7. Additional Best Practices Estimate in Story Points and tasks in hours Burndown Chart Analysis Test Automation Test Coverage (Sonar) CI is continuous QA BDD TDD