Note: the beta booklet is no longer available. See Impact Mapping book for the final version
Here is a beta version of a new book I’m working on: The Effect Mapping Handbook.
Effect Mapping is simple yet incredibly effective collaborative project planning technique, that helps teams align their activities with overall business objectives and make better roadmap decisions. Effect Mapping isn’t the first or the last solution in its space, but it is important because it fits nicely into several ongoing trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery from agile, limiting work in progress from lean software methods, build-measure-learn lean-startup style cycles, ideation, co-designing and experimentation from design thinking.
By helping organisations create better plans and manage their project objectives and road-maps more effectively, Effect Mapping helps to reduce waste, cut costs by preventing scope-creep, provides focus for projects, enhances collaboration and ensures that the right business outcomes are achieved.
The handbook is a reference guide explaining key aspects of Effect Mapping, key steps to take when facilitating Effect Mapping workshops and how this process fits into the wider software delivery pipeline.
This is a beta version – ugly but most of the content I wanted to put in is there. I’d love your feedback. You can provide feedback by filling in this form. If you’re interested in the topic, join the discussion list as well.
|
|
need an early adopter? will provide feedback if needed….