Common Activities

Activities and Tasks in the WBS

Outline of Today's Lecture

1. Common Terms2. IEEE 1074

Standard Processes for Life Cycles

3. Example Problem creating a goal statement writing a SOW planning activities etc

Jargon Alert!Jargon Alert! Activity – A major unit of work to be

completed in achieving the objectives of a software project. An activity has precise starting and ending dates, incorporates a set of tasks to be completed, consumes resources and results in work products. An activity may include other activities in a hierarchical manner.

IEEE Std 1058 – Standard for Software Project Management Plans

Jargon Alert!Jargon Alert! Task – The smallest unit of work subject to

management accountability. A task is a well defined work assignment for one or more project members. The specification of work to be accomplished in completing a task is documented in a work package. Related tasks are usually grouped to form activities.

IEEE Std 1058 – Standard for Software Project Management Plans

Jargon Alert!Jargon Alert! Project Function – An activity that spans

the entire duration of a software project. Examples of project functions include project management, configuration management, quality assurance, and verification and validation.

IEEE Std 1058 – Standard for Software Project Management Plans

Jargon Alert!Jargon Alert! Work Package – A specification for the

work to be accomplished in completing an activity or task. A work package defines the work product(s), the staffing requirements, the expected duration, the resources to be used, the acceptance criteria for the work products, the name of the responsible individual, and any special considerations for the work.

IEEE Std 1058 – Standard for Software Project Management Plans

Jargon SummaryJargon Summary

A SPMP contains the WBS.

The WBS is made up of a list of Activities.

Activities are made up of Tasks.

Activity Planning Objectives

Feasibility Assessment Resource Allocation

Resource amounts and timing

Detailed Costing Motivation

Providing targets and monitoring achievement vs targets

Coordination between TeamsSoftware Project Management by Hughes and Cotterell

IEEE 1074 Activity Groups

Software Life Cycle Model Planning

Project Management

Predevelopment

Development

Post-Development

Integral

IEEE 1074

Software Life Cycle Model Planning1. Map the SLCM to project needs

Project Management2. Project Initialization3. Project Monitoring and control4. Software Quality Management

• Software Life Cycle Model Planning• Project Management• Predevelopment• Development• Post-Development• Integral

IEEE 1074

Predevelopment5. Concept Exploration6. System Allocation

Development7. Requirements8. Design9. Implementation

• Software Life Cycle Model Planning• Project Management• Predevelopment• Development• Post-Development• Integral

IEEE 1074

Post-Development10. Installation11. Operation and Support12. Maintenance13. Retirement

• Software Life Cycle Model Planning• Project Management• Predevelopment• Development• Post-Development• Integral

IEEE 1074

Integral14. Verification and Validation15. Software Configuration

Management16. Documentation Development17. Training

• Software Life Cycle Model Planning• Project Management• Predevelopment• Development• Post-Development• Integral

IEEE 1074 ActivitiesIEEE 1074 ActivitiesDevelopment7. Requirements

24. Define and Development Software Requirements25. Define Interface Requirements26. Prioritize and Integrate Software Requirements

9. Implementation32. Create Test Data33. Create Source Code34. Generate Object Code35. Create Operating Documentation36. Plan Integration37. Perform Integration

Example Problem

Analysis of various data sets (production equipment, sales orders) to automatically forecast raw materials needs for purchasing

Experience and a quick survey of industry revels that the needed software to be produced will be unique in nature

Approach Build it a piece at a time start with easy decision

feasibility of getting the needed data, determine algorithms, etc.

second version will address overall look and feel third version will implement most important

decision create something that concretely shows project's

value repeat until done

Step One - getting organized

create a goal statement

identify the key players keepers of data champions of the project final decision makers etc

Step Two - Write the SOW

Statement of Work Contents: Goal Scope Deliverables Criteria for Success etc

Step Three - Process Model Selection

Spiral Life Cycle1. Gather Requirements2. Design3. Code4. Test5. Repeat

Step Four - Plan Activities

How do we decide what all we need to do? Based on Past WBSs Based on Brainstorming about

Tasks Based on IEEE 1074

Step Four - Using 1074 to select Step Four - Using 1074 to select activitiesactivities

6. Plan Project Management7. Analyze Risks9. Manage the Project10. Retain Records11. Implement Problem

Reporting15. Identify Quality

Improvement Needs 16. Identify ideas and needs17. Formulate Potential

Approaches

25. Define Interface Requirements

28. Define Database29. Design Interfaces30. Develop Algorithms32. Create Test Data33. Create Source Code37. Perform Integration50. Execute V&V Tasks54. Execute the Tests

Step Five - Build the Work Breakdown

Major Activities in the WBS:1. Project Functions 2. Feasibility3. Interface Architecture4. Most Important Problem5. Next Problem6. Re-Evaluation of Project7. Development Continuation8. Deployment

Step Five - Build WBS

1. Project Functions1.1 Retain Records (10)1.2 Plan Configuration Management

(55)1.3 Perform Configuration Control (57)1.4 Collect and Analyze Metric Data

(51)1.5 Produce Internal Documentation

(61)

Step Five - Build WBS

2. Feasibility 2.1 Analysis 2.1.1 Identify Major Needs (16) 2.1.2 Formulate Potential

Approaches(17) 2.1.3 Decide what is easiest to do.

2.2 Design 2.2.1 Design Database (28) 2.2.2 Design Interfaces (29) 2.2.3 Develop Algorithm (30)

2.3 Code 2.3.1 Create Test Data (32) 2.3.2 Create Source Code (33)

2.4 Test 2.4.1 Execute Tests (54) 2.4.2 Execute V&V (50) 2.4.2.1 Is this Worthwhile? 2.4.2.2 Determine key

problem for next phase 2.4.2.3 Decide if to go

forward

Step Six - Estimate Size and Duration

Step Seven - Estimate Cost

Step Eight - Use WBS and size estimates to create project plan

Step Nine - Begin Activities 1 and 2

Next Time…

Before we can build a work plan, we need to know how much time everything will take, how many people we need, how much money… In other words, estimating