Difference between revisions of "Broccoli planning"
Jump to navigation
Jump to search
(Zeroth version.) |
(Holarchy) |
||
| Line 1: | Line 1: | ||
Every piece of broccoli is in itself a broccoli. It is fractal. It adheres to {{p|levels of scale}}. Takes a holistic approach, creating a planning holarchy. A holarchy, in the terminology of Arthur Koestler, is a connection between holons—where a holon is both a part and a whole. | |||
*n-tiered or fractal approach: ever evolving (rolling wave) planning on various {{p|levels of scale}}: annual, seasonal (MTP?), sprint, week, day planning. | *n-tiered or fractal approach: ever evolving (rolling wave) planning on various {{p|levels of scale}}: annual, seasonal (MTP?), sprint, week, day planning. | ||
*use seasonally adjusted {{p|hoshin kanri}} | *use seasonally adjusted {{p|hoshin kanri}} | ||
Revision as of 12:06, 29 February 2012
Every piece of broccoli is in itself a broccoli. It is fractal. It adheres to levels of scale. Takes a holistic approach, creating a planning holarchy. A holarchy, in the terminology of Arthur Koestler, is a connection between holons—where a holon is both a part and a whole.
- n-tiered or fractal approach: ever evolving (rolling wave) planning on various levels of scale: annual, seasonal (MTP?), sprint, week, day planning.
- use seasonally adjusted hoshin kanri
Sources
- http://www.ibm.com/developerworks/rational/agile/agile-mission-critical-systems-development/ tip 2: Dynamic planning
- Rolling Wave Planning