Teams within the organization are structured in clusters . All future work of the team will be managed in the Team Backlog . Current work is shown in the Iteration Backlog or on a Kanban board . Depending on the type of team, teams create features and applications , modules and system platforms or services . The team’s quality requirements are listed in the team DoD .
Every team that organizes itself within the P4 framework has the following artifacts:
- A Team Backlog consisting of Team Backlog Items (TBIs) that are restricted by acceptance criteria. The TBIs can vary depending on the team flavor and thus the type of responsibility:
- If the team works according to Scrum: An Iteration Backlog (Scrum Board, TBIs and tasks for the iteration)
- When the team works after Kanban: A Kanban board with TBIs and tasks
- Team products, depending on team responsibility (team flavor)
- general for all teams: Inspectable Results, Usabale Knowledge, System Increment
- Application and feature teams: features & applications
- Module Teams: versioned Modules & platforms
- Service teams: Services & services
- Team definition of done
- Team Improvement Backlog
.
\r\n
Further suitable links:
| Events | Roles | Groups | Artifacts |
| Team Planning | Team Product Owner | Working Team | Team Backlog |