Product Owner & Questions
Definition of Done (DOD)
DOD is setting up a list of items that should be completed before user story can be considered complete. It separates the items from "in-progress" to "done".
The Definition of Done (DOD) will be agreed upon by both Technology and Business teams.
The sample Definition of Done is represented below
1. Analysis and Design completed
2. Coding and Unit testing completed
3. Test cases are created
4. Code review is done
5. Test case review is done
6. Functional Sign off is available
7. Integration sign off is available
8. Code is checked in
9. Code is deployed to test the environment
10. Code/feature passes regression testing
11. Code/feature passes smoke testing
12. Code is documented
13. Help documentation is updated
14. The feature is OK’d by stakeholders
- Acceptance criteria has been met
16. To be finalized after discussing with Business
Definition of Ready (DOR)
The Definition of Ready (DOR) will be agreed upon by both Technology and Business teams.
The sample Definition of Ready is represented below
1. User Story is defined at small possible fundamental level. This means, user stories should not be defined at large / mid size level.
2. User story independent in nature
3. User story is estimable
4. User story follows user story and acceptance criterion format
5. User story can be completed within a sprint
6. All the blocking dependencies (can be internal /internal) are resolved
7. All the mockups are available
8. To be discussed further and agreed between product and tech teams
Daily Scrum :
The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. It focuses on the progress toward the Sprint Goal.
As part of it, each team member is expected to update the below aspects:
What is my RAG status?
What did I do yesterday that helped the Development Team meet the Sprint Goal?
What will I do today to help the Development Team meet the Sprint Goal?
Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
- As part of this update, the team member is supposed to explain the cause for their amber or red status and actions taken/needed to turn it to green. Please refer to the Impediment section for more details.
What did I do differently yesterday that I feel proud of or want to share with others in brief words?
- At Comapnies, They encourage day-wise innovations/highlights so that we can construct them toward great value addition in a Sprint.
Key Benefits of Daily Scrums:
Improve communications
Eliminate other meetings
Identify impediments to development for removal
Highlight and promote quick decision-making
Improve the Development Team’s level of knowledge
This is a key inspect-and-adapt meeting.
The Scrum Master is expected to publish the daily scrum meeting update that adheres to the following template:
Upstream Dependencies: These are the tasks or processes that must be completed before your task can begin. Think of them as the "inputs" or requirements that are necessary for your work. For example, if you depend on another team to deliver a feature before you can start building your own, that team’s work is an upstream dependency for you.
Downstream Dependencies: These are the tasks or processes that depend on your task being completed. If someone else’s work depends on what you are doing, that is a downstream dependency. For instance, if a testing team is waiting for your feature to be implemented before they can run their tests, your work is a downstream dependency for them.
In agile or product management, managing these dependencies is important because they can affect timelines, workflow, and delivery expectations.