1

What is a project?

What is an operation?

Project Management Planning Activities

Anil B. Jambekar8/27/2004

2

Project= Schedule +Scope +Budget +Quality

Success = (((Process +(Skills +Techniques) +Tools) *Accountability) *Discipline)

3

Elements of project plan

3 W's

Why the reason for undertaking the project

What a description of objectives to be attained

When a time line for key portions of the project

3 H's

How much what the project expected to cost

Hazards what might go wrong

How how will the team function

4 C's

Critical success factors a brief listing of what should be monitored

Communication plan who needs to know what and when

Collection of knowledge

what do the team members bring to the project

Commitmentwho is involved and can make timely decisions

4

Define: ScopePlan:

Master plan- Key project milestones and deliverables and project phases and project organization and accountability matrixPhases, deliverables, tasks, milestones and resourcesQuality planCommunication planBudget estimation and scheduling

Implementation:Directing and leadingMonitoring and controllingCommunication

Closure:Reflection and lessons learned and documentationHanding over the project output, training plans, maintenance plan

5

Planning ActivityProject Leadership

Level Team Level

Scope X X

Project Organizational Structure X  

Master Plan X  

Responsibility and Accountability Matrix X X

WBSX (2 to 3 levels up

to team scope level) X

Network X X

Gantt Chart X X

Estimationof Durations and Resources X X

Budget and Spending Plan X X

Project Communication Plan X X

Risk Management X  

Change Management X X

6

Describe the following items in broad terms:•The project goal and/or underlying concepts•Justification for the project •Who are the sponsor(s) and stakeholders•Requirements of sponsors and stakeholders•The deliverables and milestones (representing approximate completion of major deliverables)•The benefits to be obtained by implementing the deliverables (•In what ways the sponsor(s) and stakeholders are prepared to support the project

Circumstances that support need of a project include the presence of a justifiable:•Market demand•Business need•Customer request•Technological advances•Legal requirement

Scope Development

7

Project Scope StatementProject Name: Date:Project Manager:Project Tracking Number:Project Justification (problem or opportunity addressed):Overview of Deliverables (. . . broad brush only—Place detailed WBS in appendices*):Specific Project Objectives & Success Criteria (schedule, cost, quality):Scope Management Issues (including ways scope changes will be handled, contract change orders will be processed, etc.):Primary Stakeholders & Roles (including broad statement of roles and responsibilities of all customers, sponsors, contributors, reviewers, managers, sign-off authorities, project manager, etc.):Key Assumptions (including broad statement of sponsor/stakeholder inputs and resources to be provided, as well as what activities and deliverables lie outside the project scope):Signatures—The following people agree that the above information is accurate: Project team members: Project sponsor and/or authorizing manager(s):

8

An Example of A Project Organization

9

Master Plan

10

Phase*

Person

A=accountable, P=participate, R=review, I=input required, S= sign-off required

Project Responsibly and accountability Matrix

11

Festival

List of volunteers GamesPromotion Rides Entertainment Food Services

Newspaper adds

Posters

Tickets

Booths

Games

Prizes

Amusementcontractor

Permits

Performers

Grandstand

Stage

Audio & lighting

Seating

Food items

Facilities

Food booths

Cooking equipments

Eating areas

Parking

Security

Clean up

Restrooms facilities

Containers

Contractors

Restrooms

First aid facilities

12

An Example of a Work Breakdown Structure

1 Coveyor Belt Control Computer1.1 Hardware1.1.1 Hardware specifications1.1.2 Hardware design1.1.3 Hardware documentation1.1.4 Prototypes1.1.5 Order circuit boards1.1.6 Assemble preproduction models1.2 Operating Systems1.2.1 Kernel Specifications1.2.2 Drivers1.2.2.1 Disk drivers1.2.2.2 Serial I/O drivers1.2.3 Memory management1.2.4 Operating system documentation1.2.5 Network interface1.3 Utilities1.3.1 Utilities specifications1.3.2 Routine utilites1.3.3 Complex utilites1.3.4 Utilities documentation1.3.5 Shell1.4 System integration1.4.1 Architectural decisions1.4.2 Integration first phase1.4.3 System hard/software test1.4.4 Project documentation1.4.5 Integrated acceptance testing

13

Project

Design and Development

Production and Delivery

Integrated Logistics System

Lab test

Environmental test

Build production line and Test equipment

Production and delivery

Documentation and training programs

Training

SDR

PDR

CDR

PRR

CDR

TRR

TRR

PRR

PRR

Detail Definition: Work Breakdown Structure

14

Activity-on-Node Network Fundamentals

15

Decide on date

Select attendants

Rent church

Reserve reception

hall

Wedding reception

Marriage license

Order dresses

Fit dresses

Create / print programs

Florist

Order invitations

Wedding ceremony

Hire photographe

r

Address and mail

invitations

Track RSVP

Make final order

Choose caterer

Decide on menu

Decorate reception

hall

Hire band

Wedding Project Network

16

17

18

Estimating Durations for Activities and Resources Required

Step 1: Assemble the following: Scope statement Activity list and network diagram Description of the resource pool, including resources available and their capabilities Historical data on similar activities from project files, commercial databases, or project team knowledge Organizational policy regarding staffing, rental/purchase of equipment and supplies, and so forth One or more experts who have estimated durations and resources required for similar projectsStep 2: Examine each activity; then estimate its duration and probable resources required. Estimate of duration, each activity Estimate of resources required and corresponding effort, for each activity Assumptions about the resources to be assigned (for example, employees will need to work 10-hour days or the machine will need to process 75 units per hour)

Note: Some organizations can supply you with data on what can reasonably be expected from a particular resource in order to achieve a quality work product. For example, a reasonable expectation for a veteran bricklayer might be to lay X number of bricks per day. If the project manager is forced, due to budget cuts, to hire fewer bricklayers or inexperienced bricklayers, then you may not be able to maintain your project schedule. Your assumptions should clearly state any “reasonable expectancies” such as these so that they may be captured in your project plan.Step 3: Reevaluate the activity relationships, given your duration and resource assumptions. Examine clusters or groups of related activities. Examine “stand alone” activities.Step 4: Adjust the project network diagram as needed. Network diagram adjustedStep 5: Informally present your estimates of durations and resources required to an expert colleague to “reality-check” it; adjust as needed. Expert review, adjustment

19

Building a Budget and Spending Plan

Step 1: Assemble the following: Project cost estimates Work breakdown structure (WBS) Project schedule Budget forms or sample budget/spending plans approved by your organizationStep 2: Make a worksheet with headings similar to these:

Activity Account Code

Budgeted, January

Budgeted, February

Budgeted, March

Budgeted [April, etc.]

Note: If you want to monitor your spending on a quarterly or weekly basis, then label the column headings accordingly. Worksheet is completed.Step 3: List all project activities in the left column of the worksheet. Project activities are listed.

20

Step 4: For each activity, examine the project schedule and cost estimate to determine how much will be spent the first month, how much the second month, and so on. Then list the appropriate dollar amounts in the columns beside each activity. Dollar amounts are listed by time.

Note: You might want to create a more detailed spending plan by breaking out specific resource costs under each activity. Consider this example:

Activities/ResourcesAccount

CodeBudgeted, Jan. 1–7

Budgeted, Jan. 8–15

Budgeted, Jan. 16–23

Write Script Scriptwriter Research Assistant Computer rental

PRD-5RAS-1EQP-1

$2,000.00500.00100.00

$2,000.00—100.00

——100.00

Review Script Producer Videographer Technical Reviewer

PRD-1PRD-3EXP-1

$3,000.001,000.001,000.00

Total: $2,600.00 $2,100.00 $5,100.00

Step 5: Informally present your preliminary budget and spending plan to an expert colleague to “reality-check” it; adjust as needed based on his or her feedback. Budget spending plan is “reality-checked” and revised.Step 6: Present your budget and spending plan to your supervisor and (if appropriate) to the sponsor; adjust as needed and obtain approval. Budget spending plan is approved.

21

Guidelines for Developing the Project Communications Plan

Step 1: Assemble the following: List of project stakeholders and their roles, responsibilities, and physical locations Any descriptions of communication requirements or related assumptions among stakeholders Information about external reporting requirements (What do the public, the press, the government, and other outsiders need to know about the project? How will they find out?) Information about technology available to support communication on the project (e.g., fax, E-mail, voice mail, messenger, postal service, radio) Information about typical project communications methods for the industry or in your organizationStep 2: Answer this question: “What kind of information does each stakeholder need?” List of information needed by each stakeholder Typical information needed by stakeholders on similar projectsStep 3: Analyze all stakeholder information needs and answer this question: “What methods/technologies will provide all information needed by stakeholders without wasting resources on providing unneeded information or using inappropriate technology?” List of appropriate communications methods and technologiesStep 4: Create a project communications plan that includes information about: Collection structure—How and by whom will project information be gathered, what information will be gathered, and from whom? Distribution structure—To whom will information flow, and by what methods? Description of each type of information to be disseminated—What format, content, level of detail, conventions/definitions will be used? Schedules listing when each type of information will be produced A method for updating the communications plan as the project progresses

22

Project Communications Planner

In the What Information column, list the type of information this person or group will need.In the When column, list how often or at what points in the project this person or group will need the information. (For example, you might say “weekly” or “monthly” here, or “at sign-off of Phase II.”)In the How (Form/Medium) column, list the appropriate medium of communication. (For example, you might say “e-mail status report,” “team meeting,” “broadcast voice-mail,” or “update to project web page.”)

Who What Information

When How (Form/Medium)

       

       

       

       

23

Identifying Risks and Planning to Respond

Step 1: Determine what sources of risk and which risk events may reasonably be expected to affect the project. Examine the product (deliverables) description. Which require creation by using unproven technology? Or which deliverables are themselves made up of unproven technology? Examine the scope statement. Are the project costs or objectives overly aggressive? Examine the work breakdown structure. Are there hidden dependencies that should be explored? Could the work breakdown structure be broken into greater detail in some areas to “shine a light” on risks or opportunities? If so, then create this detail. Examine the staffing plan. Are there “irreplaceable” team members who might be made unavailable somehow? Examine the resource requirements (people, equipment, and materials). Could market conditions make it difficult to obtain some resources (a risk) or easier to obtain some resources (an opportunity)? Examine the history of similar projects. What potential opportunities or threats might we identify based on previous experience? Use established checklists from your project’s discipline to evaluate risk and opportunities. Interview various stakeholders to uncover opportunities or risks.Step 2: Quantify the risks identified in Step 1 to determine which risk events warrant response. Consider: Expected monetary value or impact of the risk Expected impact on project quality Expected impact on project scheduleRisks are quantified.

24

Step 3: Decide which risks or opportunities to focus on and document them by making a list of “risks to pursue.”“Risks to Pursue” list is created.Step 4: For each risk warranting response, choose one of these risk responses:105 Avoid it—by eliminating the cause.

This might involve using different approaches to the work process, different staffing, redefined deliverables, revised (lower-risk) schedules, or modified stakeholder expectations. Mitigate it—by reducing the expected monetary value. For example, you could:Contract out high-risk activities to specialists who have more experience.Obtain insurance policies to deal with some types of risk.Develop contingency plans which identify specific actions that will be taken if an identified risk should occur.Set aside a “desired reserve” of cash or other resources to use if the risk occurs. Accept it—and take the consequences.For help with this analysis, please see “Worksheet: Risk Assessment and Response Analyzer.” Each risk is examined and a decision to avoid, mitigate, or accept it is made.Step 5: Create a risk management plan that contains these sections: List of potential risk events Description of risk symptoms Ways to improve processes or activities to reduce risks Opportunities to pursue or threats to which to respond Opportunities or threats that have been identified and consciously ignored Description of contingency plans and steps to take to mitigate risks Recommended contractual agreements to mitigate risks Risk management plan is created.

25