Scrum is a very popular Agile Framework, but "out of the box" it is restricted to a single, co-located, Team working on a Single Product. Most situations are more complicated than that: multiple locations, multiple Products, multiple Teams, and so on… these situations require scaling. Most scaling frameworks extend, change, or otherwise modify Scrum in order to enable scaling... but why? Scrum is already perfect for helping a small team solve tough problems... and scaling an organization is a tough problem... so why not Scale Scrum with Scrum? In this talk I will give a quick overview of Scaling Scrum with Scrum® (SSwS), as well as comparing SSwS to both LeSS and SAFe. Come join me...

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

This must be a short and sweet presentation, given in a straightforward manner. Here is the basic idea...

First, I will need to describe unscaled Scrum:

 - the Well-Formed Team

 - Atomic, by-the-book, Scrum

 - Realistic Scrum, which splits the PO into the Team's PO and the Product's PO

Second, I will describe Leadership Teams, which are Scrum Teams that manage up-and-down the scaled hierarchy, making sure that

 - all input backlogs are combined into a single Product Backlog

 - each development-level has a Team Backlog to work from

 - the collection of all the Backlogs is providing maximum value to the Organization

Then, I will describe Communication Teams, which are Teams that manage back-and-forth team-to-team issues

 - Dependencies

 - Impediments

 - Cross-cutting issues and concerns

 - Learnings

 - Architectur 

 - Etc.

Along the way, I will compare the basic ideas of SSwS, LeSS, and SAFe; 

Learning Outcome

 Attendees will:

  • Understand the differences between by-the-book and realistic Scrum
  • Understand that Release, Program, and Project Management can be done with Scrum, but outside the Development Scrum Teams
  • Understand that there are two basic scaling problems:
    • the fundamental many-to-many relationship between Products/Projects and Teams
      • note: LeSS only considers the the 'one -to-many' case, and not the generic many-to-many case...
    • the fact that having multiple teams leads to communications issues between Teams
  • See How an Organization can use “Leadership Scrum Teams” to manage the many-to-many relationship
  • See How an Organization can use “Communication Teams” to manage the cross-team communication issues
  • Gain familiarity with other Patterns such as the "Integration and Evaluation Team" and "Community of Practice"
  • See how LeSS and SAFe compare to patterns involved in SSwS

Target Audience

This course is for those intending to use Scrum in large, complicated, environments.

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal