5 why's of agile

The 5 Why’s of Agile

21 July, 2015 • Wellington • Presenter: Diana Hennessy

a.k.a The Two Year old’s Mantra

Agile is an

Attitude not a Rule21 July, 2015 • Wellington • Presenter: Diana Hennessy

Agile

Be Mindful & Present


Never forget Who you are doing it for


Agile is an


Agile

‘Agile is Dead’


‘The word “agile” has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products.’

Dave Thomas - Mar 4th, 2014http://pragdave.me/blog/2014/03/04/time-to-kill-agile/


http://pragdave.me/blog/2014/03/04/time-to-kill-agile/

‘Agile methods ask practitioners to think, and frankly, that‘s a hard sell. It is far more comfortable to simply follow what rules are given and claim you're “doing it by the book.” It’s easy, it’s safe from ridicule or recrimination; you won’t get fired for it.’

Andy Hunt - May 6th, 2015http://blog.toolshed.com/2015/05/the-failure-of-agile.html


http://blog.toolshed.com/2015/05/the-failure-of-agile.html

Failure points:

- Agile tools, not mindsets- Not inspecting and adapting- Rules and best practice, over

principles and values


‘You’re Not Agile’


So what happened to Inspect and

Adapt?21 July, 2015 • Wellington • Presenter: Diana Hennessy

What have YOU adapted lately?


Have agility in what you

do21 July, 2015 • Wellington • Presenter: Diana Hennessy

Dreyfus Model:

➔ Novice - rigid adherence to taught rules or plans

➔ Advanced Beginner - Needs small, frequent rewards; limited "situational perception"

➔ Competent - Can develop conceptual models, can troubleshoot

➔ Proficient - Driven to seek larger conceptual model, can self-correct

➔ Expert - Intuitive grasp of situations based on deep, tacit understanding, monitoring awareness

➔ Mastery - Holistic recognition, intuitive decision making, absorbed awareness


‘Doing Agile’ is not the

Goal‘Being agile’

is 21 July, 2015 • Wellington • Presenter: Diana Hennessy

Learn the skills21 July, 2015 • Wellington • Presenter: Diana Hennessy

5 Why’s


Agile?


- It delivers something useful, fast


- It delivers something useful fast- So that the user gets the benefit

ASAP



ASAP- Because using something gives you

feedback on its value




feedback on its value- So that you know you are solving the

most important user problems




feedback on its value- So that you know you are solving the

most important user problems- Because the user is the most

important person21 July, 2015 • Wellington • Presenter: Diana Hennessy



feedback on its value- So that you know you are solving

the most important user problems- Because the user is the most

important person21 July, 2015 • Wellington • Presenter: Diana Hennessy

- Because it’s flexible- Because it allows for short feedback loops & adjustment

of direction if needed- Because it allows best return of investment and

decreases the risk of wasting budget on something unnecessary

- Because it's too hard to know up-front what you want until you see it being implemented

- Because seeing things in action gives you a better idea of what it is shaping up to be rather than writing down a spec in isolation before starting the work


- Because it’s flexible- Because it allows for short feedback loops &

adjustment of direction if needed- Because it allows best return of investment and

decreases the risk of wasting budget on something unnecessary

- Because it's too hard to know up-front what you want until you see it being implemented

- Because seeing things in action gives you a better idea of what it is shaping up to be rather than writing down spec in isolation before starting the work


Let’s look again at the four values:

Individuals and Interactions over Processes and Tools

Working Software over Comprehensive Documentation

Customer Collaboration over Contract Negotiation

Responding to Change over Following a Plan


Four Values:

Are you talking to people, or adding a

comment in Jira?


Four Values:

Are you getting the feature out there to users, or documenting how to

release it?21 July, 2015 • Wellington • Presenter: Diana Hennessy

Four Values:

Are you talking to users, or ticking off requirements in

your contract?


Four Values:

Have you built what was

needed, or what was planned?


Agile is an


Agile


Agile

Thank you!@excapeartist

[email protected]


5 why's of agile

Technology

wellington presenter

diana hennessy agile

whys of agile

agile tools

agile methods

agile community

word agile

larger conceptual model