How an IT Team Broke Free From the Requirements Morass (Case Study)
Summary: Example of a team using the Project Vision document format and recommended collaborative team Vision process to rescue their project from endless detailed requirements gathering - by going back to understand high-level "customer driven" requirements for the project first.
This case study:
What you get:
- See how even a seemingly "out of control" project can be turned around and finish successfully.
- Understand how a team focus on most important business requirements can simplify the identification of most critical detailed software requirements.
- A project profile showing a typical team problem - a plethora of requirements but limited time to implement - and how the project approached a turnaround.
- Description of the actions the team took to evaluate true current status, regroup, and get back on course.