Making Agile Pay
-
Upload
ianibbo -
Category
Technology
-
view
457 -
download
0
description
Transcript of Making Agile Pay
![Page 2: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/2.jpg)
Disclaimer
I reserve the right to give you advice which conflicts with the ‘norm’.Based on my experiences not set texts!
I reserve the right to be heretical WRT ‘sacred’ texts’
Culture eats strategy for breakfastSo pick only those battles you can win..
2
![Page 3: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/3.jpg)
Devt. Cost– what’s the big deal?
Customer “changes their mind”Misinterpretations – requirements
Takes longer than expected – cascading impacts – badly estimated?
Testing reveals too many problems – cost of rework
3
![Page 4: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/4.jpg)
There’s a hole in my bucket..
Reduce scope for misinterpretations
Enable / work with / assume change
Improve levels of inspection/ testing
Reduce financial exposure per delivery
4Agile !!
![Page 5: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/5.jpg)
Impedance mismatch
Expectations..?!
5
I don’t have to make commitmentsI don’t have to document anything
I pay less for developmentI’ll get stuff fasterI can change my mind at any time
![Page 6: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/6.jpg)
Impedance mismatch
Expectations..?!
6
We can iterate over the requirementWe’ll decide at the last possible moment
Chaos is loomingI must pin them to a planI don’t know WHAT I’m getting
![Page 7: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/7.jpg)
Fog
XP versus scrum versus DSDM versus ..
Terminology
Religion
DSDMCommon reference
Business – focused terminology
UK culture ..
7
![Page 8: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/8.jpg)
The road to hell..
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
8
Agilemanifesto.org
![Page 9: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/9.jpg)
And..?
This will only work if:
We can prioritise (negotiate!)
You’re available to collaborate
We keep the plan fluid
9
![Page 10: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/10.jpg)
Don’t burn moneyPrioritisation – the right to negotiate
IncrementalFixed scope
10
sometimes16%
rarely 19%
never45%
often13%
always7%
Source: Standish Group : Chaos Chronicles 2000
![Page 11: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/11.jpg)
Prioritisation
You can’t have EVERYTHING
If you can’t prioritise then (arguably) you have no business case
Useful: Imagine if...
11
![Page 12: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/12.jpg)
PM – same as it ever was..
Controlling the project
Planning, estimating, budgeting
Managing change – negotiating priorities
Managing risk
Managing quality.
12
![Page 13: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/13.jpg)
PM Imperatives: Planning
13
OR
![Page 14: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/14.jpg)
Change Control
Agree in/ out of time-box boundaries
Context: renegotiating priorities
Explicit Trade offs
Central log, visible record / history
AssumptionsEstimates to hand
Velocity is known
Decision is objective
14
![Page 15: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/15.jpg)
Contract / Agreement
Essential:Change control – boundariesprioritisation
Deliverables – what paid for
Quality – nature of ‘re-work’
15
![Page 16: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/16.jpg)
Contract / Agreement
Are the right people in the room?
Authorised for cost sign off?
Highlight what WILL be done
Must haves
Timescales
Preventing over-spends
16
![Page 17: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/17.jpg)
Making the transition
17
![Page 18: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/18.jpg)
Caution..
Knee-jerk response .. Not a panacea – culture?Complexity? Skills? Budgets/Expectations?
18
![Page 19: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/19.jpg)
Realistic Targets
Avoid ‘cultish’ terminology
Use the dictionary not a creed..
Impact of IT organisation business change
Benefits management
Agree benchmark/ targets.
19
![Page 20: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/20.jpg)
Stakeholder buy-in
How much will this cost?
What will be delivered?
How will I know whether you’re on track
How will I know that what you’re building will work.
20
![Page 21: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/21.jpg)
Roadmap
Small projectsMinimal risk
Piecemeal technique adoption
Perceived wisdom
Critical projectsSuccess better recognised
Easier to get broader support
21
![Page 22: Making Agile Pay](https://reader033.fdocuments.in/reader033/viewer/2022052909/559871ab1a28ab8f2e8b4577/html5/thumbnails/22.jpg)
Implications
Collaborative culture Stakeholder time!
TRUST
Decisions ‘at last minute’ rather than up front
Freedom to honour the ‘spirit’ of the contract
Team skill sets
22