Definition of Ready (DoR) for Business Analysts
Updated: 14 hours ago
I bet you've been in situations where you were UNABLE to answer one of these very simple questions:
👉 Do we have enough user stories to start the sprint?
👉 Are the user stories clearly defined and understood by all team members?
👉 Have all dependencies been identified and resolved?
👉 Is the story testable, and are the testing criteria clearly defined?
The answer (or seeking the answer) to all these questions will always lead you to the Definition of Ready (often referred to as DoR).
I strongly believe that the Definition of Ready is the single most important agreement that you need to establish on your Agile team. Even more importantly, you should do it before you add a single user story to your backlog.
In this short video, I explain what Ready is (with references to the Scrum Guide! 📘) and why, as a BA, you need it. Additionally, I provide an exact template that you should use as a starting point when establishing the Definition of Ready for your specific Agile team.
I'll see you in the video!
Feeling stuck at the same BA level and don't know where to go? Join me for a free, 1-hour webinar. We'll walk through a career model used by top IT companies for business analysts - from Junior to Lead - and how you can use it to see where you are and what it takes to move up.
Comments