1

Scaled agile framework: краткий обзор и рекомендации по

внедрению

2tk.

Helen Lubchak (Prykhnych)Co-founder & trainer @ E5 Delivery manager @ CiklumIC Agile certified professional

SAFe Program Consultant Trainer

In IT sphere from 2005My career pass started with customer support agent role

Act on different managerial position from 2006Last project - open office in Kyiv of international outsourcing company

Inspire IT community ITKaiZenClub in Kyiv

3

Proven

SAFe is an online, freely revealed knowledge base of proven success patterns for implementing Lean-Agile software and systems development at

enterprise scale.

6

The Levels

8

The People

10

The Backlogs

12

The Cadence

14

Quality

16

Relentless Improvement

18

Value Delivery

Get business results

BUSINESS RESULTS

30–75% faster timeto market

Happier, more

motivated employees

20–50% increase in productivity

50%+ defect

reduction

ScaledAgileFramework.com/case-studies

22

Project A

23

Why we need to scale?

• Complicated product

• ІТ team up to 100 people

• Features development caused need of architecture scaling

• Regular releases needed

25tk.

Pros and Cons

PlusScale 8+ Agile teams

Synchronization New features and architecture epics prioritization on portfolio level

Synchronization between the teams on release level

Releases Incremental releases every 4 sprints Ability to release quickly small patches

Risk management Risks and dependency management on different stages

Quality Quality control on all levels Technical debt management

Performance Focus for each release Full loading of development team

MinusRelease process ‒ Long Lead time

‒ Long deployment to Production

Quality ‒ Removing QA team from the sprint for regression testing

Performance ‒ Long grooming because of raw requirements

‒ Many not finished features because of priority changes

Process support ‒ Additional roles and rituals for SAFe process support

28

Project B

29

Why we need to scale?• Complicated product, which was not

on production yet

• ІТ team grew up to 80-90 people very quickly

• First releases and transparency in team work were needed

• No overview of whole product

31tk.

Pros and Cons

PlusScale 7+ Agile teams

Synchronization New features and architecture epics prioritization with clients involvement

Synchronization between the teams on release level and cooperation

Transparency of teams’ work for C-level management and client

Risk management Risks and dependency management on different stages

Quality Quality control on all levels Technical debt management

Performance Focus for each release Full loading of development team

MinusPerformance ‒ Many not finished features

because of priority changes‒ Not mature enough product and

development teams Process support ‒ Additional roles and rituals for

SAFe process support

Product ‒ Hard to develop comprehensive product, but not customized for main client only solution

34

What do we need for successful scaling?

TOP 5 reasons from VersionOne

36

Is there other way?

Statistics 2015 year by VersionOne

38

Next challenge?

Useful linksSAFe (Scaled Agile Framework)

http://www.scaledagileframework.com

DAD (Disciplined Agile Delivery)https://disciplinedagiledelivery.wordpress.com/introduction-to-dad/

LeSS (Large-Scale Scrum)http://less.works

Version One Agile reporthttp://stateofagile.versionone.com

41

Que

stio

ns?

helen@e-5.com.ua E5Trainings E5Trainings E5 www.e-5.com.ua

Thank your for your attention ;)