What is DOR and DOD in a Scrum

-

DOR and DOD is a standard format defined for the project to start(Definition of Ready)  and complete (Definition of Done)  the  user stories in each sprint .

 DOR

 In simple words , DOR is the pre-requisite to check before we start any user story to work.

Examples : checking the Pre-requisite before we start any course to learn

                  ( Pre-requisite like : whether he/she knows any programming languages 

                                                   whether he/she completes minimum degree or not )    

                  

Examples : checking the Pre-requisite before we start any course to TEACH THE COURSE

                  ( Pre-requisite like :  Trainer to check whether the course content is ready to start the course 

                                                   whether the required PPT/documents are ready to teach the course )    

                  

DOD 

In Simple words , DOD is the pre-requisite to check whether all the Pre-requisites/Criteria met to confirm the assigned story is "Done" 

Example : checking the Pre-requisite before we are going to complete any chapters in the course.                        (i.e.saying that we have "DONE" - meaning we have understood that particular chapter)  

                  ( Pre-requisite like : whether he/she understood the topic / chapter of the course 

                                                   whether he/she completed the assignments/quizes  )    

Examples : checking the Pre-requisite before saying the COURSE is 'DONE"

                  ( Pre-requisite like :  Trainer to check whether all the course content is covered in the course 

                                                   whether the required PPT/documents are shared to the students or not )  

Mobile App Development Project  :   

DOD may include : All Images are compressed .

                                All code is magnified and zipped . 

Software Development project :

DOD may Include : 

All code has been thoroughly tested via Unit , Integration and end-to-end tests


As per Atlassian : 

DOR : Criteria that Allows you to evaluate the work before your teams starts on it . 

           Defines the tasks, user story or story points for your team .

DOD : Criteria that a product increment must meet for the team to consider it complete and 

            ready for customers  

Difference between DOR and DOD : 

DOR : Criteria to determine if the user story / task is ready for your team to tackle 

DOD : Benchmark to evaluate when a user story / task is complete by your team .

Comments

Post a Comment

Popular posts from this blog

Product Owner - Role And Responsibilities and Po V/s SM

-
Image
What is a Product Owner?  Reference : https://www.c-sharpcorner.com/article/product-owner-role-and-responsibilities/ To be precise, a product owner is a scrum development role for a person who represents the business or user community, and is responsible for working with the user group to determine what features will be included in the product release.   Image Source – ProductCoalition.com   What are a Product Owner’s Responsibilities? The Product Owner (PO) represents the business to the development team and the Scrum team to the business folks. The PO  is one person, not a committee or group of people. The PO has product vision. The PO  owns the budget and is responsible for the success of the product. He/she is part of the Scrum team – closely works with the development team and Scrum Master throughout the sprint. The PO owns the product backlog and directs product development through product backlog prioritization. Strives to maximize the...
Read more

how many story points we can allocate for a sprint and how

-
 To determine how many story points you can allocate for a sprint, you need to consider the available hours, the number of developers, and the relationship between hours and story points. Here’s how you can calculate it: Step 1: Determine Total Available Hours for the Sprint Given: Total hours for the sprint : 180 hours Number of developers : 3 Step 2: Estimate Story Points Per Developer Assume that one story point represents a certain number of hours of work. For example: 1 story point = 8 hours Each developer has 60 hours available: Hours per developer = 180  hours 3  developers = 60  hours/developer \text{Hours per developer} = \frac{180 \text{ hours}}{3 \text{ developers}} = 60 \text{ hours/developer} Hours per developer = 3  developers 180  hours ​ = 60  hours/developer Given this, the number of story points each developer can handle: Story points per developer = 60  hours 8  hours/story point = 7....
Read more

To determine how many sprints for a User Stories

-
 To determine how many sprints it will take to complete 59 user stories and how many story points to assign to each user story, we need to break this down step-by-step: Step 1: Estimate the Story Points Assess the Complexity : First, you need to estimate the complexity of each user story. Story points are often assigned based on factors like effort, risk, and complexity. Use techniques like planning poker or t-shirt sizing to estimate. Typical Scale : Story points are often estimated using Fibonacci-like sequences (e.g., 1, 2, 3, 5, 8, 13, 21) or other scales that represent effort. Step 2: Determine Team Velocity Velocity : Velocity is the number of story points a team can complete in one sprint. For example, if the team completes 30 story points in a 2-week sprint, their velocity is 30. Historical Data : If the team has historical data, use that to determine their average velocity. If not, start with a rough estimate based on team capacity. Step 3: Calculate Number of Sprints Once...
Read more