Jun 25, 2019 | 8:30 AM | Tuesday
Community: Downtown Tampa
DESCRIPTION What is Scrum@Scale®? Scrum@Scale is a framework within which networks of Scrum teams operating consistently with the Scrum Guide can address complex problems, while creatively delivering products of the highest possible value. These “products” may be h
What is Scrum@Scale®?
Scrum@Scale is a framework within which networks of Scrum teams operating consistently with the Scrum Guide can address complex problems, while creatively delivering products of the highest possible value. These “products” may be hardware, software, complex integrated systems, processes, services, etc., depending upon the domain of the Scrum teams.
Scrum@Scale enables the transformation of every division, department, and service in any organization and can efficiently coordinate an unlimited number of Scrum teams through its use of a “scale-free” architecture. Scrum@Scale naturally extends the core Scrum framework and was created by Dr. Jeff Sutherland, the co-creator of Scrum.
Adaptability allows versatility. Scrum has been successful in a wide variety of product and project contexts. It’s been used for everything from traditional software development to designing complex integrated defense systems. No single prescriptive approach could work in those different contexts. You need something that can adapt to the specific strategic context of your business.
Scrum is inherently adaptable. For example, the Retrospective event described within the Scrum Guide doesn’t tell you exactly how you have to implement it, the guide just says that at the end of retro you need to have a plan for improving the team process, puts some bounds around how long that meeting should take, and gives guidance on the purpose for the event but leaves the actual implementation to the team. As a result, we’ve seen many different practices that are successful in their respective contexts.
Adaptability supports incremental transformation. With a adaptive context all of the interconnections between the components are defined ahead of time so it doesn’t matter what happens within them as long as it meets those constraints, it still satisfies the goal of the component. That means you don’t need to have an entire solution delivered in one “big bang” at the beginning of your scaling. It frees you to use Scrum to incrementally develop the teams or business units that are most important to you or most ready for transformation. After several iterations, you'll have a full