Given the friction that has taken place so far between some team members, he opts for a 1-2-4 model to discuss possible agreements. This template is meant to ensure that everyone has a voice in the process: if you opt for a teamwork agreement, the most important thing is to ensure that your team is fully involved in the whole process. Make sure that any “itchy” or unpleasant topics will be dealt with and that the agreement will be placed in a place that is easily accessible to the team. After this starting point, Kanban teams can calculate their actual throughput in iteration stories simply by counting and averaging the number of stories delivered in previous iterations. Kanban teams then calculate their derived speed by multiplying the throughput with an average story size (usually three to five points). In this way, the SAFe ScrumXP and Kanban teams will be able to participate in the broader economic framework, which in turn constitutes the main economic context of the portfolio. SAFe teams have the choice between agile methods. Most use scrum, a lightweight and popular framework for work management. Teams developing new code also use EXTREME (XP) programming practices to emphasize agile software engineering (see Team Technical Agility and Technical Agility section) and code quality (see Built-In Quality Code Quality section). However, some teams – especially system teams, operations, maintenance, and support teams – choose to use Kanban as their primary method.
In these contexts, the speed of work, the rapid evolution of priorities and the lesser value of planning activities for the next iteration lead to this election. If not, the team refines the process or reduces some WIP limits until it turns out that a workflow state is “hungry” or overloaded. . . .