A "Definition of Done" is only half the story
Senior devs also use a “DoR.” A Definition of Ready makes sure you start only when you have everything you need.
You need a DoR
A “definition of ready” is just as important as a “definition of done.” And using both, consistently, is the key to success in development and delivery. That’s why senior developers use both, with every single action, every day.
There’s three things that experienced developers understand:
Having a definition of ready makes sure you won’t start something unless you’re lined up to succeed. For instance, before taking on a given task in a sprint you need a formula, a checklist, to make sure you have all the information you need to accomplish the task.
Likewise, a definition of done will make sure you don’t declare success prematurely. It could be something seemingly trivial, like making sure documentation has been updated, or something major, like actually deploying a feature to your production replica. Knowing when you can declare success is equally important.
And in both cases, consistency is the key, and that means adopting your “DoR” and “…
Keep reading with a 7-day free trial
Subscribe to Customer Obsessed Engineering to keep reading this post and get 7 days of free access to the full post archives.