An estimate by definition is: “an approximate calculation or judgment of the value, number, quantity, or extent of something.” It is fundamentally a guess, a probability distribution. When estimating an Agile backlog, no promise is made. No warranty should be expressed or implied. (If you want a guarantee, buy a …
In this post, I take a short sail through the waters of refining an Agile Team’s backlog. The ideal condition for a team’s backlog (of both user stories and non-stories) is for it to be: Owned by the team High with signal Low on noise From this state, the crew can plan …
Agile User Stories are short, simple descriptions of a feature or function told from the perspective of the person who desires the new capability represented by the story, usually a customer. They focus on the result or value that the user or customer gets. User stories can be big (but not …
While there is no single set of prescriptions or a silver bullet that will ensure repeatable success for every feature, every team, and every organization, the following Scrum Master Checklists might just help you get started thinking about the things that will ultimately move the ball in the right direction. The Really Short …
Opportunities for failure lurk everywhere. In projects, in code roll-outs, in team member interactions. We’re going to try a lot of new things. Some will work. Some won’t. We don’t set out to fail, but when we do, how will we handle it?
