Impact Mapping and Story Mapping

Impact Maps and Story Maps: delivering what really matters from Christian Hassa

Impact Mapping

A methodology meets its limits when it meets people - Alistair Cockburn

Sanjay Kumar on Linkedin

Adopting #Scrum is NOT the primary goal, nor is adopting #Kanban or #SAFe. Not even #Agile.

The primary goal is to generate #better business outcomes in a predictable and sustainable manner, followed closely by creating a work environment that motivates people towards excellence and helps them grow professionally.

Agile (and the chosen process) is the enabler for these goals, not the goal in itself. In other words,#Process must subordinate to #Outcomes, not the other way around.

If it does not, feel free to switch, customize or evolve your current process. If you do not, your agility may be severely limited... DOES NOT matter what fancy name you call it.

Agile Transformation Woes

1. Inadequate or poorly defined reference.
2. Poorly designed training program.
3. Disconnect between old and new models.
4. Inability to choose the right candidate projects.
5. Forcing agile to initiatives that could go waterfall.
6. Ignoring the business, vendor and support teams as part of the transformation.
7. Not providing a career path for Project Managers, Business Analysts, Software Testers or leaving it to the judgement of individual teams.
8. Management using agile to drive their own agenda.
9. Management using agile metrics to compare and drive teams.
10.