Many software teams try to get more done - but if you're getting the wrong stuff done, or not shipping it to customers, it can't make an impact! Some questions to ask to make more of a difference to your customers with your software development efforts.
14. What’s most important,
right now?
IMPACT DRIVEN DEVELOPMENT - STEP 1
● Who are your customers? What matters most to them?
● What are the current business objectives? Why?
● What are the weakest things about your product right now?
Example: getting more customers, keeping customers, saving time
@richardw1001 |
nhance.today
15. What’s most important,
right now?
IMPACT DRIVEN DEVELOPMENT - STEP 1
● When you improve the weakest thing enough, it will stop being the priority
● You’ll need to re-assess as you go along
● You’ll need a planning process that lets you steer as you go
@richardw1001 |
nhance.today
16. What does better look like?
IMPACT DRIVEN DEVELOPMENT - STEP 2
@richardw1001 |
nhance.today
17. What does better look like?
IMPACT DRIVEN DEVELOPMENT - STEP 2
● What are you hoping to see? Why?
● There’s always room for improvement - “done” is misleading as a concept
● How much better is “good enough - for now”?
@richardw1001 |
nhance.today
18. What does better look like?
IMPACT DRIVEN DEVELOPMENT - STEP 2
● What could you measure to see improvements?
● How can you measure these easily?
● What are their current scores?
Examples: user feedback, analytics, performance metrics, survey scores...
@richardw1001 |
nhance.today
20. Where’s the leverage?
IMPACT DRIVEN DEVELOPMENT - STEP 3
● Pareto principle - “20% (or less) of inputs lead to 80% (or more) of outputs
● Which parts add the most value? How can you focus on these?
● Which parts take the most effort? How can you reduce or eliminate these?
How: break down metrics, simplify design, filter designs for cost/value ratio
@richardw1001 |
nhance.today
21. How can we deliver an
outcome sooner?
IMPACT DRIVEN DEVELOPMENT - STEP 4
@richardw1001 |
nhance.today
22. How can we deliver an
outcome sooner?
IMPACT DRIVEN DEVELOPMENT - STEP 4
● Measure and optimise for cycle time
● That is mainly driven by:
○ Architecture/technical strategy
○ Team autonomy
○ Delivery/release strategy
● Focus on purpose, eliminate waste
@richardw1001 |
nhance.today
23. How can we deliver an
outcome sooner?
IMPACT DRIVEN DEVELOPMENT - STEP 4
● Good quality strategy, so you can release confidently at speed
● Design for releasability - feature toggles, rollout model, canary releases, etc
● Collaborate - eliminate hand-offs and build as a team
@richardw1001 |
nhance.today
24. Impact Driven Development
IN SUMMARY
● What’s most important, right now?
● What does better look like?
● Where’s the leverage?
● How can we get an outcome sooner?
@richardw1001 |
nhance.today
25. Impact Driven Development
IN SUMMARY
● What’s most important, right now?
● What does better look like?
● Where’s the leverage?
● How can we get an outcome sooner?
In association with
101ways.com
Brought to you by
nhance.today
Editor's Notes
Building software is expensive
Businesses build for impact!
Competitive advantage
Developers build to be proud of impact
Title of scrum book
Well-intentioned, but misinterpreted
Can lead to nightmare of dark agile - weaponised against the team
Is the wrong question
Better version - doesn’t matter how much work you do, matters what impact it has
The main focus traditionally - assembly lines, industrial revolution, Taylorism,
What really matters - what’s the real objective - what does the stuff you did lead to?
7th principle in agile manifesto
Depends how you define working
Definition of done
Piling up unreleased work, batches
Linear flow
No feedback loop
Means released, and getting good results
Might need iteration to achieve this