1. 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

2. 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

3. From 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 listed for a project: –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.) - a way to do Task Analysis

4. External Deliverables of A Project Support plan code develop. Process doc user guide consider these

5. A Sequence of External Deliverables Support plan code develop. Process doc user guide End 1.- Do you all agree ? Discuss - what do you need to decide here. 2.- Also decide if the sequence of deliverables “equal” sequence of activities (tasks) to produce the material

6. Representing in “Schedule” form Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGz Gy Gx Gw New parameter All the same length and no overlap Deliverables became Tasks !

7. 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?

8. A Deeper Work Breakdown Structure (WBS) for “Developing” A Support Plan Interview Customer for input Analysis and Develop Outline Review with Customer Develop the whole Plan Final Review End 1 cycle only O.K. Not O.K.

9. Effort Analysis & A Deeper Work Breakdown Structure (WBS) of “Developing” A Support Plan Interview Customer for input Analysis and Develop Outline Review with Customer Develop the whole Plan Final Review End O.K. 1/2 p-day 3 p-days 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 ? p-day estimate based on the assumptions: 1. size of (how much) work is estimated. 2. Productivity of the assigned person * note

10. Assuming WBS is Performed for Each Major Deliverable Support plan code develop. Process doc user guide End 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) 7 p-days 10 p-days 25 p-days

11. Improving on Task “Schedule” Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGw Gy Gx Gw Overlapping, different length Having chosen specific resources

12. Milestones in “Schedule” Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGw Gy Gx Gw Major Minor

13. 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 needed size of work for effort analysis For each task: -Estimate the productivity of the assigned resource 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