Goal and ScopeGoal and Scope

Where are we going and what path will we be taking?

Course Outline So far in this course…

Development Process Models Fitting into the Business Process People in the Process

Next… Establishing a target and direction Estimating the costs of getting there Creating a roadmap to get there

Steps in Every Project

1. Learn Why this is being done

2. Decide What needs to be done

3. Figure out How to get it done

4. Do it

5. Look back at how well it went

Getting Started

Why – Goal Statement

What – Statement(s) of Work

How – Software Project Management Plan

Do It Did It

4 of 16

Why What How

Why Why ask why?

Establish boundaries and priorities Context, Information Objectives, Function

Objectives

Decision to do a project is usually based on return on investment feasibility study

economic and operational feasibility technical feasibility schedule feasibility

5 of 16

> Why What How

Goal Statement - purpose

Managing Expectations

Good Goal Statements explain both what and why

6 of 16

> Why What How

Goal Statement is…

States both deliverables and process

Measurable Short Doable Communicated

7 of 16

> Why What How

Example Goal Statement

“First, I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the earth. No single space project in this period will be more impressive to mankind, or more important for the long-range exploration of space; and none will be so difficult or expensive to accomplish. ” -- JFK 1961

8 of 16

> Why What How

The Need to be Clear

9 of 16

Why> What How

Statement of Work

Context Part of the SPMP Separate from the SRS

Purpose “A SOW should specify in clear, understandable terms

the work to be done in developing or producing the goods to be delivered or services to be performed by a contractor.

A SOW defines all non-specification requirements for contractor effort.

Specifications are typically referenced in the SOW but the specific qualitative or quantitative technical requirements shall not be spelled out in the SOW. “10 of 16

Why> What How

SOW Format – example 1

STATEMENT OF WORK

1. GENERAL. The Bureau of Reclamation has a requirement for …

2. BACKGROUND. 3. WORK TO BE PERFORMED BY CONTRACTOR.4. GOVERNMENT-FURNISHED MATERIALS/SERVICES.5. SUMMARY OF DELIVERABLE.6. PROJECT COMPLETION/DELIVERY SCHEDULE

6.1 REVIEW OF DELIVERABLES.6.2 ACCEPTANCE OF DELIVERABLES.

7. CONTRACTOR PAYMENT SCHEDULE8. TECHNICAL COORDINATION9. ADDRESS FOR DELIVERABLES

11 of 16

Why> What How

SOW Format – example 2

DOD-type SOW

1. Scope – what is in this SOW

2. Background3. Related Documents4. Deliverables

Sub-Tasks Reports place of work review timetable

12 of 16

Why> What How

SPMP Contents Goal Statement Process Model

management and technical

Organization Timetable and Deliverables

Work Breakdown – next topic tonight Schedule – next week’s topic

Budget13 of 16

Why What> How

Sample SPMP Table of Contentsirmc.state.nc.us/documents/approvals/reporting/SPMPLAN.doc

1. Introduction Project Overview Project Deliverables Evolution of the Software Project Management Plan Reference Material Definitions and Acronyms

2. Project Organization 2.1 Process Model 2.2 Organizational Structure 2.3 Organizational Boundaries and Interfaces 2.4 Project Responsibilities

3. Management Process 3.1 Management Objectives and Priorities 3.2 Assumptions, Dependencies, and Constraints 3.3 Risk Management 3.4 Monitoring and Control Mechanisms 3.5 Staffing Plan

4. Technical Process 4.1 Methods, Tools, and Techniques 4.2 Software Documentation 4.3 Project Support Functions

14 of 16

5. Work Packages, Schedules, and Budget 5.1 Work Packages 5.2 Dependencies 5.3 Resource Requirements 5.4 Budget Requirements 5.5 Budget and Resource allocation 5.6 Schedule 5.7 Network Diagram

6. Project Success Criteria 6.1 Network Diagram 6.2 Project Milestones 6.3 Approval Process 6.4 Acceptance Criteria 6.5 Critical Success Factors

7. Additional Components

8. Plan Approvals

9. Glossary of Terms

10. Appendices

15 of 16

Why What> How

IEEE 1058 Standard for SPMP

1. Introduction 1.1 Project overview 1.2 Project deliverables 1.3 Evolution of the SPMP 1.4 Reference materials 1.5 Definitions and acronyms

2. Project organization 2.1 Process model 2.2 Organizational structure 2.3 Organizational boundaries and

interfaces 2.4 Project responsibilities

3. Managerial process 3.1 Managerial objectives & priorities 3.2 Assumptions, dependencies &

constraints 3.3 Risk management 3.4 Monitoring & controlling mechanisms 3.5 Staffing plan

4. Technical process 4.1 Methods, tools & techniques 4.2 Software documentation 4.3 Project support functions

5. Work packages, schedule & budget

5.1 Work packages 5.2 Dependencies 5.3 Resource requirements 5.4 Budget & resource

allocation 5.5 Schedule

16 of 16

Why What> How

Where next…

deciding on the sub-tasks the Work Breakdown Structure

(WBS)

estimating size, duration, …

assigning tasks