I propose that we stop measuring throughput or velocity. Instead, companies should empower software teams to make value estimates on individual work items.
In this third part of my Rethinking Agile series, instead of adding practices, I recommend something for you to remove. That is, stop estimating effort!
A month or so into an engagement, we came across a story that took much longer than our estimate suggested. This experience made us reevaluate the backlog.
In a previous role, I took any chance to better understand how my product could satisfy the needs of my market. A beta release provides that opportunity.
Thanks for following along as I adapt agile software practices into "normal" life! Today, we’re going to talk about building a non-software-related backlog.
The software backlog is everyone’s main hub for information, and it should be more than a giant to-do list. Here are 5 questions your backlog should answer.
