This preview shows page 1. Sign up to view the full content.
Unformatted text preview: other objectives. But
the information is not specified anywhere. It could all have been made available (example using
Planguage, or simple text) together with the ‘basic’ requirement.
There was absolutely no engineering culture, in this large engineering organization, to even
produce a single page of text for these requirements, which in this example were 1/8 of a $100
million project spend! Maybe the roughly $12 million (1/8 of $100 million) spent on this would have been more effectively spent if the metrics were backed up by more study and more
information. I think so. Unfortunately – this organization is typical, rather than exceptional. 3. Develop metrics with early rapid numeric and non-numeric feedback.
You will, hopefully – if you focus right - be trying to get to a critical few numeric long-term
goal levels - of performance/quality.
We believe the smartest way to the long term is to try to move towards them in early, frequent,
small ‘weekly’ steps. (Real example Figure 2)
The frequent-cycle metrics are initially estimated – to decide what pays off to do;
then measured at cycle end, to confirm or deny the estimate-hypothesis;
then evaluated against estimates, to learn from the...
View Full Document
This document was uploaded on 02/26/2014 for the course E 515 at University of Louisiana at Lafayette.
- Spring '13
- Systems Engineering