8--Estimation
Without Chapter an accurate schedule estimate, there is no foundation for effective planning and no support for rapid development. Coming up with a perfect estimate doesn't do any good if you can't get the estimate accepted. Which of the following in not part of the software-estimation story? A. You can't tell how much a project will cost until you know exactly what it is. B. Thorough planning reduces the overall project time. C. If you want to build to a budget, you have to be very flexible about the product characteristics. D. Software development is a process of gradual refinement, so some imprecision is unavoidable. E. Estimates can be refined over the course of a project. Shortest-possible software schedules are achieved by creating the most precise estimate.
Number the following steps (1-3) based on the order in which they are performed. _____ Estimate the effort _____ Estimate the schedule . _____ Estimate the size of the product All the following are estimation tips except: A. Avoid off-the-cuff estimates B. Use software estimation tools C. Use several different estimation techniques, and compare the results D. Change estimation practices as the project progresses E. All are estimation tips A good estimate captures risk and uncertainty in a project? Which of the following is not a recommend technique for improving schedule-estimate presentations? A. Plus-or-minus qualifiers B. Peer review comments C. Ranges D. Risk quantification E. Best case, worst case, planned case, and current case Which of the following is not a suggested way to convert a size estimate into an effort estimate? 1. Estimation software 2. Lines of code conversion schedules 3. Historical data 4. Field strength estimates Algorithmic 5. approaches At some point, adding more developers slows a project down. There is a limit to how much you can reduce a schedule by adding people and requiring more overtime.
You can reduce the cost of your project and shorten your schedule by reducing the team size. Assign the most appropriate schedule type for each of the following descriptions or assumptions. Team drawn from the top 10 percent of the talent pool A. Impossible schedules Risks may be managed less actively than is ideal B. Shortest possible schedules Team drawn from the top 50 percent of the talent pool C. Efficient Schedules There is a shortest possible schedule, and you can't D. Nominal Schedules beat it Requirements are completely known Teams might not gel Anything shorter than the shortest possible schedule Requirements don't change Compressing nominal schedules can produce schedules that are of similar duration to the efficient schedules and are no more costly because of efficient development practices. Organizations reap significant b...