The Importance of Agile Scaling

[suchona.kani.z]

Agile approaches in an organization are usually Scrum and therefore the all manifesto and are based on the values ​​of "individuals" and "interactions", "collaboration with customers", "responding to change" and "functional products". Therefore, agile scaling in the sense of SAFe refers to the assumption that Scrum can be transferred to larger units consisting of five to eleven members per group.

However, when scaling agilely, several factors should be taken into account in order to be able to develop products effectively and efficiently and to establish them successfully and correctly in the company, which we can and want to only briefly address in detail. Keywords here are: user role, product owner, release definition, team size, specialization, iteration length or similar.

The question of competencies
If we have a product owner, for example, we can make initial considerations about the implementation teams. The product owner brings the user and/or technical perspective to the product.

If necessary, there are also architects in the company whose job it is to greece consumer email list specifically consolidate the technical features within the company, keep them up to date and establish innovations. We are also happy to bring them into this discussion about the skills required for the implementation team.

In addition to architects, experienced and interested employees can of course also support the discussion on the optimal team composition, both from a professional and technical perspective. We usually try not to involve managers at this point, as the first step is not about specific employees.

The question of capacities
Once we have the basic skills, the question of capacity immediately arises. As we know from Scrum, the potential performance of a team with far more than nine members quickly drops. We therefore recommend considering setting up several teams. The overhead of coordination between powerful small teams is much smaller than coordination within a team that is too large.

If we have decided on several teams, we should distribute the responsibilities between the teams in such a way that each of these teams can work as independently and solely responsible as possible within its sprint and, in the best case, can release.