richard cowling - agile guild - a history, the reasoning behind, and the principles of agile v6
TRANSCRIPT
![Page 1: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/1.jpg)
Agile GuildAgile, a Mechanism for Managing Stakeholder
Expectations; and focussing the delivery
Richard CowlingPrincipal SEiT, EMIS Health, PCC
![Page 2: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/2.jpg)
Richard Cowling
1982
1987
1990
1992
1993
1995
20042008
2012
2014
2010
![Page 3: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/3.jpg)
The continuing “Software Crisis”
• It’s difficult to deliver software• It’s often late and over budget• It’s often bad
• Over the years - you’ve only to watch the news or read a newspaper … or visit somewhere software is used to know this! See Wikipedia, or visit here : http://www.computerworld.com/article/2533563/it-project-management/it-s-biggest-project-failures----and-what-we-can-learn-from-them.html
![Page 4: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/4.jpg)
Why?• Lots of reasons
– Lack of discipline– Abstract intangible nature– Highly conceptual– People and perception filters– Underestimating complexity– Underestimating size– Changing world / changing minds / moving targets– Lack of visibility– Creeping scope – Misunderstandings / Ambiguity / Communication interference– Failing to engage key stakeholders– Chinese whispers
![Page 5: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/5.jpg)
Communicating Specifications
![Page 6: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/6.jpg)
Model Traditional Engineering / Manufacturing
• Initial attempts to solve the “Software Crisis” – on the face of it seemed rational and sensible– Bring in engineering rigour, discipline and create
“Software Engineering” – modelled on “Civil Engineering”, “Electrical Engineering”, “Mechanical Engineering” …
– Engineering means “specify, plan and design”– And utilise “Project Management” best practice …
follow standards and procedures – process models - CMM etc.
![Page 7: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/7.jpg)
Focus on Specification & Design First• “Before writing a line of code let’s just be sure
we know exactly what it is we’re developing – let’s first try to fully describe the system – if we put this upfront effort in now – it’ll save us time later!”
• Business Analysts head off eliciting and writing down requirements for months and months until they finally achieve analysis paralysis and stop – then the design phase begins … WATERFALL ...
• Lots of documents get written …
![Page 8: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/8.jpg)
Taught at Uni :
• Software should be planned and designed and manufactured like anything else – Bridges– Shoes– Tractors– Tower blocks– Engines– Boats
• Thing is, they’re all visible concrete things.
![Page 9: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/9.jpg)
Turns out delivering software is
• More like playing chess
• Than building a bridge.• And you DON’T PLAN a game of chess
move my move – you HAVE A GOAL and STRATEGY.
![Page 10: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/10.jpg)
Trad. Manufacturing/Factory Model : QC Inspector is Too Late
![Page 11: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/11.jpg)
Big-Bang / Waterfall Delivery
![Page 12: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/12.jpg)
Why … Again?• Lots of reasons
– Lack of discipline– Abstract intangible nature– Highly conceptual– People and perception filters– Underestimating complexity– Underestimating size– Changing world / changing minds / moving targets– Lack of visibility– Creeping scope – Misunderstandings / Ambiguity / Communication interference– Failing to engage key stakeholders– Chinese whispers
![Page 13: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/13.jpg)
Another School of thought …
![Page 14: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/14.jpg)
Sir Francis Bacon 1561 - 1626
• Scientific Method
![Page 15: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/15.jpg)
What about this guy ?
![Page 16: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/16.jpg)
William Edwards Demming 1900-93
• Quality Management, Continual Improvement, Toyota Lean Manufacturing – the Japanese Industrial Boom - KAIZEN
![Page 17: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/17.jpg)
So, there’s an alternative approach to getting things done – and done well!
• The thinking and work done by Demming starts to get applied to thinking about how to develop software.
• IT’S ALL ABOUT THE FEEDBACK LOOP AND MAKING FULL USE OF THE ALL THE FEEDBACK.
• Tom Gilb’s EVO and Barry Boehm’s Spiral
![Page 18: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/18.jpg)
Feedback Loops
![Page 19: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/19.jpg)
Incremental Construction
![Page 20: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/20.jpg)
Agile – the incremental approach toolkit
• Agile provides the tools to enable incremental approaches, principles, and benefits
![Page 21: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/21.jpg)
Benefits should be …• Early and continual verification and validation• So, that’s building quality in - and de-risking project/product• Incremental Acceptance is possible and can be used to
manage change.• Short feedback loops focus more on expectations than
requirements – so genuine customer/stakeholder satisfaction AND allow you to track the moving targets.
• Lean – waste and rework restricted to last small increment.• Visibility and predictability – rolling re-estimation – a
continual conversation.• Is its own early warning system.• Relieves deadline pressure.• Continual Improvement of processes and practices
![Page 22: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/22.jpg)
Quality!
What is quality?
![Page 23: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/23.jpg)
What does Software Quality mean?
• The amount of stakeholder satisfaction• How well the expectations of the
customers / users / stakeholders are met or exceeded.
• How well the requirements have been met – depends on the how good the requirements are …
• “Fitness for Purpose” … ???
![Page 24: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/24.jpg)
Remember that feeling …
• You ordered your favourite meal at a new restaurant …
• It wasn’t what you were expecting – you were disappointed.
• Your perception of the quality of the meal, and establishment is affected – to you it was not a high quality experience.
• The menu is like the written requirements.• The proof is in the eating.
![Page 25: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/25.jpg)
Conclusion ...
![Page 26: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/26.jpg)
Benefits should be …• Early and continual verification and validation• So, that’s building quality in – and de-risking
project/product• Incremental Acceptance is possible and can be used to
manage change.• Short feedback loops focus more on expectations than
requirements – so genuine customer/stakeholder satisfaction AND allow you to track the moving targets.
• Lean – waste and rework restricted to last small increment.• Visibility and predictability – rolling re-estimation – a
continual conversation.• Is its own early warning system.• Relieves deadline pressure.• Continual Improvement of processes and practices
![Page 27: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/27.jpg)
Failure Reasons… Again?• Lots of reasons
– Lack of discipline– Abstract intangible nature– Highly conceptual– People and perception filters– Underestimating complexity– Underestimating size– Changing world / changing minds / moving targets– Lack of visibility– Creeping scope – Misunderstandings / Ambiguity / Communication interference– Failing to engage key stakeholders– Chinese whispers
![Page 28: Richard Cowling - Agile Guild - a history, the reasoning behind, and the principles of Agile v6](https://reader035.vdocument.in/reader035/viewer/2022062522/58a336891a28ab9b6d8b59eb/html5/thumbnails/28.jpg)
Questions!• Are we using Agile, as a mechanism to manage
stakeholder expectations; and focus the delivery on the moving target?
• Are we feeling the benefits of incremental small step construction … (sprinting)
• Are we more about “expectations” or still thinking in terms of “requirements”.
• Are we more about project “Strategy” or “Plan”?• Is Incremental Acceptance what we do – should it be?• Is Sprint Review being made maximum use of – in terms
of feedback and adapt?