Upload
nino-martincevic
View
41
Download
0
Tags:
Embed Size (px)
Citation preview
Agile Project Success
No, we satisfy the customer and deliver value!
„ Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.”
8
Agile Project Success
Satisfy the customer:
Deliver the requirements she wants!
Deliver the most valuable early!
10
The Sad Truth
But we still waste a lot of time writing a list of numerousfeatures (now calledBacklog) that coulddeliver value.
14
The Waste
But he says too: 80% of the requirements are not „required“, but only ideas orcould-haves, at best – or crap and wasted time, at worst .
Jeff Sutherland: „The idea behind a backlog is that it shouldhave everything that could possibly be includedin the product. You‘re never going to actuallybuild it all, but you want a list of everythingthat could be included in that product vision.“(From: Scrum – The Art Of Doing Twice The Work In Half The Time - 2014)
16
Get Real
It’s better to make half a product than a half-assed product.(37 Signals – Getting Real)
17
Get Real
• Ignore Details Early On • It’s a Problem When It’s a Problem • Hire the Right Customers • Scale Later • Half, Not Half-Assed • It Just Doesn’t Matter • Start With No • Can You Handle It? • Forget Feature Requests• And the most important of all…
18
Focus On Purpose
We build this product because it
• gives us a competitive advantage
• is critical and complex
• cannot be bought or outsourced
• causes sleepless nights
21
Focus On Value
Which of the 49 requirements (epics or stories) makeour vision work and have the biggest business value?
Should we even care about the other 37 right now, then?
22
We Still Think In Projects…
“A temporary organization that is needed to produce a unique and predefined outcome or result at a pre-specified time using predetermined resources.” [ PRINCE2 ]
Temporary? Pre-specified time? Predetermined resources?
24
Let‘s Think Products!
Temporary? Pre-specified time? Predetermined resources?
A product …
• has no predefined end date
• only “ends” when it has no more benefit
• changes as soon as it gets used
• has a different life-cycle than a project
25
Identify Success
What if the 12 reqs already deliver 90% of theexpected value?
Do we still need all others?May we stop here?
27
Inspect & Adapt - Everything
If your product vision works, adapt your plans, contracts and documents and continue withnext. Or make cash.
Otherwise rethink - or stop.
28
Agile Management
If the organization wants to have competitiveadvantage in todays market complexity andvelocity – it‘s an almost mandatory choice.
30
Chance Management
The mental model created by the project model does more damage than good.
Stop trying to control uncertainty, be creativeand convert it to chances and values.
31
Elastic Management
It‘s not the obligation of Agile to adapt tocontracts with fixed price and scope, but vice versa.
35
Agile Success
Doing the best we can in satisfying our customerby delivering the best possible product andoptimize our work continuously…
will give us …
36