Relates to: [[coding-pricinples-zooming-patterns.md|Coding Pricinples (zooming patterns)]] [[story-slicing-stories.md|Story_ slicing stories]] Part A - [[story-slicing-stories-as-teambuilding.md|Story_ slicing stories as teambuilding]] Part B - [[story-constraining-a-story-until-there-is-no-complexity-left.md|Story_ constraining a story until there is no complexity left]] Video: ??? - Greg Young video about software automating the majority of cases, while humans did the rest (“majority was 3 categories, with the tail end left to humans”) [[practice-constrain-with-error-messages-to-slice-stories.md|Practice_ constrain with error messages to slice stories]] Can we use this technique as an analysis technique? Benefits deliver sooner (not faster) (this is Lean / Agile) not all constraints will need to be lifted Agile ‘stop building when good enough’ Lean ’less waste’ from over-engineering lower complexity