Getting to 2.0: The Roadmap to the Roadmap
•
1 like•362 views
I gave the keynote presentation for todays session at the FFWD Pre-Accelerator Program on the subject of how to build good software more effectively. Software development is hard for a number of reasons, not least uncertainty, complexity, communication problems. We need tools to avoid becoming another failed product & company and I outline the problem and three tools: single page strategy, value proposition design, and impact mapping that can make a major difference to chaances of success.
Recommended
More Related Content
Similar to Getting to 2.0: The Roadmap to the Roadmap
Similar to Getting to 2.0: The Roadmap to the Roadmap (20)
Recently uploaded
Recently uploaded (20)
Getting to 2.0: The Roadmap to the Roadmap
- 1. Getting to 2.0 The Roadmap to a successful roadmap
- 2. Founding Partner Activate Capital http://capital.activate.co.uk/ Managing Partner Mower/Valdemarin http://mwrvld.com/ Judge & Mentor Mass Challenge http://masschallenge.org/ CTO Playmob http://playmob.com/ Accredited Coach/Consultant/Mentor BGI Strategy Parnters http://www.bgistrategypartners.com/
- 3. “Houston we have a problem!”
- 4. What’s the 1st rule of 8% club?
- 5. Development is easy Wasting $$$ is easier
- 6. Create what customers need … and will pay for
- 7. Focus on customers & business goals
- 8. Flickr - Purple Slog - CC
- 9. Starting any business is difficult enough
- 10. “Chance favours only the prepared mind.”
- 11. The great divide
- 12. Agile gets you so far
- 13. Building good software is hard
- 14. “People learn about what they want, when you show them what they don’t want.”
- 16. “If 4 groups work on a compiler, you get a 4-pass compiler.”
- 17. "It's a trap!” 2002 2004 2009 Success 34% 29% 32% Failure 15% 18% 24% Challenged 51% 53% 44%
- 18. Lego for the Mind or Digital Cement?
- 20. “I’ve had a great idea!”
- 21. Get something to customers fast
- 23. T F Q
- 24. $ Time
- 25. Start 1.0 1.1 1.5 2.0 1 yr$
- 26. Focus on your value proposition
- 30. Customers: the acid test
- 31. MVVP MVP
- 33. Ship it already!
- 34. Focuses resources where they will have most impact
- 36. Where are we now? Where do we want to be? What must change? How can we change it? How can we measure progress?
- 37. t
- 39. What does any of this have to do with building software?
- 43. Impact Map = Road Map
- 45. You can go backwards
- 46. Where does feedback go?
- 47. Business as usual is not a recipe for success
- 48. Use business goals to drive development
- 49. Fin
- 50. Strategy on a Page Deri ap John Llewellyn Davies Value Proposition Design Alex Osterwalder Impact Mapping Gojko Adzic