Geocities web hosting - How does a project get to be a
How does a project get to be a year late? One day at a time. Frederick P. Brooks, Jr. CROSS-REFERENCE For more on developer motivations, see Chapter 11, “Motivation.” CROSS-REFERENCE For more on detailed estimation, see “Estimate at a low level of detail” in Section 8.3. realistic. Since your milestones are fine-grained, you will find out early that you have a problem. That gives you an early opportunity to recalibrate your schedule, adjust your plan, and move on. . Fine-grain control. In Roger’s Version,John Updike describes a diet plan in which a woman weighs herself every Monday morning. She is a small woman, and she wants to weigh less than 100 pounds. If on Monday morning she finds that she weighs more than 100 pounds, she eats only carrots and celery until she again weighs less than 100 pounds. She reasons that she can’t gain more than 1 or 2 pounds in a week, and if she doesn’t gain more than 1 or 2 pounds, she certainly won’t gain 10 or 20. With her approach, her weight will always stay close to where she wants it to be. The Miniature Milestone practice applies this same idea to software development, and it’s based on the idea that if your project never gets behind schedule by more than a day or so, it is logically impossible for it to get behind schedule by a week or a month or more. Milestones also help to keep people on track. Without short-term milestones, it is too easy to lose sight of the big picture. People spend time on detours that seem interesting or productive in some vague sense but that fail to move the project forward. With larger-grain tracking, developers get off schedule by a few days or a week, and they stop paying attention to it. With Miniature Milestones, everyone has to meet their targets every day or two. If you meet most of your milestones just by working a full day and meet the rest by working an extra full day you will meet the overall, big milestones as well as the little ones. There’s no opportunity for error to creep in. Improved motivation. Achievement is the strongest motivator for software developers, and anything that supports achievement or makes progress more palpable will improve motivation. Miniature Milestones make progress exceptionally tangible. Reduced schedule risk. One of the best ways to reduce schedule risk is to break large, poorly defined tasks into smaller ones. When creating an estimate, developers and managers tend to concentrate on the tasks they understand best and to shrug off the tasks they understand least. The frequent result is that a 1-week “DBMS interface” job can turn out to take an unexpected 6 weeks because no one ever looked at the job carefully. Miniature Milestones address the risk by eliminating large schedule blobs entirely.
Looking for affordable and reliable webhost to host and run your business application? Then look no more and go to servlet web hosting services.