While the Scrum Guide encourages teams to create a Definition of Done so that everyone understands what ‘done’ means, it says nothing about creating a Definition of Ready so that everyone understands what pre-conditions must be met before a user story may be allowed onto a sprint.Continue reading What is a Definition of Ready?
Happy new year!
Human beings have seemingly been making new year’s resolutions for around 4,000 years. There is something about the year incrementing by one that somehow encourages folks to examine their past failures and vouch to do better in the year ahead.
And yet, research (and plenty of personal experience) shows that around 80% of resolutions will be broken by the second week of February.
There is a better way.Continue reading Marginal gains for development teams
Recently at work, we’ve been looking at standardising certain tools and events such as sprint reviews. This post looks at what a sprint review is and offers a suggested agenda.Continue reading What happens during a sprint review?
A few months ago, my team at work considered using DSDM’s MoSCoW prioritsation technique for our project’s user stories in Jira.
After a little pondering, this morning I worked out how to do this in our cloud-hosted Jira. This short post shows you how.Continue reading How to create new MoSCoW prioritisation statuses in Jira
I’ve been thinking a lot recently about the size of user stories in agile projects. The idea that I’ve been reflecting on is what if teams only worked with small, similarly-sized pieces of work, rather than exponentially larger blocks of work?
In theory, small user stories should be more predictable, should include less risk, less uncertainty and less complexity. They should, therefore, take less time to complete than larger user stories… you would think! Or as Mike Cohn put it in Agile Estimating and Planning (Prentice Hall, 2006), “small stories keep work flowing”.Continue reading The importance of small user stories