Agile

Circular diagram divided into four quadrants (Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective) with notes in surrounding boxes.
Stefan Morcov, via Wikimedia Commons (CC BY-SA 4.0)
Agile methodologies, with their short iterations and responsiveness to change, are named as well suited to unpredictable project conditions, with roots the book traces to Stafford Beer's Project Cybersyn and links forward to Lean Startup practices.
The book names Agile methodologies as a response to unpredictable project conditions: "Agile methodologies in software design, with their short iterations and responsiveness to changing requirements, are well-suited to handling erratic events in project contexts." It also draws a lineage from Stafford Beer's Project Cybersyn to contemporary practice: "the core ideas behind Cybersyn, balancing central coordination with peripheral autonomy, fostering rapid information exchange and empowering local actors feel more relevant than ever, echoing in today's agile methodologies and collaborative platforms." Outcomes are described as functioning "as critical learning artifacts within the iterative cycle of design... as emphasized in Agile methodologies and Lean Startup principles."

Related in Community

Entries this one is tied to through the book.

Methods

Books and references

Examples

In the Framework

  • Outcomes Component

In the book

  • Chapter 2, section 018 · The Temporal Paradox and Event Types
  • Chapter 3, section 025 · Cybersyn's Ghost: A Vision of Decentralized Design
  • Chapter 16, section 154 · Our creations (What?)

Mentioned in

Methods