| Content Levels | |
| Register for free access to papers, case studies, and almost 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Abstract
This case study explores an "extreme" project conducted in a strained atmosphere, where a dysfunctional team still managed to correct a critical business issue in just nine days.
What this is
This case study explores an "extreme" project conducted in a strained atmosphere, where a dysfunctional team still managed to correct a critical business issue in just nine days.
Why it's useful
There's nothing like a previous bad experience to taint an ongoing relationship. But this case illustrates how focusing on project requirements -- the critical success factors of the project -- rather than the possible functional solutions, gave both project managers and their engineering and programming resources the flexibility and common ground to find the answers together. Communication and documentation smoothed the way for discordant teams to find those answers quicker than anyone believed was possible.
How to use it
Read the case study to learn how the project managers negotiated the scope of work to come up with a workable solution, and eventually implement a solution that exceeded the expectations created by the immediate, critical need.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy