11:12
EM.413 meeting program management James Lyneis
project design for quality
Makes me think of zen and the art of motorcycle maintenance
Grade vs quality
Grade is determined by scope
What you’re building
Quality is determined by defects
How well you built
Quality dynamics
Rework as a function of quality
Change
Emergent change
A problem with meeting existing requirements
->
Not sure that “emergent” is the best descriptor here
Initiated change
Based off a change in requirements
Am important takeaway
Adding resources can increase delay
Brook’s Law
Asking a question is like drawing a vector
The answer extrapolates from the direction of the vector
This explains why asking a question often involves additional clauses to help fine tune the vector direction so it doesn’t set the respondent off in an unintended direction
Put a model diagram on your wall
Inspired by example from F-18 project
Truly novel projects are hard to predict what requirements are actually valuable
Excess work in models?