lost while building products...by clearly communicating assumptions, helping teams align their activities with overall business objectives” (http://www.impactmapping.org/) Saturday, 5 December 15
turn on a light. I can work, cook, read—long after sundown...The simple flip of a switch makes many things possible and solves many problems. When I ask developers and engineering managers what their software product does, often, they don’t tell me. They regale me details equivalent to explaining the production of electricity, starting from mining coal until the switch closes a circuit. It’s all about the technical how. Your customers...want to know the what—what is possible on their side of the metaphorical light switch when they use your product.” (http://www.estherderby.com/2015/11/what-does-your-product-do.html) Saturday, 5 December 15
centred on a business goal • Enable us to map scope from these goals • It’s a living, collaborative document • Ties in with aspects of DDD, Lean, Agile Saturday, 5 December 15
• Focus on why it’s a useful thing to build • Make It SMART • “Increase User Logins” :( • “Increase User Logins from mobile devices by 25% by March 2016” :) Saturday, 5 December 15
are directly fulfilled (eg customers) • Secondary - users whose needs must be fulfilled (eg SEO team) • Tertiary - often regulatory Saturday, 5 December 15
Describe the change, not the solution - what we want them to do, not how they do it. • eg “Make it easier to login” rather than “Implement FB login” Saturday, 5 December 15
‘cheapest’ thing • Measure against our Goal • Learn • Dynamically adjust requirements based on learnings • Don’t spend more than you need to Saturday, 5 December 15
“As a system syndrome” • Fixes “Backlog hell” • Stops pollution of the solution space • “In order to” rationale for each card • Visualise and adapt to scope creep Saturday, 5 December 15