14
Peak LAN Project Group A: Timothy Flannigan, Candace Hunt, Bobby McCrary, Karie Smithers and Stacy Welk MGMT 505: Project Management Fundamentals September 18, 2011

Peak LAN Project Group A:

Embed Size (px)

DESCRIPTION

Overview Company Profile Company Project Identifying and Managing Milestones Budget Constraints Assessing Probable Set-Backs Customer Satisfaction Project Risks Risk Assessment Form Risk Response Matrix Summary

Citation preview

Page 1: Peak LAN Project Group A:

Peak LAN ProjectGroup A:

Timothy Flannigan, Candace Hunt, Bobby McCrary, Karie Smithers and Stacy Welk

MGMT 505: Project Management FundamentalsSeptember 18, 2011

Page 2: Peak LAN Project Group A:

Overview• Company Profile• Company Project• Identifying and Managing Milestones• Budget Constraints• Assessing Probable Set-Backs• Customer Satisfaction• Project Risks• Risk Assessment Form• Risk Response Matrix• Summary

Page 3: Peak LAN Project Group A:

Peak Systems

• Information Systems Consulting Firm, small• Meridian, Louisiana

Page 4: Peak LAN Project Group A:

Project

• Design and install local area network (LAN) for Meridian Social Service Agency• Deliverables • Technical Requirements• Limits and Exclusions• Budget =<$90,000• Time limit = 1 month

Page 5: Peak LAN Project Group A:

Identifying and Managing Project Milestones

Hardware – Availability and cost of products to complete the project

User’s Priority and authorization – Who, and what the users will be granted access too.

In house network test - Organization with third party, and meeting the agenda with the customer

Client site test – Meeting test deadlines, and planning the observation period with the customer

Training completed – Complete all training to become self operational, and compatible

Page 6: Peak LAN Project Group A:

MilestonesKey Milestones Target

Date

1. Hardware January

22

2. Setting Users’ priority and authorization January

26

3. In-house whole network test February

1

4. Client site test February

2

5. Training completed February

16

Page 7: Peak LAN Project Group A:

Budget Constraints• Time phased-budget baseline- Helps identify the cost of tangible items, and resources to

complete the project• It is overall important for the projects success to measure the

projects performance• Monetary, and time sensitive budgets drive overall project

success• Resource utilization – Make sure that all resources are being

utilized to the highest efficiency- Garner resources, and relations to complete the project at a

low cost

Page 8: Peak LAN Project Group A:

Assessing Probable Set-backs

• Accept possible set-backs during project planning for maximum readiness, and avoidance

• Complete a risk assessment form to evaluate and rate possible risk during the project

- Likelihood: 5 represents greatest to 1 with least probability of occurrence - -Impact: 5 represents gravest to 1 with least jeopardizing project deliverables - Detection Difficulty: 5 represents hardest to 1 with least difficulty

Page 9: Peak LAN Project Group A:

Customer Satisfaction

• Customer Satisfaction displays a complete understanding of meeting the customers needs, wants, and expectations

• The Project Manager is responsible for ensuring 100% Customer Satisfaction is meet.

• Notify the customer of all needs, and possible set-backs to accomplish the project. This allows the customer to be involved, and ensure their decisions, and needs are meet within the project

Page 10: Peak LAN Project Group A:

Project Risks

• Identifying and Managing Milestones• Budget Constraints• Technical Requirements and Deliverables• Assessing Probable Set-backs• Customer Satisfaction

Page 11: Peak LAN Project Group A:

Risk Assessment FormRisk Event

Likelihood Impact Detection Difficulty

When

Milestonesnot met

3 3 1 Each

Budget over obligated

1 3 1 Each Milestone

Timing of Resources

3 1 1 Each Milestone

Customer Satisfaction

1 5 3 Each Milestone

Setbacks: unexpected events

3 1 1 Each MilestoneLikelihood: 5 represents greatest to 1 with least probability of

occurrenceImpact: 5 represents gravest to 1 with least jeopardizing project deliverablesDetection Difficulty: 5 represents hardest to 1 with least difficulty

Page 12: Peak LAN Project Group A:

Risk Response MatrixRisk Event

Response Contingency Plan

Trigger Who is Responsible

Milestones Mitigate: Structure development Plan

Share important tasks w/ workers

Complete before project kickoff

Team

Budget Restrictions

Mitigate: Set a time-phased budge

Plan accordingly

Must be worked into development plan

Managers

Timing of Resources

Mitigate: Prioritize and allocate resources

Have Replacements available

Implement timing throughout project

Team

Customer Satisfaction

Mitigate: Educate & involve through completion

Understand project scope

Must have involvement start to finish

Project Manager

Setbacks: unexpected events

Mitigate: Plan into budget and time

Have a plan B Identify risk throughout project

Project Manager

Page 13: Peak LAN Project Group A:

Summary

• Objective• Milestones• Budget• Setbacks• Customer Satisfaction• Risks

Page 14: Peak LAN Project Group A:

ReferencesDr. Susan Michie. (2002). CAUSES AND MANAGEMENT OF STRESS AT WORK. Occupational and Environmental Medicine, 59:67-72.

Erik W. Larson, Clifford F. Gray. (2011). Project Management the Managerial Process. New York: McGraw-Hill Companies, Inc.

Higginbotham, J. (208, March 31). Project Planning: Identify Milestones, Assumptions, and Tasks. Retrieved September 16, 2011, from Volunteer Centered: http://www.volunteercentered.com/2008/03/31/project-planning-identify-milestones-assumptions-and-tasks/

JOHN R. DRAKE, TERRY ANTHONY BYRD. (2006). RISK IN INFORMATION TECHNOLOGY PROJECT PORTFOLIO MANAGEMENT. JOURNAL OF INFORMATION TECHNOLOGY THEORY AND APPLICATION, 1-11.

Kim, S.-c. (2009). Project success indicators focusing on residential projects: are schedule performance index and cost performance index accurate measures in earned value? Canadian Journal of Civil Engineering, 1700.

University of Wisconsin. (2006, February 1). Develop High-Level Milestones and Timeline. Retrieved September 16, 2011, from Project Management Advisor: http://pma.doit.wisc.edu/initiate/4/print.html