Defining the S@S use case
S@S stays true to Scrum's origins of defining a framework to resolve complex adaptive problems through installing empirical process control theory (empiricism) within an iterative and incremental development framework. S@S preserves many of the roles and events of the original Scrum Framework.
However, as the organization continues to scale beyond the level at which a single Product Owner can manage, S@S implements new roles, organizational structures, and events that help support the coordination and integration of the underlying teams. You will see that S@S extends the original Scrum Framework by repeating small team patterns, thus creating fractal-like organizational structures.
But before we can define those new roles, events, and structures, you need to know something about the underlying theories upon which S@S is built. These theories are the topics that will be covered in the remainder of this section.
