Lorem ipsum dolor sit amet
Stakeholders are all persons and groups affected by a system, as well as all those directly interested or involved in the product. Stakeholders are invited to Review meetings at all levels and can optionally be invited to Backlog Refinement meetings to explain their requirements.
To identify stakeholders, the P4 framework uses two different life cycles as conceptual guidelines. These are:
- the product life Cycle (from the idea to the end of product maintenance) and
- the single item life Cycle (from purchase of raw material to recycling)
For each product or system, the different stakeholders (= interest groups) can be identified from these.
Product life cycle
Item life cycle
The P4 framework distinguishes between three groups of stakeholders, which are assigned to the three areas
- Market & Business: users, customers and sales
- Technology & Architecture: suppliers, supply chain & production
- Infrastructure & Processes: managers of other areas of the organisation
Other stakeholders
In addition to the "direct" stakeholders, other, "more general" stakeholders are usually defined in requirements management. These are, for example
- the society, consisting of public and government organizations
- the environment (mostly affected by emissions and waste)
- competitors
In the P4 framework, these stakeholders are not represented by Stakeholder Needs, but by specific goals (e.g. to describe the competitive situation) or they are represented by norms and standards in the area of Quality Attributes & Constraints (QA&C).
Stakeholder map
A Stakeholder map shows the various stakeholders with their needs and the strength of their influence on the team or system.
.
The Team Calendar shows the availability of the Nucleus and Extended Team members for an Iteration. Each Team Member enters planned absences in order to determine the gross capacity of the team before (or at the latest in) the Iteration Planning. The gros capacity is used to adjust the work forecast by relating it to the team's Velocity, which significantly improves predictability.
The concept of a calendar to determine the gros capacity can also be used for Clusters and cycles, ideally based on public holidays and the longer-term vacation planning of the team members .
If the team does not work with iterations but continuously by means of Kanban, the team calendar is maintained for several weeks in advance on a weekly basis.
End
