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
The sailboat retrospective is a model that I especially like to use at the end of significant chunks of work, like a release or the end of an epic or the end of a project. But it could be used at any time, especially if there is a need to better understand project objectives, risks, hindrances and helpers.
I like to use this model for post release retrospectives because it helps the team to focus on lessons learned around unexpected risks, the things that slowed the team down and celebrate the things had really helped us.Continue reading Retrospective idea: Sailboat