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


Incremental delivery and the need for speed
Digital AI’s annual State of Agile report is a survey that has global participation from small, medium-sized and large companies. It asks questions such as what Agile frameworks are being used, and what are the biggest problems Agile teams face. But one of the most interesting questions - to me - that they ask is this: Why are you using Agile? In almost every single one of those years the number one answer has been SPEED. But why? After all, Agile teams don’t code any fa
Mary Iqbal
Jul 133 min read
bottom of page
