David Lemmer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
*[[David Lemmer Log]] | |||
*AFIT - Air Force Institute of Technology . Ohio. | *AFIT - Air Force Institute of Technology . Ohio. | ||
*Systems Engineering Masters - model-based systems engineering. Systems engineering - before it used to be document based. | *Systems Engineering Masters - model-based systems engineering. Systems engineering - before it used to be document based. | ||
| Line 6: | Line 7: | ||
**Number of modules successfully produced | **Number of modules successfully produced | ||
**Metric - number of people, and proper teams that showed up. | **Metric - number of people, and proper teams that showed up. | ||
*Key thing in modular breakdown - map out the boundary - dimensions, inputs, outputs, where it's going. Specify only critical interfaces and properties. | |||
*End up with a redundancy of solutions - of | |||
Revision as of 22:28, 14 July 2020
- David Lemmer Log
- AFIT - Air Force Institute of Technology . Ohio.
- Systems Engineering Masters - model-based systems engineering. Systems engineering - before it used to be document based.
- Extreme_Enterprise_Event_Design#Pre-Preparation
- Start with Definition of Done
- Metrics - how do you measure if the process went well.
- Number of modules successfully produced
- Metric - number of people, and proper teams that showed up.
- Key thing in modular breakdown - map out the boundary - dimensions, inputs, outputs, where it's going. Specify only critical interfaces and properties.
- End up with a redundancy of solutions - of