160 likes | 269 Views
The State-Based Process A Success Story . Buford D. Tackett and Buddy Van Doren, ITT industries, 1999. 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.
E N D
The State-Based ProcessA Success Story Buford D. Tackett and Buddy Van Doren, ITT industries, 1999
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
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?
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
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
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
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
The Walkthroughs - Cont. • Each DI in a state had at least 3 walkthroughs: • Advantages of the walkthroughs?
The Minutes: • Templates of the minutes could be found at the guide • Included: • Metrics collection • Decisions • Action items
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
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
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!!!)
Why this process succeed so much? • Management benefits (Management view) • User involvement • Team ownership and commitment