At this milestone, the product is formally turned over to the operations and support groups. Typically, the project team either begins work on the next release or disperses to other development projects. Each milestone is a synchronization point where the team is re-calibrated to customer expectations. Milestones are managed using the known tradeoffs of resources, features, and schedule. Versioned releases, rather than including every feature the first time.
Technology rapidly changes the capabilities of the PC-empowered user.
Versioned releases are necessary to leverage investments made in PC-based computing environments. This process model produces better decisions, less rework, higher morale, and a higher quality product. And, by addressing support and performance issues as part of the development process, it can lower the risk of rolling out new solutions and lower the cost of ownership.