Software Estimation/Project Scheduling Flashcards

1
Q

What is the Chaos Report?

A

a report by the Standish Group illustrating that most project fail or near fail

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

4 sources of estimate uncertainty

A

project size too small

architectural complexity

design complexity

unstable/changing requirements

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

6 Steps of the Project Planning process

A

1) establish project scope (what will be done and not done)
2) determine feasibility (can we actually do this)
3) analyze risks
4) define required resources (SW and people)
5) estimate cost and effort
6) develop project schedule

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

3 ways of estimating cost and effort for a SW project

A
  • history (compare to similar projects in the past)
  • top-down decomposition
  • empirical models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Give an example of an empirical model for SW estimation

A

Cocomo II by Barry Boehm

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

How to do estimation for Agile

A

decompose user stories into tasks

estimate task effort by assigning story points

sum the points for each user story

add user stories to the sprint backlog in order of priority until the all available effort is allocated

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

8 primary reasons for schedule overrun

A
  • unrealistic deadline
  • customer changes requirements but schedule not allowed to change
  • honestly underestimated effort
  • unpredictable and/or unconsidered risks
  • technical difficulties that were not forseeable
  • human difficulties
  • miscommunication among staff
  • unmonitored schedule breakage (the project has gone off schedule)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

7 project scheduling activities given a WBS

A

compartmentalize - group similar tasks together

determine interdependency of tasks

allocate time to tasks

parallelism clamped by teams size

defined assignments/responsibilities -assign tasks to people

defined outcomes - what proves a task is completed

defined milestones

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

What is the 40-20-40 rule?

A

40% of the time = front-end analysis
20% of time = coding in unit tests
40% of time = I&T, V&V, package, shipping

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

2 methods for task scheduling

A

PERT chart

CPM (critical path method)

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

In regards to scheduling, what is optimistic time?

A

time a task takes in which there are no delays (i.e. better than normal)

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

In regards to scheduling, what is normal time

A

the time you would expect a task to take with a typical amount of delays

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

In regards to scheduling, what is pessimistic time

A

more delays than normal but not catastrophes

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

In regards to scheduling, what is slack time

A

the maximum time you can delay the start of a task without delaying the delivery of the product

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

In regards to scheduling, critical path time

A

the total time it takes to complete the tasks in the UC main scenario (no slack time here)

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

In regards to scheduling, what is lead time

A

the amount of overlap between two tasks

17
Q

In regards to scheduling, what is lag time

A

the amount of delay between two tasks

18
Q

what is the Earned Value Method?

A

a metric for tracking project process

1) assign costs to each task
2) define earning rules (earn points when task completed)
3) compare % of timeframe completed with % of points earned