week 3 Flashcards

1
Q

What is a Scope Statement?

A

Identifies project objectives and “deliverables”

Puts boundaries around what is and what is not covered by the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Project scope checklist

A
Project objective
Deliverables
Milestones
Technical requirements
Limits and exclusions
Reviews with customer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Bottom-up approach

A

Based on estimates or elements found in the WBS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Top-down approach

A

Derived from analogy, group consensu or mathmatical relationships
-analogy, group consensus, or mathematical relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Planning fallacy

A

-Plans and forecasts that are unrealistically close to best case scenarios

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Estimating

A
  • The process of forecasting the time and cost of completing project deliverables
  • The task of balancing expectations of stakeholders and need for control while the project is implemented
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Factors influencing the quality of estimates

A
  • Planning Horizon
  • Project complexity
  • People
  • Project structure and organisation
  • Padding estimates
  • Organisation culture
  • Other (non-project) factors
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the 7 guidelines for estimating time,cost and resources

A
  • Have people familiar with the tasks make the estimate
  • Use several people to make estimates
  • Base estimates on normal conditions, efficient methods, and a normal level of resources
  • Use consistent time units in estimating task times
  • Treat each task as independent, don’t aggregate
  • Do not make allowances for contingencies.
  • Add a risk assessment to avoid surprises to stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Top-down approaches methods

A

Consensus methods
Ratio methods (sometimes called parametric)
Apportion method
Function point methods for software and system projects
Learning curves

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Bottom-down approach methods

A

Template methods
Parametric procedures applied to specific tasks
Range estimates for the WBS work packages
Phase estimating: A hybrid

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Top-down estimate intended use

A
  • Feasibility/conceptual phase
  • Rough time/cost estimate
  • Fund requirement
  • Resource capacity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Bottom-up estimate intended use

A
  • Budgeting
  • Scheduling
  • Resource requirements
  • Fund timing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Types of costs

A
  • Direct costs
  • Direct (project) Overhead costs
  • General and Admin overhead costs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly