1.
From Implementing
Agile to Being Agile
Agile Evolution Lifecycle
Michal Epstein
January 2014

2.
Agile Evolution Lifecycle
Adoption
Adjustment
Advancement
Culture

3.
Adoption

4.
Adoption
Scaling
• What worked well?
• Team spirit and independency
• Dev-QA collaboration
• What required improvement?
• Insufficient visibility outside the team level
• Missing ability to plan and predict
• Difficult to improve
• Focus on tasks and estimations, less on deliveries
• Planning process was lacking

5.
Adjustment
Emphasis only on few scrum basics:
Sprint as a checkpoint for the team efficiency
Deliver MVF’s
• Work on small and well defined user stories
• Focus and WIP limit
Be an owner
• Take full responsibility over team deliveries.
Use tools for visibility and improvement

6.
Advancement
Challenge:
How to work Agile in an organization
that needs to reflect a roadmap to its customers?

7.
Advancement
Direction is clear. Path might change.

8.
Scope to fit
- What is the business value we get?
- How much are we willing to spend?
Estimate the entire release and
set strict timelines
- When will it be ready?
- How much should it cost?
Advancement
OUT
IN

9.
List
features
Business
value
Cost
Scope to fit
Prioritize
Scope to Fit
Advancement

10.
Culture
Strong
organizational
unity
(marketing, sales, R&D)
Altering
internal and
external
approach
Short cycles
and gradual
value
Happy Customers

11.
Agile Evolution Lifecycle
Culture
Agile as a Culture
Advancement
Agile beyond R&D
Adjustment
Visibility and Adjustment
Adoption
Learn and Practice

12.
Don’t let the Change
manage you..
Manage
the change!
Thank you