Impact Mapping is a strategic planning skill preventing from getting lost while building products and delivering projects. Clear communicating assumptions, helping teams align their activities with overall business goals.
In this webinar, we presented an overview of Impact Mapping, outlined how it fits into Scrum-centric Agile practices, and explored some of the unique experiences and drawbacks that occur when leveraging Impact Maps in distributed teams.
Nigel Thurlow: Nigel Thurlow is a Lean evangelist, continuous improvement leader, quality advocate, Agile and Scrum coach, and ex-member of The Machine That Changed the World. With more than 25 years of international business experience across a broad spectrum of industries, he has had a strong concentration and enormous success in Enterprise Program Management, helping to develop Agile cultures. Considered by others an expert in Lean implementation and process improvement gained from a Toyota, he evangelizes quality improvement and waste avoidance. He is the principal Scrum coach and trainer at Toyota, and is leading the company’s Agile transformation using the Scrum framework.
Christian Hassa: Christian Hassa helps organizations use software development more effectively to achieve their business goals. He focuses on the collaboration of software delivery teams with business stakeholders, specializing in particular on Impact Mapping, story mapping, and specification by example. Christian has been working in software development since the early 1990s. He is managing partner at TechTalk, a .NET services and consulting company focusing on Agile coaching and delivery. In 2007, he and his team at TechTalk initiated SpecFlow, a .NET open source tool for BDD and specification by example. Christian is also the product owner for SpecMap, a story mapping tool for Visual Studio Team Services.
Luke Hohmann: Luke Hohmann is the founder and CEO of Conteneo In.(formerly the Innovation Games Company). Conteneo's enterprise software platforms and professional services merge collaboration frameworks, data analytics, and domain expertise to help organizations optimize decision making in the areas of strategy, innovation, sales, product development, and market research. Luke is also co-founder of Every VoiceEngaged Foundation, a 501(c) 3 nonprofit that helps citizens, governments, and other nonprofit organizations collaborate at scale to solve technical and wicked problems.
Answer: Both Impact Mapping and Story Mapping are a lightweight visual collaboration methods. Because the method uses card mapping to visualize goals, actor, impacts and deliverables.
Answer: Understanding the expected outcome of a requested Deliverable (User Story) helps teams delivering the most effective solution to a given problem. User Stories are the artifact at the heart of the continuing dialog between what is desirable and what is possible (Kent Back, http://c2.com/xp/UserStory.html). An Impact Map visualizes these expected outcome of user stories and also how they contribute to a higher level business goal of the organization.
Answer: Impact Mapping is a concrete visualization and collaboration method that can be also used for Risk Management (but also for other complex problem solving activities). “Risk Management” is a generic term which I wouldn’t associate any particular method with (there are many methods for risk management).