Post by account_disabled on Dec 11, 2023 0:01:09 GMT -7
Scaling Scrum Caroline Becker May 16 Blog, Scrum Guide Scaling Scrum The Scrum Team should consist of up to ten people. But what to do when a larger group of specialists needs to C Level Executive List work on one project? Or if the organization decides to follow an agile way of management? To solve this problem, Scrum developers proposed Scrum@Scale.
It is a scale-free architecture to organize whole teams according to Scrum principles. Scaling Scrum – table of contents: Introduction Scrum@Scale The Scrum of Scrums Further scaling and Scrum@Scale issues Summary Introduction As soon as an organization grows, new kinds of problems appear. For instance, a drop in employee effectiveness that’s caused by complex internal structure, difficult decision-making or direction setting. Companies operating agile at the small project-team level often look to scale up. Even if many Scrum Teams are running simultaneously, they don’t need coordination as the groups operate independently. However, this does not mean that it is a multi-team Scrum.
The need for scaling comes only when most of the organization is working on one product and can synchronize its multiple Scrum Teams effectively. Most organizations that adopt agile management methods at scale choose the SAFE model, or Scaled Agile Framework. Today, however, we won’t focus on SAFE but we’ll discuss a different model called Scrum@Scale, as according to the 15th State of Agile report from 2021, it’s the second-best choice among businesses that opt for agile. Scrum@Scale In 1996, the creators of Scrum, Jeff Sutherland and Ken Schwaber, were working on a large project. As they were doing it, they were having trouble keeping smaller teams working in Scrum in sync. They came up with a way to scale it, which they eventually called Scrum@Scale.