In the P4 framework, people work together in teams that are as stable as possible, with the vast majority of people belonging to exactly one team (also known as a nucleus). These teams have a common responsibility and the team members work on common goals. To do this, they exchange information with each other, complement each other and, ideally, can also take over work from other team members, e.g. in the event of overload, vacation or illness.
Other people work as extended team members (for a few Nucleus teams) or as supporters on demand or only for a short time. This more often applies to certain expert roles. (For a description of the Supporter role, see “Working Team”).
So how can these Supporters organize themselves as individuals, especially if they are not organized in a service team with others?
In our view, the “lone worker” form of organization has some disadvantages and we would always prefer team organization to this. However, if it cannot be avoided, Personal Scrum is a tool to apply the principles of Scrum to the work of an individual.
Personal Scrum and Personal Kanban
Roles
Scrum lives decisively from the principle of separation of powers. In Personal Scrum and Personal Kanban, however, this is not easily possible, which is the biggest disadvantage.
- The Personal Product Owner is the group or department manager, if applicable.
- Stakeholder: They are the Team POs of the commissioning teams or other commissioning managers.
- The Personnel Scrum Master is also. the group or department manager
Caddence and Events
- The iteration length ranges from 2 to 7 days. The iterations should fit into the team iterations and be synchronized with them.
- The planning elements are goals (personal-goals) and tasks (personal-tasks).
- Day 1:
- Review results of planned goals and tasks with the assigning team PO(s).
- Planning of next goals and tasks
- Discussion of impediments and improvements with the staff scrum master, particularly the percentage of capacity allocated to the various teams/projects
- Day 2 to n:
- Participate in Extended Team Syncs and Team Syncs as appropriate, as per the allocated percentage capacity divided by 20. One team sync may be participated in for every 20% of allocated capacity.
- Work time is allocated exactly according to the percentage capacity scheduled on Day 1. The work focus is on the completion of goals and tasks
Personal Scrum/Kanban Board
- All tasks that create significant work are on the board
- Goals/tasks for different teams are easy to recognize, e.g. they have different colors
Image by wayhomestudio on Freepik