From Implementing Agile to Being AgileAgile Evolution Lifecycle

January 2014

Michal Epstein

Agile Evolution Lifecycle

Adoption

Adjustment

Advancement

Culture

Adoption

Adoption

• 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

Scaling

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

Advancement

Challenge:

How to work Agile in an organization

that needs to reflect a roadmap to its customers?

Direction is clear. Path might change.

Advancement

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?

OUT

IN

Advancement

List features

Business value

Cost

Scope to fit

Prioritize

Scope to Fit

Advancement

Culture

Strong organizational

unity (marketing, sales, R&D)

Altering internal and

external approach

Short cycles and gradual

value

Happy Customers

Agile Evolution Lifecycle

CultureAgile as a Culture

AdvancementAgile beyond R&D

AdjustmentVisibility and Adjustment

Adoption Learn and Practice

Don’t let the Change

manage you..

Manage

the change!

Thank you