Task Analysis

1
Task Analysis

• Task analysis is domain dependent
• build a desk
• plant a tree
• survey opinions on political candidate
• write computer program
• build a road
• make a spaghetti dish
• Software project task analysis is no different
• you need domain knowledge to do this well
• computer science
• software engineering
• information technology

2
From the Requirements to Work Breakdown Structure
(WBS)

• We get 2 sets of information from Requirements
• required deliverables to the customers
• descriptions about those deliverables
• The first high level task of sequencing the
  required customer deliverables may seem simple,
  but --- consider the example list ----
• code
• user guide
• support plan
• development process document

Note date is purposely not included, yet
WBS is the listing and sequencing of the work
activities needed to produce the
required deliverables. (Note that there may be
concurrent activities.)
3
External Deliverables
code
user guide
Support plan
?
develop. Process doc
4
A Sequence of External Deliverables
code
develop. Process doc
Support plan
End
user guide
- Do you all agree ? Discuss - what do you need
to decide here. - Also decide if the sequence of
deliverables equal sequence of activities
(tasks) to produce the material
5
Representing in Schedule form
deliverables became Tasks !?
New parameter
Resp.
May
June
July
Tasks
Proc
Gw
All the same length and no overlap
Code
Gx
User Guide
Gy
S.Plan
Gz
6
Effort ?

• Estimation of Effort for each deliverable
• need to understand the subtasks required to
  produce the deliverable and any intermediate
  deliverables that may be required.
• need to break it (deliverable/task) down more
• by sub-components
• to the level where
• one person can do the task
• skill of the person can be described
• actual task can be described and estimate has
  some comparable past history or algorithm

How important are these?
7
A Deeper Work Breakdown Structure (WBS)of
Developing Support Plan
Interview Customer for input
Analysis and Develop Outline
Develop the whole Plan
Review with Customer
Not O.K.
O.K.
1 cycle only
Final Review
End
8
A Deeper Work Breakdown Structure (WBS)of
Developing Support Plan
Interview Customer for input
Analysis and Develop Outline
Based on the assumptions 1. How much work is
estimated. 2. Productivity of the assigned person

2 days
1/2 day
Develop the whole Plan
Review with Customer
O.K.
1/2 day
5 days
1/2 day
- Do not forget about wait time - how many
people are required ? - what kind of skill
background ?
Final Review
End
1 day
9
Assuming WBS is Performed for Each Deliverable
code
develop. Process doc
Support plan
25 days
End
7 days
user guide
10 days
10 days
Assume you agree with the sequence
For each of the major deliverables, estimate the
required effort in days via WBS ( these are
person-days ---- want to get to individuals)
10
Improving on Task Schedule
Having chosen specific resources
Resp.
May
June
July
Tasks
Proc
Overlapping, different length
Gw
Code
Gx
User Guide
Gy
S.Plan
Gw
11
Milestones in Schedule
Resp.
May
June
July
Tasks
Proc
Gw
Code
Gx
User Guide
Gy
S.Plan
Gw
Major
Major
Minor
Minor
12
General flow of WBS
Identify the deliverables
For each deliverable identify the tasks
for completing the deliverable
Sequence the tasks

• For each task
• Estimate the needed
• effort

• For each task
• Estimate the productivity
• of the assigned resource

For each task compute the timeline for that task
by dividing effort by productivity
After all the timelines for all the tasks for
all the deliverables are computed do
following step
Lay out the timeline for all the ordered tasks
needed for each of the deliverables