Web hosting packages - 27.1 Using Miniature Milestones CLASSIC MISTAKE CROSS-REFERENCE For
27.1 Using Miniature Milestones CLASSIC MISTAKE CROSS-REFERENCE For another example of this, see “Track schedule progress meticulously” in Section 16.2. Have developers create their own mini milestones. Some developers will view Miniature Milestones as micro-management, and, actually, they’ll be right. It is micro-management. More specifically, it’s micro project-tracking. However, not all micro-management is bad. The micro-management that developers resist is micro-management of the details of how they do their jobs. If you let people define their own miniature milestones, you allow them to control the details of their jobs. All you’re asking is that they tell you what the details are, which improves buy-in and avoids seeming like micro-management. Some people don’t understand the details of their jobs, and those people will feel threatened by this practice. If you handle their objections diplomatically, learning to work to a miniature-milestone schedule will serve as an educational experience for them. Keep milestones miniature. Make mini milestones that are achievable in 1 or 2 days. There’s nothing magical about this size limit, but it’s important that anyone who misses a milestone can catch up quickly. If people have done generally good jobs of estimating their work, they should be able to catch up on any particular missed milestone by working overtime for 1 or 2 days. Another reason to keep milestones small is to reduce the number of places that unforeseen work can hide. Developers tend to view a week or weekend as an infinite amount of time they can accomplish anything. They don’t think about exactly what’s involved in creating the “data conversion module,” and that’s .why the job takes 2 weeks instead of the estimated one weekend. But most developers won’t commit to tackling a problem in 1 or 2 days unless they understand what it involves. To be sure you’re basing your schedule on meaningful estimates, insist on further decomposingtasksthat areabove the “infinite amount oftime” threshold for your environment. Make milestones binary. Define milestones so that they are either done or not. The only two statuses are “done” and “not done.” Percentages are not used. As soon as people are allowed to report that they are “90 percent done,” the milestones lose their ability to contribute to a clear view of project progress. Some people can’t resist the temptation to fudge their status reporting with Miniature Milestones. “Are you done?” you ask. “Sure!” they say. “Are you 100 percent done?” you ask. “Well, uh, I’m 99 percent done!” they say. “What do you mean, ‘99 percent done?” you ask. And they say, “Uh, I mean that I still need to compile and test and debug the module, but I’ve got it written!” Be fanatic about interpreting milestones strictly.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.