 |
|
|
 |
|
|
|
Sometimes things are burning. Appointments exceeded, budget overdrawn. No time left for large-scale correction.That's when methods and supporting management actions must be used quite pragmatically to quickly push the buttons that provide the project with fresh air. |
|
|
|
The Initial Situation |
|
|
|
Delivery date already twice postponed, current milestones break away, permanently growing requirements and serious problems have destroyed every confidence in a successful project completion. |
|
|
| |
Unstable software status and scarcely available test environments make a constructive work impossible and scratch in the last remained piece of team morality. Every further week burns $ 100.000 with no recognizable progress for the top management. |
|
|
|
The Measures |
|
|
| |
Simple but effective |
|
|
|
Quick win 1
A location regulation and a clear definition of the project destinations creates the basis for focusing on the essential. Responsibilities create freedoms for partial successes.
"Only if you know the start and the target, you can choose the right way". |
|
|
|
Quick win 2
Understandable communication to the top management in figures and facts instead of “more incomprehensibly technical problems “ creates trust and backing. |
|
|
|
Quick win 3
Moderation of the internal communication. Solve of crusted mental structures and standard reactions. |
|
|
|
Quick win 4
Introduce from cross section responsibility for device management, configuration management and test. Through this relief of the know-how carriers and protect the developer capacity without a great knowledge transfer. |
|
|
|
The Result |
|
|
|
The team will quickly gain ground again. The earliest project closing date found out after the position fixing is held without a further delay. |
|
|
|
Today, the product is market leader in its class. |
