@miniver @lissijean One of the challenges here is that context matters. It is possible to design the bulk of a system in advance. In some cases , that makes a ton of sense. In others cases, the same approach makes very little sense. So....
@miniver @lissijean ... designers (& teams generally) would do well to understand the nature of the domain, and select their design approach intentionally. Sometimes you have to set the system in motion to understand the behaviors that will emerge. Sometimes, you have more predictable contexts...
@miniver @lissijean ...mostly, you need a mix of both approaches: parts of a system can be predictable, while others elude advance forecast. You want to have a way to set up initial structures, refactor them when needed, and then support both long arc and short arc work streams on the team.
@miniver @lissijean Where teams go wrong is sticking to a single method: all work happens in sprint, story, small increment; or all work happens via set plan.
