Is SAFe Evil? Henrik Kniberg Lars Roost Hi! Lars Roost Henrik - - PowerPoint PPT Presentation

▶

Aug 10, 2023 110 likes •647 views

Is SAFe Evil? Henrik Kniberg Lars Roost Hi! Lars Roost Henrik Kniberg Program Manager & Agile/Lean coach Agile Change Agent Is SAFe Evil? It depends.... Is SAFe Evil? No. To Tools ls, to , tools ls, to , tools ls Henrik Kniberg

SLIDE 1

Is SAFe Evil?

Henrik Kniberg Lars Roost

SLIDE 2

SLIDE 3

Hi!

Henrik Kniberg Agile/Lean coach Lars Roost Program Manager & Agile Change Agent

SLIDE 4

Is SAFe Evil?

It depends....

SLIDE 5

Is SAFe Evil?

No.

SLIDE 6

To Tools ls, to , tools ls, to , tools ls

Henrik Kniberg & Lars Roost

SLIDE 7

Any tool can be misus used

Henrik Kniberg & Lars Roost

SLIDE 8

Scaled Agile Framework™ Big Picture

SLIDE 9

01:32

SAFe in a nutshell

10:25

SLIDE 10

SAFe

(Scaled Agile Framework)

Agile ”umbrella” –

a family of iterative, incremental methods

Scrum XP

DSDM FDD Crystal

Kanban

Henrik Kniberg

SLIDE 11

SAFe in a nutshell

Henrik Kniberg

Scrum T eam T eam backlog Story

T estable

Sprint

2-3 weeks

Program backlog

PROGRAM LEVEL TEAM LEVEL PORTFOLIO LEVEL

Product Increment

8-12 weeks

Agile Release T rain Epic

Business case

Feature

Releasable

Funnel Review Analysis Portfolio Backlog Implementing

Portfolio Kanban System

SLIDE 12

Pattern: 2-tier planning

Months

Weeks Weeks Weeks Weeks Henrik Kniberg

SLIDE 13

Pat Pattern ern: Pl Plan an on a a caden adence, e, rel releas ease e on dem deman and

Release candidates Release candidates Plan & sync Plan & sync Plan & sync Release 1.0 Release 1.1 Release 1.2 Release 1.2.1 Release 2.0 Henrik Kniberg

SLIDE 14

01:32

Example: PI-planning @ Lego

10:32

SLIDE 15

Agenda for PI planning 5

8 weeks

2 Weeks 2 Weeks 2 Weeks 2 Week

Henrik Kniberg & Lars Roost

SLIDE 16

BIG ¡ ¡

An And d this is what it looks like: e:

BI BIG Ro Room m planning

2 day ays + + 140 0 peo eople e + + experi

erimen ents, , experi erimen ents, , experi erimen ents…

SLIDE 17

¡ ¡

Af After er having been een her ere: e:

Bi Big-is ish R Room

om p

planning ing

Not enough chairs For everybody Very noisy, many left with a headache Timing overlapped with important releases in some teams But we had funny hats!

SLIDE 18

Feedb eedback on pas ast per erform rmance

Data: ¡

More! I want MORE!!!

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 19

Day ¡1 ¡

SLIDE 20

Global ¡Insights ¡ Digital ¡Child ¡Safety ¡

High level priorities:

1. ...
2. ...
3. ....

Architecture vision / priorities / constraints Data ¡Privacy ¡Law ¡

Lightning talks

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 21

Instant feedback on the event

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 22

Law of 2 feet....

T eam breakouts

Day ¡1 ¡

Can you help?

Henrik Kniberg & Lars Roost

SLIDE 23

T eams pull features from common backlog

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 24

T eams pull features from common backlog v2

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 25

T eam boards

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 26

The Program Board

Dependency mapping by teams

Day ¡1 ¡

Notice any patterns? Scrum of Scrums

Henrik Kniberg & Lars Roost

SLIDE 27

Risk Board

(per major project/program epic)

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 28

Draft plan ”fair”

4 presentation rounds: 10 min + 10 min + 5 min + 5 min

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 29

Management review

Day ¡1 ¡ Henrik Kniberg & Lars Roost

SLIDE 30

Day 2

Henrik Kniberg & Lars Roost

SLIDE 31

Day 2

Henrik Kniberg & Lars Roost

SLIDE 32

Day 2

Henrik Kniberg & Lars Roost

SLIDE 33

SLIDE 34

01:32

Should the building instructions be followed?

10:42

SLIDE 35

Shu Ha Ri

Shu = Follow the rules Ha = Adapt the rules Ri = Ignore the rules

Henrik Kniberg

SAFe = Shu-level scaling

SLIDE 36

01:32

Lego’s journey

10:45

SLIDE 37

Simplicity Collaboration

Focus on the basics

Lars Roost

SLIDE 38

SLIDE 39

So what to do with lots of them?

NEXUSTM ¡Framework ¡ Disciplined ¡Agile ¡Delivery ¡

And many, many more…

Lars Roost

SLIDE 40

Lars Roost

SLIDE 41

Lars Roost

SLIDE 42

So what have we gained?

T ransparen ency, , T ransparen ency, , T ransparen ency, , T ransparen ency, , T ransparen ency…

Lars Roost

SLIDE 43

“Solid” effects so far

Increas ased ed pred edictab ability T e T eams handle “resource e allocation”

7 out of 10: T eam Priorities are clearer 6 out of 10: I add more value

Sel elec ected ed answer ers to “Ho How has as SA SAFe affec ected ed your r daily work rk?”

3 out of 10: We spend less time on meetings 2 out of 10: We have less Work In Progress

Lars Roost

SLIDE 44

And it gives us so much more…

Momen entum Aw Awaren eness of f cha change Inter erfaces agile e teams with water erfall IT dep dep.

Lars Roost

SLIDE 45

But ¡journey ¡has ¡just ¡begun… ¡

Photo ¡by ¡Yoryo ¡García ¡ ¡

Lars Roost

SLIDE 46

01:32

The Good The Bad The Ugly

10:55

SLIDE 47

Planning as a social event Dependency Board

(aka Program Board)

Risk Board

Henrik Kniberg & Lars Roost

SLIDE 48

Don’t get stuck in Shu

Henrik Kniberg & Lars Roost

Big Bang is risky Don’t swallow the whole elephant

Watch out for Queues and Batches

Don’t believe in Hype

r Anti-Hype

SLIDE 49

Source: http://www.smbc-comics.com/?id=2475

SLIDE 50

01:32

Wrapup

11:05

SLIDE 51

Take-away points

SAFe is a toolkit. Neither Good nor Evil.
SAFe is built on Lean & Agile principles.
SAFe = Shu-level scaling.
It’s big and detailed. Take the stuff you need only.
SAFe can be useful when you have:
A bunch of teams working on the same product
A bunch of teams working on different products, but have many

dependencies.

Don’t get stuck in Shu. Experiment a lot!

Henrik Kniberg & Lars Roost

Thanks for listening!

SLIDE 52