Suborbital-Systems/ReadySetGit
2
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

Renumber 4.1

Browse Source
This commit is contained in:
William Sandner 2023-07-25 14:39:26 +02:00
parent a6cdaf10f5
commit 9b825ec104
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
SDM.md
View File

@ -301,29 +301,29 @@ Backlog refinement, also known as "Backlog Grooming," is an ongoing process wher
The Product Owner (PO) is primarily responsible for managing the Product Backlog. Their involvement includes: The Product Owner (PO) is primarily responsible for managing the Product Backlog. Their involvement includes:
1. Defining and Communicating Vision: The PO defines the product vision and communicates it to the team and stakeholders. The vision serves as a guide for prioritizing the items in the Product Backlog based on their alignment with the product's overall goals. - 4.1.3.1 Defining and Communicating Vision: The PO defines the product vision and communicates it to the team and stakeholders. The vision serves as a guide for prioritizing the items in the Product Backlog based on their alignment with the product's overall goals.
1. Gathering Stakeholder Requirements: The PO collaborates with stakeholders, customers, and users to understand their needs, requirements, and feedback. They gather input and insights to ensure the Product Backlog reflects the most valuable features and improvements. - 4.1.3.2 Gathering Stakeholder Requirements: The PO collaborates with stakeholders, customers, and users to understand their needs, requirements, and feedback. They gather input and insights to ensure the Product Backlog reflects the most valuable features and improvements.
1. Prioritization: The PO prioritizes the items in the Product Backlog, considering the stakeholders' needs and the product's strategic goals. High-priority items are positioned at the top of the backlog to be addressed earlier. - 4.1.3.3 Prioritization: The PO prioritizes the items in the Product Backlog, considering the stakeholders' needs and the product's strategic goals. High-priority items are positioned at the top of the backlog to be addressed earlier.
1. Continuous Refinement: The PO continuously refines the Product Backlog, ensuring that it contains clear, well-defined, and actionable items. They add new items, revise existing ones, and remove obsolete or less valuable items based on changing priorities and feedback. - 4.1.3.4 Continuous Refinement: The PO continuously refines the Product Backlog, ensuring that it contains clear, well-defined, and actionable items. They add new items, revise existing ones, and remove obsolete or less valuable items based on changing priorities and feedback.
1. Collaboration with the Development Team: The PO collaborates closely with the Development Team to provide clarifications on requirements and answer questions during backlog refinement. This ensures that the team has a clear understanding of the items before Sprint Planning. - 4.1.3.5 Collaboration with the Development Team: The PO collaborates closely with the Development Team to provide clarifications on requirements and answer questions during backlog refinement. This ensures that the team has a clear understanding of the items before Sprint Planning.
##### 4.1.4 Involvement of the Development Team ##### 4.1.4 Involvement of the Development Team
The Development Team plays an active role in Backlog Refinement, ensuring that the items in the Product Backlog are "ready" for Sprint Planning. Their involvement includes: The Development Team plays an active role in Backlog Refinement, ensuring that the items in the Product Backlog are "ready" for Sprint Planning. Their involvement includes:
1. Asking Clarifying Questions: During backlog refinement sessions, the Development Team seeks clarifications from the Product Owner regarding the details, acceptance criteria, and expected outcomes of the items. - 4.1.4.1 Asking Clarifying Questions: During backlog refinement sessions, the Development Team seeks clarifications from the Product Owner regarding the details, acceptance criteria, and expected outcomes of the items.
1. Estimating Effort: The Development Team estimates the effort required to implement each item. These estimates help the Product Owner and stakeholders understand the relative size and complexity of the work items. - 4.1.4.2 Estimating Effort: The Development Team estimates the effort required to implement each item. These estimates help the Product Owner and stakeholders understand the relative size and complexity of the work items.
1. Providing Feedback: The Development Team provides feedback on the feasibility, technical constraints, and potential risks associated with the items. They offer insights into alternative approaches or potential improvements to enhance value delivery. - 4.1.4.3 Providing Feedback: The Development Team provides feedback on the feasibility, technical constraints, and potential risks associated with the items. They offer insights into alternative approaches or potential improvements to enhance value delivery.
1. Splitting User Stories: If backlog items are too large or complex, the Development Team collaborates with the Product Owner to split them into smaller, more manageable user stories that can be completed within a single Sprint. - 4.1.4.4 Splitting User Stories: If backlog items are too large or complex, the Development Team collaborates with the Product Owner to split them into smaller, more manageable user stories that can be completed within a single Sprint.
1. Commitment to Deliver: Before Sprint Planning, the Development Team commits to delivering a set of items from the Product Backlog for the upcoming Sprint. This commitment ensures a shared understanding and responsibility for achieving the Sprint Goal. - 4.1.4.5 Commitment to Deliver: Before Sprint Planning, the Development Team commits to delivering a set of items from the Product Backlog for the upcoming Sprint. This commitment ensures a shared understanding and responsibility for achieving the Sprint Goal.
Through effective collaboration between the Product Owner and the Development Team, the Product Backlog becomes a valuable tool for prioritizing and aligning the team's efforts with the product's vision and objectives. Continuous refinement ensures that the team works on the most valuable and relevant items, contributing to the success of the project. Through effective collaboration between the Product Owner and the Development Team, the Product Backlog becomes a valuable tool for prioritizing and aligning the team's efforts with the product's vision and objectives. Continuous refinement ensures that the team works on the most valuable and relevant items, contributing to the success of the project.