From a33b25673b76d315725cd97b44629e2fc2c75c71 Mon Sep 17 00:00:00 2001 From: William Sandner Date: Fri, 17 Nov 2023 18:39:49 +0100 Subject: [PATCH] Refactor Scrum Team description and responsibilities - Simplify and clarify the description of the Scrum Team and their roles. - Emphasize the importance of cross-functionality and self-management. - Highlight the benefits of smaller teams and the need for reorganization if they become too large. - Acknowledge the Scrum Team's responsibility for all product-related activities. - Stress the importance of working in Sprints at a sustainable pace. --- Scrum-Guide.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/Scrum-Guide.md b/Scrum-Guide.md index 143400a..5c2b94e 100644 --- a/Scrum-Guide.md +++ b/Scrum-Guide.md @@ -110,24 +110,13 @@ These values give direction to the Scrum Team with regard to their work, actions ## Scrum Team -The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of -one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams -or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. +The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. -Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value -each Sprint. They are also self-managing, meaning they internally decide who does what, when, and -how. +Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how. -The Scrum Team is small enough to remain nimble and large enough to complete significant work within -a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better -and are more productive. If Scrum Teams become too large, they should consider reorganizing into -multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the -same Product Goal, Product Backlog, and Product Owner. +The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner. -The Scrum Team is responsible for all product-related activities from stakeholder collaboration, -verification, maintenance, operation, experimentation, research and development, and anything else -that might be required. They are structured and empowered by the organization to manage their own -work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency. +The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. They are structured and empowered by the organization to manage their own work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and