Laws of Software Engineering · Framework
Framework
Wardley Mapping
Plot the things your system depends on. Two axes: how visible they are to the user, and how mature they are. Watch how they move over time.
How to use it. Map before you decide on strategy. Most strategy decisions get made without anyone really seeing the situation. Wardley is the discipline of seeing it.
How it gets misused. Treated as decoration. The map is the work. A pretty map without a decision is theatre.
Related
-
Framework
Cynefin
Five kinds of situation: clear, complicated, complex, chaotic, and confused. Each one needs a different response.
- Pattern Pace Layers Different parts of a system change at different rates. Fast layers innovate. Slow layers stabilise. Each layer constrains and is constrained by its neighbours.