Planning of all work scope for the project to completion
- For traditional projects this means a master plan and master schedule for the planned work, the sequence of that work, the dependencies between the sequenced work.
- There are foundation and non-functional requirements that are derived from the project narrative or vision. These are usually pretty stable
- There are interface requirements to existing systems, products, and processes; again, pretty stable
- And then there are user requirements that are like a fuzzy cloud floating on top of these more or less stable layers. That's where agile really comes in. And, as Glen shows, these methods, each applied to their own, are reconcilable.