Chapter 27: Miniature Milestones 27.1 Using Miniature Milestones (Java web server)
Chapter 27: Miniature Milestones 27.1 Using Miniature Milestones CROSS-REFERENCE For more on initiating new measures in response to a crisis, see “Timing” in Section 16.2. You can apply the Miniature Milestones practice throughout the life of a project. You can apply it to early activities such as Requirements Specification and Evolutionary Prototyping; in fact, it is particularly useful in focusing those hard-to-direct activities. For maximum benefit, the Miniature Milestones practice will be implemented at the project level by the technical lead or manager, whichever is appropriate. But individual contributors can implement it on a personal level even if their leaders don’t. The amount of detail required when implementing Miniature Milestones will give pause to whoever has responsibility for tracking those details, especially on large projects. But large projects are the projects that most commonly spin, out of control, and it is on those projects that this kind of detailed tracking is especially needed. Initiate Miniature Milestones early or in response to a crisis. Miniature Milestones provide a high degree of project control. Set them up early in the project or in response to an acknowledged crisis. If you set them up at other times, you am the risk of seeming Draconian. As with other aspects of project control, it’s easier to overcontrol in the beginning and relax control as the project progresses than it is the other way around. As Barry Bbehm and Rony Ross say, “Hard-soft works better than soft-hard” (Boehm and Ross 1989).
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.