A hardening sprint is an additional sprint that some teams run to stabilize the code and ensure that everything is ready just before release. Agile teams vary in their opinions on using hardening sprints in Scrum, but if your team does agree on having one before your release, there may be a lot to be done and varied expectations from the product owner, testers and developers. It may also lead to other work being delayed, leading to accumulation of technical debt.
In my article for Gurock TestRail Blog, I have discussed some tips on optimising the hardening sprint and achieving the maximum quality before release.
I talk in detail about some main points to focus on–
- Plan Ahead
- Perform End-to-End Testing
- Perform Non-Functional Testing
- Perform Tests on Other Platforms and Languages
- Reduce Lower Priority Defect Counts
- Use your sprint Wisely
Read the full article here — > https://blog.gurock.com/optimize-hardening-sprint/
Please share your thoughts!
One thought on “Optimize Your Hardening Sprint for a Quality Advantage”
[…] I, too, have worked with Hardening Iterations and here is the article I wrote a while back about it https://testwithnishi.com/2018/10/08/optimize-your-hardening-sprint-for-a-quality-advantage/ […]