Myths abd reality of SAFe (Scaled Agile Framework)

1. Myths and reality of SAFe
(Scaled Agile Framework)
Helen Lubchak
Aleksey Shebanov

2. About expert
CEO & Consultant
IC Agile certified professional, ICP-APM
SAFe Program Consultant Trainer
Work as IT specialist since 2005, as manager – since 2006
Have experience in outsourcing, out staffing and product
companies as project and delivery manager
Last project - opening of offline office in Kiev of one
international outsourcing company.
Coordinate and inspire local Kyiv managers community,
organize ITKaiZenClub events.
improve yourself CONTINUOSLY
CEO & Consultant @ E5
In past - Delivery Manager, Agile project manager @ Ciklum
Helen
Lubchak

3. About expert
Trainer
Certified project manager PMP, ICP-APM, TKP,
certified business-trainer.
Worked as project manager @ Vodafone, DTEK, GMS
AG, Ciklum.
Worked with the teams ups to 70 people
Implemented ITIL/ITSM, Business Continuity, ISO,
DataPrivacy in different companies
Developed PMO and Risks management systems
inside companies
improve yourself CONTINUOSLY
Aleksey
Shebanov
Head of Project Management Division, Trainer @ E5
Program Manager @ Ciklum

4. SAFe®
is a freely revealed knowledge base of
integrated, proven patterns for enterprise
Lean-Agile development.
scaledagileframework.com

5. mythbusters

6. Myth #1 – Complex framework

7. 4 configurations of SAFe

8. Essential SAFe provides the basis for
success

9. Portfolio SAFe adds Lean Portfolio
governance

10. Large Solution SAFe is coordinated by
a Solution Train

11. Some enterprises require Full SAFe

12. Myth #2 – SAFe is enterprise only

13. Essential SAFe supports small teams
up to 50 people

14. Myth #3 – You can't scale up agile—it doesn't work
like that

15. Get business results
ScaledAgileFramework.com/case-studies
30 – 75% faster
time-to-market
10 – 50% happier,
more motivated
employees
20 – 50% increase in
productivity
25 – 75%
defect reduction

21. Myth #4 – Communications are complicated.
Special between 10 000 people 

22. Program events

23. Innovation and Planning Iteration

24. PI planning
Program Increment (PI) planning is a cadence-based, face-to-face event that serves as
the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a
common mission and vision.

25. PIplanning

26. Program board

27. PI objectives

28. Inspect & Adapt workshop
The I&A workshop
consists of three parts:
1. PI System Demo
2. Quantitative
measurement
3. Retrospective and
problem-solving
workshop

29. Problem solving workshop

30. Myth #5 – Agile doesn't work with large software
projects

32. ScaledAgileFramework.
com/case-studies

33. Myth #6 – SAFe is not applicable in Ukraine

34. Project A
Payment system

35. Why do we need to scale?
# Complicated product
# ІТ team up to 100 people
# Features development caused
need of architecture scaling
# Regular releases needed

36. Test Pack UATS2
Kanban
+ UAT S3
Pack &
Deliver
Portfolio
meeting
EG1 EG2 Planning
Agile Release Train
GoLive
CodeFreeze
S1
Commitment
Release Train Engineer
Product
Owner
Vision
Release
Goals Architectural Runway
Feature
roadmap
How does it work?

37. Achievements
# Optimal release cadencies were chosen.
We had very bureaucratic hosting provider
and very high security requirements
# The requirements were systemized on
Product Management/ Product Owners
level
# The communications between the teams
was improved since we had common goal:
make one release
# The product quality increased with fixed
Code Freeze

38. Project B
Sport betting system

39. Project C
Sport betting system

40. Myth #7 – SAFe cannot be implemented fast and easy

42. At least one person in your
company must understand
what you’re doing 

43. Ближайшие тренинги
2
3 Team Kanban
Practitioner 28/10
1 Leading SAFe 27-28/10
4 Business Analysis Big
Bang 5.0 17/10 -13/12
Project management Soft &
Hard Skills 24/11, 1/12
По промокоду:
PMDay

44. Thank you for your attention!
info@e-5.com.ua
+38 (067) 790 66 11
www.e-5.com.ua
E5Trainings
E5
E5Trainings