1

PERFORMANCE

Solution to 5 practical cases caused by the scaling process.SAFe implementation experience at Fitbit.

Anna Barzakovskaya

2

PERFORMANCE

Anna Barzakovskaya

Lead Project ManagerDevelopment Team ManagerProgram ManagerAgile Coach

3

Fitbit

4

5

Why?

6

7

8

9

10

Scaled Frameworks

Disciplined Agile 2.0A Process Decision Framework for Enterprise I.T.

Scrum of Scrums

11

Why?

Keep doing:

- Keep agility for changes and improvements of our product;

- Encourage and facilitate initiatives;

- Keep fast response and our pace of development.

Avoid:

- Chaos;- Dependences.

We believe in our ability to keep all our benefits of startup in turns of a huge company!

1212

SAFe

13

14

15

How it works in Fitbit?

1616

CASES

17

Case 1. How to control dependences

among teams…

18

Teams Flow

19

Team Level

20

Milestone Planning Goals1. Define a scope for 8 weeks;2. Define dependences between teams;3. Resolve dependences;4. Define risks;5. Resolve risks;6. Each team presents its backlog

21

Milestone planning

22

23

Risks

1.Define risks2.Create a strategy (plan)3.Prioritize4.Execution5.Monitoring

24

A Risk ExampleTeam Risk description/Cause

- Risk - EffectProbability

Impact Plan (Mitigated, Owned, Accepted, Resolved)

Risks Identification Questionnaire

Mobile Cause - Risk - EffectWe have dependency on external illustrator to create final assets - Final assets and designs won't be ready in time – Release could be postponed

Medium High Mitigated:Develop functionality on Draft assets.Owned:Brad Pit to get final assets from illustrator as early as possible, and provide final designs to the team. We need to track status and progress of final designs every day.Angelina Joly help to understand estimated time that needed to update assets to final version on backend.

Risks Identification Questionnaire (Mobile)

25

26

Case 2. How to make sure teams are working effectively in terms of

multiple teams

27

AssessmentsScrum Activities

Kanban Activities

Processes

Understanding of Scrum Roles

Fulfillment of Scrum Roles

Sprint Planning Daily Scrum

User Stories

Acceptance Criteria

Estimations - Story points

Tasking & Task estimates

Average VelocitySprint Close

Sprint Demo

Sprint Retrospective

Backlog Grooming

Sprint Burndown

Product IncrementDone DoneRisk assessment

Quality of stories

Technical debt

Feedback and adaptation

Contingency planning

Goal definitions

Capacity planning

Work scheduling and dependency managementCross-team collaboration

28

29

Case 3.Continuous improvements

30

To retrospective everything…

Milestone reviewProject managementPO+Business tandemMilestone planning retro

31

Case 4. How to keep to business priorities?

32

33

Kanban board for all projects

34

Case 4. How to enhance visibility and predictability

• Showcases

• Presentation of incoming projects for development team

• Projects roadmap

• Release train

35

36

37

38

39

40

41

42

Thank you!Questions?