Many folks in leadership positions mistakenly buy in to “Doing” Agile with only their IT/Engineering departments, looking to increase velocity, to ship features faster, and have their organization behave in a predictable way. I’m afraid they have it all wrong….
The goal of the Agile project inception stage is to: Bring clarity to what it is that might be built, who to build it for, and why Drive down risk in a very cost-effective way – by prototyping and experimenting Fail fast, cheap and safe (if in fact we’re going …
Where does the traditional, hierarchical role of “Boss” or the Agile Manager role fit in at an organization that is guided by the values and principles of the Manifesto: Individuals and interactions over processes and tools. Build projects around motivated individuals. Give them the environment and support they need, and …
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 …
