Each team organized within the P4 framework produces inspectable results, i.e. all team results can be checked for completeness and quality according to their acceptance criteria and the Definition of Done.
The type of inspectable results can vary greatly depending on the type and responsibilities of the team. It is important that the team’s added value is clearly traceable. This is also important for the self-image of the team and the pride of the team members in their work.
The Team Scrum Master Group and the Cluster Scrum Master must ensure that each team is responsible for as much of the added value of a product as possible. If the division is too fine-grained and the team is too specialized, the team loses the feeling of participation in the product and feels more like a “small cog in the wheel”.
Examples of inspectable results are:
- Result report of a consumer study
- Industrial design of a product
- User interface for a mobile app
- 3D model of mechanical parts at an agreed level of maturity (e.g. without bevels for tools)
- Circuit diagrams of electronic circuits
Depending on the P4 team type (team flavor) there are different predefined areas of responsibility and team results:
- general for all teams: Inspectable Results, Usable Knowledge, System Increment
- Application and feature teams: features & applications
- Module Teams: versioned Modules & platforms
- Service teams: Services & services
.
Further suitable links:
| Events | Roles | Groups | Artifacts |
| Team Planning | Team Product Owner | Working Team | Team Backlog |