This document discusses several approaches for scaling agile frameworks to manage multiple teams and projects. It describes the Spotify model which uses small cross-functional teams called Squads to develop features. It also outlines the Scaled Agile Framework which coordinates work at the portfolio, program, and team levels. Additionally, it examines how a company structured their program and project management to continuously deliver multiple interdependent projects through decoupling releases and streamlining development.

1. 1
Scaling agile
Multiple teams
NFI - Project Management in Agile
Organizations @ Tele2

2. Scaled Scrum
PSI
• --------
• --------
• --------
• --------
• --------
• --------
Increment
backlog
Build
release
candidate,
Demo &
Release
review
meeting
Joint teams
retrospectiv
e meetingHardening
period 3
weeks
RC
PSIPSIPSI PSI
PPB 1
(Project
Portfoli
o
Board) PPB 2
Sprint
plannin
g
meeting
Daily Scrum
Weekly Scrum of Scrums
Year 1 Year 2
Inc 1 Inc 2 Inc 3 Inc 4 Inc 5
Pre-
planning
meeting
Release
planning
meeting
PSI
Fiel
d
test
Software
integration
Sprint
retrospective
One-pager release report
• Aggregated increment
burndown
• Status &progress each Epic
• Improvements to be done
• Impediments
• ----
----
• ----
----
• ----
----
• ----
----
• ----
----
• ----
----
NFI - Project Management in Agile
Organizations @ Tele2
2

3. Spotify
3NFI - Project Management in Agile
Organizations @ Tele2
https://dl.dropboxusercontent.com/u/1018
963/Articles/SpotifyScaling.pdf
Source: Henrik Kniberg & Anders Ivarsson

4. Who steers what?
4NFI - Project Management in Agile
Organizations @ Tele2
Source: Henrik Kniberg & Anders Ivarsson

5. Squad responsibilities
5NFI - Project Management in Agile
Organizations @ Tele2
Source: Henrik Kniberg & Anders Ivarsson

6. Dependencies between Squads
6NFI - Project Management in Agile
Organizations @ Tele2
Source: Henrik Kniberg & Anders Ivarsson

7. Scaled Agile Framework™ Big Picture
NFI - Project Management in Agile
Organizations @ Tele2
7

8. Portfolio Level
8NFI - Project Management in Agile
Organizations @ Tele2

9. Program Level
9NFI - Project Management in Agile
Organizations @ Tele2

10. Team Level
10NFI - Project Management in Agile
Organizations @ Tele2

11. 11
Program and projects at DeLaval
Leveransprojekt
Affärsområden
Mjukvaruleverabel
Marknadsrelease
Support
Krav-
arbete
Program
NFI - Project Management in
Agile Organizations @ Tele2

12. De Laval
Continuous Delivery of Multiple Projects
Where one release is interdependent of one or more teams
Where one release is directed at one or more projects
Inc n + 1 Inc n + 2 Inc n + 3 Inc n + 4
Project A
System Architecture
Quality Releases
Project B
Project C
Project D
System Releases
NFI - Project Management in Agile
Organizations @ Tele2
12

13. Release preparation &
verification
R n.1
Merge
Corrections
TG0 TG5
PD2Release content
decided
Which features to include in a
release, both developed, under
development and not yet started.
21 272019181716 ...12 .... 1511
GO
Decision
Verified “up and running” system version:
Feature
implementation
decision
R n.1
R n.2
Development
“Go” per
Decoupling of release projects
DesignRelease
Integration & Automated Regression Test (with load)
Streamlined Development
NFI - Project Management in Agile
Organizations @ Tele2
13

14. Product Owner Hierarchy or team?
14NFI - Project Management in Agile
Organizations @ Tele2

15. System Anatomy to manage multiple
teams
15NFI - Project Management in Agile
Organizations @ Tele2

16. 16NFI - Project Management in Agile
Organizations @ Tele2