Map Your Improvement Strategy Because That Expert You Hired Has No Magical Bullets

Written by ppito | Published 2019/11/04
Tech Story Tags: agile | wardley-maps | improvement-strategy | beware-of-experts | pattern-matching | production-management | latest-tech-stories | hackernoon-top-story

TLDR Wardley Maps are typically created to model the creation of a product or service, where the anchor is obvious — the end user. The anchor is the delivery function of a programme/project/product. In this context of driving improvements of an agile delivery, the components are capabilities and other aspects needed for delivery (such as tools or artefacts) Chain the components using a dependency or value chain to form the Y axis of the map. Position the components vertically based on their value or visibility. Position them horizontally based on a form of evolution. Evolution phases suggested by Simon Wardley for capabilities : Novel, Emerging, Good and Best.via the TL;DR App

no story

Written by ppito | Learning agile while practicing. Programmer, husband, father. Cyclist wannabe. I try to be the best
Published by HackerNoon on 2019/11/04