Posts

Your project shouldn’t finished when every ticket is implemented. Instead have in mind to finish it when there are no more stories worth doing. There will come a time when the stakeholders scan the backlog and find that none of the remaining stories are worth doing. It’s not uncommon for an early story’s priority to evaporate over time, as higher‑value work is surfaced. That’s just fine. The team should recognize that when the flow of value has stopped, we can gracefully end the project, instead of chasing backlog completion for its own sake.

We can look at each iteration as a pump. As each iteration completes, we add the completed velocity to the chart so that everyone can see how fast we’re going. Iteration after iteration the pump draws ROI out of the story deck. Continuous exploration pumps ROI back in by discovering new, valuable stories. As long as incoming ROI outpaces outgoing ROI, the project keeps flowing. When exploration slows and new features dry up, the deck’s ROI is exhausted. ...

Plan from What You Learned We learn how much a team can do by looking at the last iteration - that’s “yesterday’s weather.” If the team finished 18 points in the last iteration, we plan for 18 points in the next iteration. And at the midpoint we check the team’s progress, expecting to learn that half of the work, 9 points, has been done. But, if we find that more got done, 12 points (wonderful!), then the stakeholders might decide to move more work into the current sprint since there might be capacity for it. ...

At the midpoint we check our team’s progress. If the team is behind, the worst choice is to tell them to “catch up.” More pressure makes builders rush, skip tests, and ignore edge cases. That leads to bugs, technical debt, and burnout. A better choice is to re‑scope. Ask: if the team keeps the same quality and pace, what can be finished this week? Remove lower‑value stories and set a new honest goal. ...

How do we choose what to build first? One approach to help figure this out, is to play a simple four-quadrant game: look at each story’s value and cost. Valuable and cheap: do it now. Valuable but expensive: do it later. Not valuable and cheap: maybe someday. Not valuable and expensive: don’t do it. This is just a guide to get the ball rolling, in some cases the results don’t always make sense. For example, Logout might be important and cheap, so do it; But Login may be important but costly, so wait; ...