1. How to Improve Quality of a product in an Agile environment
A Coach’s perspective

2. Your Instructor
Madhur Kathuria
Certified Scrum Coach
CSC,CSP, CSM, CSA
Product Operations Manager, PegaSystems
Chair, India Scrum Enthusiasts Community

3. How to Improve Quality of a product in an Agile environment
A Coach’s perspective

4. How to ‘Kill’ Quality of a product in an Agile environment
The Agile Devil’s workshop

5. WHO AM I ?
www.agiletour.org

6. Tip # 1
Ignore the story priorities
www.agiletour.org

7. Tip # 2
All stories must complete on last 1-2
days of sprint
www.agiletour.org

8. Tip # 3
Team should pick up more
stories than it can test
www.agiletour.org

9. Tip # 4
Make sure DoD is never looked
into during sprint review and is
invisible on team pages too .
www.agiletour.org

10. Tip # 5
Make Sure tasks published on
Scrum task board do not have
test plan review, test execution
and bug fixing
www.agiletour.org

11. Tip # 6
Code changes should continue
till last date of the sprint.
www.agiletour.org

12. Tip # 7
Make Sure Minimum time remains for
bug fixing at the end of sprint.
www.agiletour.org

13. Tip # 8
Make Sure Some bugs are definitely
carried to the next sprint and to the bug
backlog..
www.agiletour.org

14. Tip # 9
Make sure your bugs are not
tagged to stories/ features
www.agiletour.org

15. Tip # 10
Make Sure No Regression
testing is possible in the sprint
www.agiletour.org

16. Tip # 11
Focus only on the tasks
assigned to you.
www.agiletour.org

17. Tip # 12
Make sure your estimates include only
the development complexity/size and
not the test complexity and size.
www.agiletour.org

18. The Next Steps
Identify which of these things are common happenings in your projects
Identify 5 ways that you will thwart the plans for Agile Devil
www.agiletour.org 18

19. To improve the quality of a product
• Make Sure the team picks up only the stories it can test
• Make Sure your code changes finish well before the last date of the sprint.
• complete the story by priority and make sure stories finish well in time before sprint end
• Make Sure team tasks include test plan review, test execution and bug fixing
• Make Sure story are taken up for construction as per priority
• Make Sure No bugs are carried to the next sprint and to the bug backlog.
• Make Sure to include Regression testing in the sprint so that the bugs can be found early
• Help other team members if your work is complete. Remembers, its team goals which are important and Not the
individual goals.
• Make Sure Enough time remains for Bug fixing at the end of sprint. This would ensure high quality release.
• Make sure DoD is always looked into sprint review and is visbile on team pages too
• Make sure your bugs are tagged to stories/ features. This way you would be able to trace where it all started.
• Make sure your estimates include not only the development complexity/size and but also the test complexity and size
www.agiletour.org

20. THANK YOU
www.agiletour.org