Here's the scenario: A new team replaces an existing team of four completely and all of a sudden. Existing team has disappeared for various reasons and even though some of them may be available in the same company, they are not freely available unless there is a disaster to manage. New team takes up a goal that is architecturally sensitive. Team has no idea how they are going to achieve it! Time is running out and there is a feeling that reputation is at stake!

Key contingencies are "Poor understanding of system", "Poor understanding of underlying technologies", "Demanding yet friendly eco-system" and "Poor / Virtually no process in place". Target is to survive and keep maintaining the system and impress with some cool features. It is portrayed that the senior manager is interested in knowing when the team could complete a particular goal of its interest.

Team does typical mistakes - "Making optimistic commitments", "Not planning time for learning activities", "Try, Fail, Discover, Try, Fail, Discover, ... Ultimately, it feels as though "Never Complete and all commitments broken!".