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

2.
2
PERFORMANCE
Anna Barzakovskaya
Lead Project Manager
Development Team Manager
Program Manager
Agile Coach

3.
3
Fitbit

4.
4

5.
5
Why?

6.
6‹#›
People 2007-2008
2

7.
7‹#›
People 2012
126

8.
8‹#›
People 2014
471

9.
9‹#›
1152
People YTD

10.
10
Scaled Frameworks
Disciplined Agile 2.0
A Process Decision Framework for
Enterprise I.T.
Scrum of Scrums

11.
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!

12.
1212
SAFe

13.
13

14.
14

15.
15
How it works in Fitbit?

16.
1616
CASES

17.
17
Case 1.
How to control dependences
among teams…

18.
18
Teams Flow

19.
19
Team Level

20.
20
Milestone Planning Goals
1. 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.
21
Milestone planning

22.
22

23.
23
Risks
1.Define risks
2.Create a strategy (plan)
3.Prioritize
4.Execution
5.Monitoring

24.
24
A Risk Example
Team Risk description/Cause
- Risk - Effect
Probabilit
y
Impact Plan (Mitigated, Owned,
Accepted, Resolved)
Risks
Identification
Questionnaire
Mobile Cause - Risk - Effect
We 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.
25

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

27.
27
Assessments
ScrumActivities
KanbanActivities
Processes
Understanding of Scrum
Roles
Fulfillment of Scrum Roles
Sprint Planning Daily Scrum
User Stories
Acceptance Criteria
Estimations - Story points
Tasking & Task estimates
Average Velocity
Sprint Close
Sprint Demo
Sprint Retrospective
Backlog Grooming
Sprint Burndown
Product Increment
Done Done
Risk assessment
Quality of stories
Technical debt
Feedback and adaptation
Contingency planning
Goal definitions
Capacityplanning
Workscheduling and dependencymanagement
Cross-team collaboration

28.
28

29.
29
Case 3.
Continuous improvements

30.
30
To retrospective
everything…
Milestone review
Project management
PO+Business tandem
Milestone planning retro

31.
31
Case 4. How to keep to business
priorities?

32.
32

33.
33
Kanban board for all projects

34.
34
Case 4. How to enhance visibility
and predictability
• Showcases
• Presentation of incoming projects for development team
• Projects roadmap
• Release train

35.
35

36.
36

37.
37

38.
38

39.
39

40.
40

41.
41

42.
42
Thank you!
Questions?