Task analysis is part of planning
This presentation is the property of its rightful owner.
Sponsored Links
1 / 13

Task Analysis is Part of Planning PowerPoint PPT Presentation


  • 104 Views
  • Uploaded on
  • Presentation posted in: General

Task Analysis is Part of Planning. Once we have completed planning on the deliverables and contents of the deliverables , we need to plan out “how to accomplish” the deliverables. Task Analysis. Task analysis is domain dependent : build a desk plant a tree write computer program

Download Presentation

Task Analysis is Part of Planning

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Task analysis is part of planning

Task Analysis is Part of Planning

Once we have completed planning on the deliverables and contents of the deliverables,

we need

to plan out “how to accomplish” the deliverables


Task analysis

Task Analysis

  • Task analysis is domain dependent:

    • build a desk

    • plant a tree

    • 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

      • possibly application domain

Task Analysis: Defining and Sequencing the sub-activities of a Task


From requirements to work breakdown structure wbs

From Requirements to Work Breakdown Structure (WBS)

Note: date is purposely

not included, yet

  • 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 listed for a project:

    • code

    • user guide

    • support plan

    • development process document

WBS: - is the listing and sequencing of the work activities needed to produce

the required deliverables. (Note that there may be concurrent activities.)

- a way to do Task Analysis


External deliverables of a project

External Deliverables of A Project

code

user guide

Support

plan

consider these

develop.

Process

doc


A sequence of external deliverables

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


Representing in schedule form

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


Effort analysis

Effort Analysis

  • 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 size estimate has some comparable “past history” or “algorithm”

        • a common measurement: effort = size/productivity

How important are these?


A deeper work breakdown structure wbs for developing a support plan

A Deeper Work Breakdown Structure (WBS)for “Developing” A 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


Effort analysis a deeper work breakdown structure wbs of developing a support plan

Effort Analysis & A Deeper Work Breakdown Structure (WBS) of “Developing” A Support Plan

* note

Interview

Customer

for

input

Analysis

and

Develop

Outline

p-day estimate based on the assumptions:

1. size of (how much) work is estimated.

2. Productivity of the assigned person

3 p-days

1/2 p-day

Develop

the whole

Plan

Review with

Customer

O.K.

1/2 p-day

5 p-days

1/2 p-day

** - Do not forget about wait time

- how many people are required ?

- what kind of skill & background ?

Final Review

End

1/2 p- day


Assuming wbs is performed for each major deliverable

Assuming WBS is Performed for Each Major Deliverable

code

develop.

Process

doc

Support

plan

25 p-days

7 p-days

End

user guide

10 p-days

10 p-days

Assume you agree with the sequence

For each of the major deliverables, estimate the required effort in p-days via WBS

(*** these are person-days ---- want to get to individuals)


Improving on task schedule

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


Milestones in schedule

Milestones in “Schedule”

Resp.

May

June

July

Tasks

Proc

Gw

Code

Gx

User

Guide

Gy

S.Plan

Gw

Minor

Minor

Major

Major


General flow of wbs to timeline schedule

General flow of WBS to Timeline Schedule

Identify the

deliverables

For each deliverable:

identify the tasks for

completing the deliverable

Sequence the tasks

  • For each task:

  • Estimate the productivity

  • of the assigned resource

  • for effort analysis

  • For each task:

  • Estimate the needed

  • size of work for effort

  • analysis

For each task:

compute the “effort” timeline

for that task by dividing

size of work by productivity

After all the effort

for all the tasks for all

the deliverables are

computed do following

step

Lay out the effort timeline for all

the ordered tasks needed for

each of the deliverables


  • Login