ch 6 - Chapter 6: The Work Breakdown Structure and Project...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 6: The Work Breakdown Structure and Project Estimation True/False 1. A work breakdown structure (WBS) provides a hierarchical structure that outlines the activities or work that needs to be done in order to complete the project scope. 2. The work breakdown structure (WBS) decomposes, or subdivides, the project into smaller components and more manageable units of work called work packages. 3. A tangible and verifiable piece of work is called a milestone. 4. Each phase should provide at least one specific deliverable. 5. Haugen (2002) suggests that the 100 percent rule is the most important criterion in developing and evaluating the WBS. The rule states: “The (parent) element must represent 100 percent of the work applicable to next level decomposition of a WBS element (child level).” 6. In much the same fashion as the claim “you can never be too rich”, when developing a WBS, one can never have too much detail in planning activities. 7. One way to ensure that the WBS has the appropriate level of detail is to ensure that the people who do the work are involved in its development. 8. The most common error in guesstimating is to be pessimistic and to overestimate the time and resources necessary to complete a project. 9. The Delphi technique is a quick and economical way to estimate the duration and costs of project activities. 10. Time boxing involves allocating a time segment for a task rather than attempting to estimate how long that task should take.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
12. Basing an estimate of activity durations on experience gained from working on similar projects is called analogous estimation. 13. Software engineering refers to a broad range of measurements for objectively evaluating computer software. 14. The three major factors in estimating an IT application are: size, complexity, and constraints and influencers. 15. Counting lines of code (LOC) is a good way to encourage efficient programming. 16. Because function points are independent of technology, they provide a way to compare projects that may use different platforms or languages. 17. COCOMO is an example of a non-parametric model because it is characterized by a usually unlimited set of named parameters. 18. The use of heuristics is based following immutable principles of project development and lead to highly accurate forecasts. 19. Research suggests that projects that use a formal estimating tool have a better chance of delivering a system that is on time and within budget. 20. If the estimates from different estimating techniques are fairly close, then you can
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 12/30/2011 for the course IT PMIT taught by Professor Andr during the Spring '11 term at Boğaziçi University.

Page1 / 10

ch 6 - Chapter 6: The Work Breakdown Structure and Project...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online