1 / 16

Transforming Project Success: The State-Based Process in the ATAMS Project

This case study explores the successful implementation of the State-Based Process in the ATAMS project at Cheyenne Mountain Operations Center. Faced with significant challenges and budget overruns, the project adopted an evolutionary methodology emphasizing user involvement, clear processes, and frequent inspections. The breakdown of work into Development Items (DIs) and structured walkthroughs fostered accountability and rigorous quality assurance. As a result, the ATAMS project was completed on time and within budget, yielding an almost flawless software product. This success story illustrates the power of effective project management and team commitment.

sharona
Télécharger la présentation

Transforming Project Success: The State-Based Process in the ATAMS Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The State-Based ProcessA Success Story Buford D. Tackett and Buddy Van Doren, ITT industries, 1999

  2. Backround Story • 1961 – Cheyenne Mountain Operations Center • 1981 – Cheyenne Mountain Upgrade: 6 year, $968 million • 1994 – The project is late and $1 billion over budget

  3. Backround – cont. • 1995 – New project – ATAMS (automated tracking and monitoring system) • High pressure and restrict demands: • From 20 monitors to a few • Much more functionality than planned • Shortening the time from two years to one Doomed from day one?

  4. The State-Based Process - Guidelines: • An evolutionary and incremental approach • Each increment is fully executable and demonstrable to the user • Highly user involvement • Keeping the process simple and clear • Frequent inspections meetings

  5. The State-Based Process: DI

  6. The DI's (Development Items): • Dividing the work to small development items • Each DI is treated as a separated entity • Each DI undergoing a series of state-to-state transitions • The responsibility on a DI is given to a specific development team from the beginning through the entire process

  7. The States: • 12 states +1 • Prescribed operations on the DI in each state • Transition from a state to another – • Enter and exit requirements • Flexible • State-notes

  8. The Walkthroughs: • What is it? • Purpose • Each reviewer presents his findings • Deciding an action items for each defect • Deciding whether or not DI is ready for the next state

  9. The Walkthroughs - Cont. • Each DI in a state had at least 3 walkthroughs: • Advantages of the walkthroughs?

  10. The Minutes: • Templates of the minutes could be found at the guide • Included: • Metrics collection • Decisions • Action items

  11. The Metrics: • The Metrics were made for assessing the process status • Included: • Walkthroughs duration • No. of participants • Major and minor defects or issues that were uncovered • ROI

  12. The State-Notes: • A document for each state that was continually revised • Included : • Past lesson learned • Suggestions and questions to ask • Hints and critical things to check

  13. Results: • ATAMS project deployed on time and within budget • The State-Based Process was used throughout the ATAMS project with great success • They produced an almost perfect software product (748 of 749 defects were uncovered before compilation!!!)

  14. Why this process succeed so much? • Management benefits (Management view) • User involvement • Team ownership and commitment

  15. Thank you!

More Related