CS 250 [email protected] in Under 15min TranscriptSo, first thing’s first. Don't scale if you don't need to scale. So why? Why would you want to scale Scrum?Well, this is Cecilia. She's a Product Owner, and she's responsible for maximizing the value of theproduct.She has just one team working on her one product. There are also other teams in the organization, manyin fact. And they each work on their own Product Backlog and maximize the values of their product. Itcan take Cecilia's one team six whole sprints to deliver the stuff she needs. But six sprints is too long. Wecan't wait 12 weeks. If we do, she won't be able to relaunch her product in time, and a competitor couldwin over the market. The cost of waiting 12 weeks is just too great.If she had three teams working on one product, it could take her just four weeks to deliver it. In a singleorganization, all products are not created equal, so having a single Backlog where the whole organizationcan focus on the most important things is pretty paramount these days.Let's look at another example. A company wants to implement new systems or completely refactorlegacy systems. This could take months or even years to do, and it needs multiple teams from multipledepartments across the entire organization to all coordinate its efforts. It's not easy though.It's been found that as the number of Scrum Teams within an organization grows, the output – workingproduct – and the velocity of those teams begin to fall. Because there's many issues like cross-teamdependencies and even duplication of work.It became pretty obvious that a framework for effectively coordinating those teams was needed in orderto achieve that linear scalability that we strive for. [email protected] is designed to accomplish this goal viaits scale-free architecture.[email protected] simplifies scaling by using Scrum to scale Scrum. In [email protected], we separate theaccountability of the “what” with the “how”. These two cycles consists of various components, whichtogether produce a powerful framework for coordinating the efforts of multiple teams along a singlepath.The components actually allow an organization to customize their whole transformation strategy andimplementation of this. A great starting point is to implement a scalable reference model for a small setof teams that does Scrum well.As this reference model of teams accelerates, the impediments and bottlenecks that delay the delivery,produce waste, or impede the whole business agility become very apparent. And the most effective wayto eliminate these problems is to spread Scrum across the entire organization so that the whole valuestream is optimized.Let's start with the team level process. This is as per the Scrum guide with the three artifacts, the fiveevents, and the three roles. The goals of the team level process are to maximize the flow of completedand quality work, increase the performance of the team over time, and operate in a way that'ssustainable and enriching for the team, as well as accelerate the customer feedback loop.