project scope and activities info 638lecture #21

Software Project Management

Project scope and activities

INFO 638 Lecture #2 1

Project ScopeIn Traditional Project Management (TPM), it

is assumed that you can determine the goal of the project from the onsetThe adaptive or extreme management methods

examined later will allow this not to be trueCapture key project objectives in the Project

Overview Statement (POS)


Role of the POSThe POS captures key objectives of the

project, such as the Conditions of Satisfaction (COS)It should be a short document (1-2 pp)The COS should convey what the project is

expected to deliver and accomplishIt should be reviewed and updated throughout

the project – it isn’t staticIt is negotiated with the customer


Role of the POSThe POS is a communications tool among the

project manager, their development team, the customer, and the project manager’s boss (upper or senior management)

The POS is a concise statement of the project, and a summary of its justification to continue


Other ViewsThe POS and COS are often known by other

terms, like the Vision or Mission of the projectPOS and COS are Wysocki’s terminology


Generating the POSOften the POS is developed through an

iterative processThe customer makes a request for some major

aspect of the product (key set of features, for example)

The developer asks to clarify the requestThe customer provides a responseCustomer and developer agree on the responseRepeat the previous four steps until done


Non-traditional POS UsesThe POS can help understand a project even

if not starting from scratchInheriting a project from someone elseUsing a POS as a suggestion to start an

unsolicited projectUse a POS as a reference to guide your team

during development


Parts of a POSThe POS has five major sections

Problem/opportunityGoalObjectivesSuccess criteriaAssumptions, risks, obstacles

Each is typically a few paragraphs long


Problem/opportunityThis section summarizes major problems the

project will fix, and identify significant new opportunities of which it will take advantageLike the INFO 503 analysis method of the same

name, this helps prove there is significant motivation for the project to occur


GoalThe goal gives direction and purpose to the

project, summarizing how the organization will address the problems, or act on the opportunities

Don’t commit to specific time or cost goals – the scope of the project is too vague for that


ObjectivesThe objective statements elaborate on the

goal, and clarify its scope or boundariesIf you meet all the objectives, then

the goal must also be metEach objective should define an expected

outcome, the rough time frame it will be done, a measure, and the action needed to meet the objective


Success criteriaImagine the project is done, and you want to

prove how much the organization benefited from itWhat specific measures could you make to

prove the project was worthwhile? These are your success criteria

Typical criteria are increased revenue, reduced costs, improved service, etc.


Assumptions, risks, obstaclesThis is an executive summary of major

assumptions the project is based upon, key risks to manage, and foreseeable obstacles that will need to be overcomeParticularly focus on areas you might need

help managingMore details will appear in the Project

Definition Statement (PDS)


POS AttachmentsThe POS can have attachments for more

information on the projectMost common are

A risk analysis (to show more detail than given earlier), and/or

A financial analysis (such as cost-benefit analysis, feasibility studies, ROI, etc.)


POS ApprovalThe POS is submitted to middle or upper

management for approvalThe expected outcome is to continue more

detailed planning and analysis for the project


Expand POS into PDSThe Project Definition Statement (PDS)

expands on the POS in two key areasObjectives can be more specific, and use more

technical language to convey their exact intentAssumptions, risks, obstacles can cover more

details of interest to the development team


Summary of Project ScopeThe POS and PDS capture the key concepts

needed toUnderstand the basis for the project (why does

it need to exist?)Demonstrate understanding of the project

risks, context, and concernsProvide an outline of objectives the project will

(hopefully) achieveAnd therefore justify approval for the project to

continue


project scope and activities info 638lecture #21

Documents