top of page


Don’t Develop in One Sprint and Test in the Next
When teams first learn that every Sprint they must deliver a usable, Done increment—including both development and testing—it can feel impossible. A common temptation is to develop in one Sprint and test in the next. Don’t. The extra cost is far higher than most teams expect. Here are the five biggest problems this creates. Administrative Burden You've just created a whole lot of administrative burden for the Scrum team. Now instead of keeping track of one Product Backlog it

Mary Iqbal
Aug 232 min read
bottom of page
