Definition of Ready

Ready for what?

Ready to be picked up by the delivery team and added to a Timebox/Sprint backlog.

NOT:

Defined to the nth degree of detail so that no further discussion is required.

Definition of Ready:

Like the DoD, the DoR is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change.
Being agreed and enforced by the team means that it should, hopefully, mean an end to the common moaning in retrospectives that 'the story was crap'.

As the team gets used to only selecting 'ready' stories it focuses grooming/refinement sessions to ensure that the top priorities are in the best possible state.

The business/product owner will also very quickly understand the need for good prioritisation and quality stories. This is driven home the first time a team refuses to take a priority story into an iteration.

While there are a number of ways to start, many people are familiar with the INVEST principles for writing good user stories.

This stands for:

Independent, Negotiable, Valuable, Estimable, Small and Testable

DoR must, at the very least, address value, testable and estimable.

What might a basic DoR look like?

A story:

must have a defined business value (whether relative - points - or absolute - financial)
must be testable (by the owner at least, but also by the delivery team)
must be estimable (if it's too big to estimate, break it down. If we don't know enough to estimate, discuss it further and add details.)
must be prioritised in the team backlog
must exist in the tool used to store the team's stories (Cards or electronic)
must have a defined owner willing to work with the team and sign it off

Comments

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement. And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ? I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise. I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how to become more effective, then tunes and adjusts its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...

Definition of Done - An example

Done? To call a story 'Done-Done' we should refer to two things: the acceptance criteria for each story the team’s Definition of Done The DoD is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change. If you have project based teams, it's something to agree before timebox 1 kicks off. If you're more product based and continuously working through an ever growing backlog, slot it into a timebox kick-off, a retro (if that's where it was discussed) or just grab 10 minutes after the daily stand-up. An Example: Here's a basic example created by a team I was working with: ---------------------------------------------------------- A. Dev done ---- Code review done ---- Unit Tests written and passing ---- Integration tests written and passing B. Test complete ---- Manual Testing complete – Acceptance Met ---- Automation Tests written and ...

Empowerment?

The reason I titled this post with a question mark is that I believe empowerment to be a very misused term. Here's the Cambridge dictionary definition: Of course, you know this already. Yet for some, "to empower" has become synonymous with "to abrogate responsibility" Or in other words, passing the buck to your team: 'boss we need help dealing with team x' 'you're empowered to deal with that' This is just crappy leadership. Of course , you have to empower people so you're not a blocker. Of course , you have to give people additional responsibility to help them develop beyond their current role. But when you 'empower ' someone, you retain the accountability overall. It's not a get-out-of-jail-free card to blame them if things don't go as planned or to turn around months later and say 'well you can't complain. I empowered you to do it and you failed' No. If you're my bos...

IT Project Management - life on the front line

Search This Blog