Skip to main content

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




Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

Agile Bert joins the world of blog.

My far more technical compadre and fellow Agile Yorkshire attendee 'Agile Bert' (aka John) has joined the blogging world. Will he become a prolific blogger? Will he become a (thought) leader amongst men? Why is he called Bert? That last one actually has an answer: here
Post a Comment
Read more

The case for Project Management in Agile?

OK, I know how most of the Agile community feels about Project Managers: Process over People Meetings Documentation Urrgh... But however you name the role (Agile Delivery, Scrum Master, Project Manager) and whoever does it  - someone needs to help the team to: Plan Track Deliver Communicate Being a group of incredibly talented engineers does not give a team the right to ignore 3.5 of these. All too often, engineers want to dive in to designing and building great software, but see planning as a hassle, tracking as a waste of time (or an abuse of their rights), communication as an alien concept and delivery (the fun bit) as something that will be done when it's done. It may be popular to talk about being a 'self-organising team' and railing against any form of 'order' being imposed.  But why is that order being imposed?  Maybe it's to deal with the chaos that your s-o-t has failed to deal with so far. As organisations scale and the senior leadership gets further a...
Post a Comment
Read more