CHAPTER 13Applying Complexity Thinking to Projects with Poorly Understood, Volatile Requirements

  Project Profile
Complexity Dimensions Independent Moderately Complex Highly Complex
Requirements Volatility and Risk
  • Strong customer/ user support
  • Basic requirements are understood, straightforward, and stable
  • Adequate customer/user support
  • Basic requirements are understood, but are expected to change
  • Moderately complex functionality
  • Inadequate customer/ user support
  • Requirements are poorly understood, volatile, and largely undefined
  • Highly complex functionality

Project complexity ensues when requirements are unstable and poorly understood, functionality is likely to be complex, or customer/user support is insufficient. In this chapter ...

Get Managing Complex Projects now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial