{"id":83,"date":"2019-05-07T18:43:14","date_gmt":"2019-05-07T16:43:14","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=83"},"modified":"2026-02-16T11:55:59","modified_gmt":"2026-02-16T10:55:59","slug":"rteamlevel","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/rteamlevel\/","title":{"rendered":"Team"},"content":{"rendered":"

The Team<\/strong> is the basic element of an agile organization and forms the home of working people. Up to nine related Teams form a Cluster<\/a>.<\/p>\n

Most of the work takes place in stable and long-lasting Teams. <\/span>Due to the stability or “longevity”, the teams are available in the event of problems even if the Application or Market Variant<\/a> is not currently being revised (ie when the classic project teams no longer exist).<\/span><\/span><\/p>\n

P4 adopts the basic structure of a Scrum team. <\/span>It consists of a <\/span><\/span>Team Product Owner<\/span><\/span><\/strong><\/a> , <\/span><\/span>Team Scrum Master<\/span><\/span><\/strong><\/a> and the <\/span><\/span>Working Team<\/span><\/span><\/strong> who works together to create value for the <\/span><\/span>Stakeholders<\/span><\/span><\/a>. <\/span>The <\/span><\/span>principle of the separation of powers<\/span><\/span><\/a> creates clearly defined areas of role responsibility that complement each other in the Team.<\/span><\/span><\/p>\n

The <\/span><\/span>Team Product Owner<\/span><\/span><\/strong><\/a> is responsible for maximizing the value of the “Product” resulting from the work of the Working Team. <\/span>How this happens can vary greatly depending on the organization and Working Team, as well as the experts working in them. <\/span>The Team Product Owner<\/a> is the only person responsible for managing the Team Backlog<\/a>.<\/span><\/span><\/p>\n

The <\/span><\/span>Working Team<\/span><\/span><\/strong>\u00a0consists of three to nine members plus the <\/span><\/span>Team System Engineer,<\/span><\/span><\/strong><\/a>\u00a0who <\/span>work out <\/span>finished and <\/span>inspectable results<\/span><\/a> in each <\/span><\/span>Iteration<\/span><\/span><\/a> and <\/span>ideally present a potentially deliverable system or subsystem increment\u00a0<\/span>in the <\/span>Team Review<\/span><\/a> at the end of the Iteration <\/span>.<\/span><\/span><\/p>\n

The <\/span><\/span>Team Scrum Master<\/span><\/span><\/strong><\/a> is a “Servant Manager” and is responsible for encouraging and supporting team work in accordance with the Scrum and P4 rules by helping everyone involved to understand the values \u200b\u200band practices. She cares about the team process, risks, problems and improvements.<\/span><\/span><\/p>\n

Unlike Teams, Groups<\/strong> are mainly there to communicate and make decisions across different levels and teams. The simple principle applies: “Teams work, groups discuss and decide”.<\/p>\n

The Working Team<\/h2>\n

[WPinclude]workingteam[\/WPinclude]<\/p>\n

Descriptions of Team types (aka “Team Flavors”)<\/span><\/span><\/h2>\n

Team types describe different lineups of Teams within the Organization, as well as their type of \u200b\u200bresponsibility.<\/span><\/span><\/p>\n

Service Team<\/span><\/span><\/span><\/h3>\n

[WPinclude]service-team[\/WPinclude]<\/span><\/span><\/p>\n

Module Team <\/span><\/span><\/span>and<\/span><\/span> Platform Team\u00a0<\/span><\/span><\/span><\/h3>\n

[WPinclude]module-team[\/WPinclude]<\/p>\n

Application Team <\/span><\/span>and<\/span><\/span><\/span> Feature Team<\/span><\/span><\/span><\/h3>\n

[WPinclude]application-team[\/WPinclude]<\/p>\n

More Teams<\/span><\/span><\/h2>\n

In some organizations there are special <\/span><\/span>Support Teams<\/span><\/span><\/strong> for the better separation of development <\/span>topics <\/span>and support and maintenance <\/span>topics, which accept unplanned inquiries and work, clarify and solve simpler topics themselves. <\/span>This shields the development teams from unplanned activities and enables better planning and predictability of the development teams.<\/span><\/span><\/p>\n

.<\/span><\/p>\n

\n

Further suitable links: Example of a medium-sized organization<\/a><\/p>\n\n\n\n\n
Events<\/td>\nRoles<\/td>\nGroups<\/td>\nArtifacts<\/td>\n<\/tr>\n
Team Planning<\/a><\/p>\n

Team Sync<\/a><\/p>\n

Team Backlog Refinement<\/a><\/p>\n

Team Review<\/a><\/p>\n

Team Retrospective<\/a><\/td>\n

Team Product Owner<\/a><\/p>\n

Team System Engineer<\/a><\/p>\n

Team Scrum Master<\/a><\/td>\n

Working Team<\/a><\/p>\n

Community of Practice<\/a><\/td>\n

Team Backlog<\/a><\/p>\n

Inspectable Results<\/a><\/p>\n

Team DoD<\/a><\/p>\n

Team Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"The Team is the basic element of an agile organization and forms the home of working people. Up to nine related Teams form a Cluster. Most of the work takes place in stable and long-lasting Teams. Due to the stability or “longevity”, the teams are available in the event of problems even if the Application…","protected":false},"author":3,"featured_media":357,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,21],"tags":[233,234,426,427,428,490],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/83"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=83"}],"version-history":[{"count":88,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/83\/revisions"}],"predecessor-version":[{"id":3007,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/83\/revisions\/3007"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/357"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=83"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=83"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=83"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}