why scaled agile frameworks exist and why you don't need them

Post on 22-Jan-2018

257 Views

Category:

Technology

8 Downloads

Preview:

Click to see full reader

TRANSCRIPT

neil_killickNeil Killick, 2017, All Rights Reserved

And why you don’t

need them

Why scaled agile frameworks exist

neil_killickNeil Killick, 2017, All Rights Reserved

What are “scaled agile frameworks”?

neil_killickNeil Killick, 2017, All Rights Reserved

Frameworks which enable the organisation and management of Agile Software Development

across multiple teams and/or products, programs, projects and technologies

— i.e. frameworks to enable Agile “at scale”

neil_killickNeil Killick, 2017, All Rights Reserved

SAFe (Scaled Agile Framework)

Neil Killick, 2017, All Rights Reserved

LeSS (Large Scale Scrum) neil_killick

neil_killickNeil Killick, 2017, All Rights Reserved

Nexus

neil_killickNeil Killick, 2017, All Rights Reserved

Disciplined Agile Delivery

Neil Killick, 2017, All Rights Reserved

Scrum of Scrums neil_killick

neil_killickNeil Killick, 2017, All Rights Reserved

Why do they exist?

neil_killickNeil Killick, 2017, All Rights Reserved

They address three broad scenarios:

1. Business has one agile team, wants more

2. Business has many non-agile teams, wants “Agile”

3. Business has many agile teams, wants better results

Scenario 1

1 product (pipeline)

1 Agile team

Straightforward, works well

$$$$$$$$$$$$$$$$$$ neil_killick

Neil Killick, 2017, All Rights Reserved

Agile team

Business

Feature ideas

Customer

neil_killickNeil Killick, 2017, All Rights Reserved

OK, now let’s SCALE!

$$$$$$$$$$$$$

$$$$$ neil_killick

Neil Killick, 2017, All Rights Reserved

Agile team 1

Business

Feature ideas

1 product (pipeline)

2 Agile teams

Much complexity added • decisions • team performance • coordination • prioritisation • autonomy/dependencies • technology

Customer

Agile team 2

neil_killick

Strategic project idea 3

$$$$$$$

Strategic project idea 1

$$$$$$$

Strategic project idea 2

$$$$$$$

Portfolio/PMO

Strategic project idea 4

$$$$$$$

$$$$$$$$$$$$$

$$$$$

Neil Killick, 2017, All Rights Reserved

Agile team 1Business

Feature ideas

Customer 1

Agile team 2

Customer 2

$$$$$$$$$$$$$

$$$$

Feature ideas

Agile team 3

Agile team 4

neil_killickNeil Killick, 2017, All Rights Reserved

Why you don’t need them

neil_killickNeil Killick, 2017, All Rights Reserved

1 You can experiment with good ideas from any framework

Neil Killick, 2017, All Rights Reservedneil_killick

“We are uncovering better ways of developing software…”

neil_killickNeil Killick, 2017, All Rights Reserved

2 You don’t need to solve all problems Agile addresses in one go

Why might businesses want Agile? Beat competitors to market (reduce risk of disruption and/or losing first mover advantage)

Build right thing (reduce risk of over-investment in software which is not being used or realising value)

Build thing right (reduce risk of gaining a poor reputation for quality of product, and of spending time/$$ on failure demand and technical debt)

Happier customers (reduce risk of losing customers, or gaining a poor reputation for quality of service)

neil_killickNeil Killick, 2017, All Rights Reserved

Why might businesses want Agile? Tax benefits (increased potential for earlier and more frequent capitalisation of released software as an asset)

Early revenue/cost reduction benefits/ROI

Operational efficiency (aka “get more done faster”; higher capacity, throughput and revenue per worker)

Happier shareholders (more products and features = more return)

Happier workers (reduce risk of attrition)

neil_killickNeil Killick, 2017, All Rights Reserved

Example - “We want Agile because we want to beat our competitors to market”

OK

What currently stops you from beating competitors to market?

neil_killickNeil Killick, 2017, All Rights Reserved

Projects take at least 6 months, usually longer - we don’t identify MVP’s or MMF’s - we define all scope up front, then add to it as we discover more

Deploying is hard, takes time and can only be done by one person, so we don’t do it often

We have lots of approval steps to release anything to production, so we don’t do it often

Releasing is coupled with deploying - we can’t hide unfinished features, so have to finish everything

neil_killickNeil Killick, 2017, All Rights Reserved

OK, what can we do to improve the situation?

neil_killickNeil Killick, 2017, All Rights Reserved

neil_killickNeil Killick, 2017, All Rights Reserved

Pick a project, and identify MVP’s/MMF’s for Release 1

OK, what can we do to improve the situation?

Make it easier to deploy by establishing environments, automating scripts where possible, cross-skilling team members, opening up permissions, etc.

neil_killickNeil Killick, 2017, All Rights Reserved

Pick a project, and identify MVP’s/MMF’s for Release 1

OK, what can we do to improve the situation?

Make it easier to deploy by establishing environments, automating scripts where possible, cross-skilling team members, opening up permissions, etc.

neil_killickNeil Killick, 2017, All Rights Reserved

OK, what can we do to improve the situation?

De-couple releasing (shipping) and deploying - enable frequent deployment of working product to a production-like environment which stakeholders can see/test but is not the “live” product

Pick a project, and identify MVP’s/MMF’s for Release 1

neil_killickNeil Killick, 2017, All Rights Reserved

Image credit: http://agadaenergyhealing.com/wp-content/uploads/2017/02/focus2.jpeg

neil_killickNeil Killick, 2017, All Rights Reserved

3 They are based on established enablers for agility

Neil Killick, 2017, All Rights Reservedneil_killick

• Customer-focus — in how we decide and describe what we build, and execute

• Autonomous, self-organising “feature” teams — e2e delivery

• Limit WIP, small batches — focus, deliver continuous value

• Transparency — visualise work, create shared definitions, understanding

• Continuous feedback and improvement — experiment, learn, remove wasteful steps to value creation, get better

Neil Killick, 2017, All Rights Reserved Image credit: Henrik Knibergneil_killick

neil_killickNeil Killick, 2017, All Rights Reserved

What does “Agile at scale” look like?

Neil Killick, 2017, All Rights Reserved Image credit: Henrik Knibergneil_killick

Neil Killick, 2017, All Rights Reserved Image credit: Henrik Knibergneil_killick

neil_killickNeil Killick, 2017, All Rights Reserved

What can I do TODAY to start enabling agile at scale?

Neil Killick, 2017, All Rights Reservedneil_killick

Neil Killick, 2017, All Rights Reservedneil_killick

Neil Killick, 2017, All Rights Reservedneil_killick

Neil Killick, 2017, All Rights Reservedneil_killick

Neil Killick, 2017, All Rights Reservedneil_killick

Neil Killick, 2017, All Rights Reservedneil_killick

neil_killickNeil Killick, 2017, All Rights Reserved

Thank you!

Any questions?neil_killick

Neil Killick, 2017, All Rights Reserved

top related