I sometimes hear from people in tech: "I hate scrum and don’t think it provides any value." That probably means they're doing scrum wrong.
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!
Estimating work is a difficult process, and coming to consensus can be challenging. But just averaging everyone's points estimates isn't good enough.
In every backlog I've estimated, I encounter the story that knows no bound. The Un-estimatable Story. Anxiety wells within me at the drawn out conversation about to begin as we get
A systematic method for breaking a large design project into activities, features, and tasks — helping you spend your time in the most valuable places.
If you're plagued with poor estimation of user stories, appoint a "scout" — someone who'll take responsibility and properly prepare for planning meetings.
Though they have a place, burn charts, iterations, and story points don't keep the team focused on shipping meaningful chunks of value.
A discussion of what to do when an Epic story is broken down into smaller stories and the point totals don't add up.