Completion Bottlenecks: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Steps in a build that create dependencies, without which a build cannot be completed. By design, completion bottlenecks may be minimized in a given build - by various means -...") |
No edit summary |
||
| Line 7: | Line 7: | ||
*Redesigning such that a complete build or functionality, at least temporary, will be obtained even if the step is missed - because the fix can be retrofitted readily afterwards | *Redesigning such that a complete build or functionality, at least temporary, will be obtained even if the step is missed - because the fix can be retrofitted readily afterwards | ||
The intent of removing Completion Bottlenecks is to address | The intent of removing Completion Bottlenecks is to address catastrophic contingencies towards build completion - thereby improving team morale and maximizing learning opportunities. | ||
Latest revision as of 00:50, 27 August 2014
Steps in a build that create dependencies, without which a build cannot be completed.
By design, completion bottlenecks may be minimized in a given build - by various means - such as:
- Choosing a different part
- Choosing a different approach
- Redesigning such that a complete build or functionality, at least temporary, will be obtained even if the step is missed - because the fix can be retrofitted readily afterwards
The intent of removing Completion Bottlenecks is to address catastrophic contingencies towards build completion - thereby improving team morale and maximizing learning opportunities.