Project managers
PM/490 v2
Project Management Institute (PMI) Methodology Plan
PM/490 v2
Page 2 of 2
Project Management Institute® (PMI) Methodology Initiating and Planning Components
Refer to the Project Scope document to complete the four parts of this template.
Part 1: Stakeholder Register
Refer to the Project Scope document to complete this table.
· In the Name column, list each stakeholder’s name.
· In the Role column, list each stakeholder’s role or title.
· In the Interest column, identify whether each stakeholder has a high, medium, or low level of interest in the project.
· In the Influence, column, identify whether each stakeholder has a high, medium, or low level of influence on the project.
· In the Impact column, identify whether each stakeholder has a high, medium, or low level of impact on the project.
|
Name |
Role |
Interest (High, Med, or Low) |
Influence (High, Med, or Low) |
Impact (High, Med, or Low) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Part 2: Work Breakdown Structure (WBS)
Complete the WBS below using nouns to describe deliverables as discussed in Burek. The examples used throughout are about a bicycle-building project and do not reflect the scenario used in the assessment. Examples are in italics. Delete the examples prior to submission.
Choose 3 of the following Level 1 deliverables to use in the WBS. Be sure to use the correct L1 number of the deliverables you select. These numbers should not change throughout the life of the project.
1.0 Project initiation
2.0 Requirements analysis
3.0 System design
4.0 Development
5.0 Testing and quality assurance
6.0 Deployment
7.0 Maintenance and support
Identify 3 Level 2 deliverables for each chosen Level 1 deliverable (3 L2s for each L1, 9 L2s in total). Identify 3 Level 3 deliverables for each Level 2 to illustrate project deliverables (3 L3s for each L2, 9 for each L1, 27 in total). Use the following guidelines:
· In the WBS Level column, assign each high-level deliverable a number, along with appropriate sub-deliverable levels.
· Level 1: high-level deliverables that represent major deliverables or phases of the project
· Level 2: deliverables for each Level 1 deliverable that break the work into smaller, more manageable deliverables (labeled 1.1, 1.2, 1.3, etc.)
· Level 3: deliverables for each Level 2 deliverable that break down the work into smaller, more manageable deliverables (labeled 1.1.1, 1.2.1, 1.3.1, etc.)
· In the WBS ID column, assign each deliverable an ID.
· In the WBS Name column, assign each product or deliverable a name.
· In the WBS Description column, describe what the deliverable entails in about 2–10 words.
· Update the deliverable graphic below the table.
|
WBS Level |
WBS ID |
WBS Name
|
WBS Description |
|
Level 1 |
1 |
Bicycle |
Design and build the product |
|
Level 2 |
1.1 |
Frame Set |
Design and build the components |
|
Level 3 |
1.1.1 |
Frame |
Design and build the sub-components |
|
Level 3 |
1.1.2 |
Handlebar |
Design and build the sub-components |
|
Level 2 |
1.2 |
Braking System |
Design and build the components |
|
Level 3 |
1.2.1 |
Lever |
Design and build the sub-components |
|
Level 3 |
1.2.2 |
Pedal |
Design and build the sub-components |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
WBS Graphic Example:
Part 3: Project Schedule
Complete the table below to transition from the deliverables in Part 2 to tasks necessary to accomplish the deliverables. Align each task needed to accomplish the deliverables identified above with a time frame, stakeholder, and budget. Tasks are described with verbs . Refer to the stakeholder register completed in Part 1, and the Time Frame, Budget, and Project Milestones sections of the Project Scope document. Examples are in italics. Delete the examples prior to submission.
· In the WBS ID column, list the WBS ID assigned to the task.
· In the Task column, list 10–15 tasks, including at least 5 Level 2 tasks and the rest Level 3 sub-tasks.
· In the Duration column, list the number of days between the start date and finish date.
· In the Start Date column, list the start date. Refer to Project Scope document for your major milestones within a 6-month period.
· In the Finish Date column, list the finish date.
· In the Stakeholder column, list the role assigned to the task. Refer to the stakeholder register.
· In the Budget column, list the amount expected to be spent on each task. According to the Project Scope document, the budget is $800,000 and will need to be allocated among all 7 Level 1 Deliverables and their tasks. The tasks and sub-tasks should be allocated accordingly from these budget amounts.
|
WBS ID
|
Task |
Duration |
Start Date |
Finish Date |
Stakeholder |
Budget |
|
1.2 |
Build the braking system |
45 days |
Feb. 15 |
March 31 |
Engineer |
$200,000 |
|
1.2.2 |
Build the pedals |
8 days |
Feb. 17 |
Feb. 26 |
Technician |
$50,000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Part 4: Summary
Respond to the following in approximately 350–525 total words. Be sure to use section headings to organize your responses.
Explain how creating the stakeholder register, WBS, and Project Schedule align with the PMI methodology.
Describe the challenges that occurred when creating each WBS deliverable. Recommend ways to address these challenges in future deliverables.
Explain how creating the stakeholder register, WBS, and Project Schedule demonstrates your project management skills.
Reflect on how creating these components based on the PMI methodology can be used in future career endeavors.
Bicycle
1.1 Frame Set
1.1.1 Frame
1.1.2 Handlebar
1.2 Braking System
1.2.1 Lever
1.2.2 Pedal
Copyright 2025 by University of Phoenix. All rights reserved.
Copyright 2025 by University of Phoenix. All rights reserved.