Skip to content

Commit

Permalink
Merge pull request #14 from SaschaLucius/SaschaLucius-patch-1
Browse files Browse the repository at this point in the history
fixed  ScrumTeams error
  • Loading branch information
Sascha Lucius authored Jul 22, 2024
2 parents f7c08aa + 04f603c commit efc55e4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/Scrum_Guide_2020.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ They[ScrumTeam] are also self-managing[SelfManagement], meaning they[ScrumTeam]
The Scrum Team[ScrumTeam] is small enough to remain nimble and large enough to complete significant work within a Sprint[ScumEvents,Sprint], typically 10 or fewer people.
In general, we have found that smaller teams[ScrumTeam] communicate better and are more productive.
If Scrum Teams[ScrumTeam] become too large, they[ScrumTeam] should consider reorganizing into multiple cohesive Scrum Teams[ScrumTeams,ScaledScrum], each focused[ScrumValues,Focus] on the same product.
Therefore, they[ScrumTeam] should share the same Product Goal[ScrumArtifacts,ProductBacklog,Commitment,ProductGoal], Product Backlog[ScrumArtifacts,ProductBacklog], and Product Owner[ScrumTeam,ProductOwner].
Therefore, they[ScrumTeams] should share the same Product Goal[ScrumArtifacts,ProductBacklog,Commitment,ProductGoal], Product Backlog[ScrumArtifacts,ProductBacklog], and Product Owner[ScrumTeam,ProductOwner].

The Scrum Team[ScrumTeam] is responsible[Responsible] for all product-related activities from stakeholder[Stakeholder] collaboration, verification[Learn], maintenance, operation, experimentation, research and development, and anything else that might be required.[CrossFunctional]
They[ScrumTeam] are structured and empowered[Management] by the organization[Organization] to manage[Management] their[ScrumTeam] own work.
Expand Down

0 comments on commit efc55e4

Please sign in to comment.