PPM4110 Baker College IT infrastructure & Work Breakdown Structure Paper For the scenario below, a work breakdown structure will need to be completed for t
PPM4110 Baker College IT infrastructure & Work Breakdown Structure Paper For the scenario below, a work breakdown structure will need to be completed for the total build out of the office site/equipment needs as well as a complete rebuild of the IT infrastructure. A template for the work breakdown structure has been included.
Scenario
The accounting firm where you work has assigned you as the Project Manager to supervise an upcoming project.In exactly three months, the firm will merge with a smaller company and needs a new location for its employees. The firm currently consists of 40 employees and will be adding an additional 10 employees as a result of the merger. The second floor of a historic, two-story building has been purchased to accommodate the 50 employees in the citys downtown district. It is completely gutted, so a complete build-out will be necessary. In order to minimize downtime, the move will take place over Labor Day weekend. You’ve been tasked to oversee renovations and installation of all IT requirements.As a recent graduate of Baker College Online, your CEO (project sponsor) has afforded you a considerable amount of discretion when it comes to decision-making. Although he will provide final approval, he expects you to decide on a floor plan, as well as what furniture and computers to keep and what must be replaced. The firms image is important, so he expects you to balance cost with quality.
·Build-out: Offices and/or cubicles for 50 employees (the CEO would like you to price out single offices for 10 senior level employees), a conference room, a break room with a kitchenette, a lobby reception area, a LAN room, storage / supply room, and restrooms.
·Computer network: Currently, the employees of the smaller firm are using older model Dell computers (circa 2005) with a Windows XP operating system. Your company is also in desperate need of hardware updates. Most employees are using older systems with Windows XP and some are using Windows Vista. Your company has a client/server network using Windows 2000 server. Your accountants use either Intuit QuickBooks or Sage Peachtree software. You are currently using Symantec Antivirus Corporate protection. Your company currently performs full backups nightly to an onsite server. Security is of the utmost importance. Your proposal should consider the following:
A. Computers for each employee (Marketing has indicated a preference for Macs for their 5 people due to their graphic capability)
B. Software requirements for each computer
C. Network hardware and operating system
D. Backup System
E.Additional devices required (Printers, Scanners, etc.).
F.Internet Service Provider
I attached the whole breakdown of the assignment, with the scenario being highlighted teal and the portion that is due highlighted yellow. From the assignment as a whole, if you need any of the other previously completed assignments, let me know and I will be happy to attach them. Team Project
Scenario
The accounting firm where you work has assigned you as the Project Manager to supervise an upcoming
project. In exactly three months, the firm will merge with a smaller company and needs a new location
for its employees. The firm currently consists of 40 employees and will be adding an additional 10
employees as a result of the merger. The second floor of a historic, two-story building has been
purchased to accommodate the 50 employees in the citys downtown district. It is completely gutted,
so a complete build-out will be necessary. In order to minimize downtime, the move will take place over
Labor Day weekend. Youve been tasked to oversee renovations and installation of all IT requirements.
As a recent graduate of Baker College Online, your CEO (project sponsor) has afforded you a
considerable amount of discretion when it comes to decision-making. Although he will provide final
approval, he expects you to decide on a floor plan, as well as what furniture and computers to keep and
what must be replaced. The firms image is important, so he expects you to balance cost with quality.
Build-out: Offices and/or cubicles for 50 employees (the CEO would like you to price out single
offices for 10 senior level employees), a conference room, a break room with a kitchenette, a lobby
reception area, a LAN room, storage / supply room, and restrooms.
Computer network: Currently, the employees of the smaller firm are using older model Dell
computers (circa 2005) with a Windows XP operating system. Your company is also in desperate
need of hardware updates. Most employees are using older systems with Windows XP and some are
using Windows Vista. Your company has a client/server network using Windows 2000 server. Your
accountants use either Intuit QuickBooks or Sage Peachtree software. You are currently using
Symantec Antivirus Corporate protection. Your company currently performs full backups nightly to
an onsite server. Security is of the utmost importance. Your proposal should consider the following:
A. Computers for each employee (Marketing has indicated a preference for Macs for their 5
people due to their graphic capability)
B. Software requirements for each computer
C. Network hardware and operating system
D. Backup System
E. Additional devices required (Printers, Scanners, etc.).
F. Internet Service Provider
Project Initiation
1) Create a proposal containing:
Purpose and need for project
Scope of project (project objectives, deliverables, milestones, specifications, overall cost, human
resources, communications, procurement, limits and exclusions)
2) Project Teams must identify the projects primary and secondary stakeholders, the stakeholders
needs, and how the project objectives affect the stakeholders.
3) Include a RAM based on the RACI format (Responsible, Accountable, Consult and Inform). This type
of RAM is called a RACI chart, because it assigns the role that the resource is to play for each given
activity.
Project Planning Part I
1) Create RFPs (for both Build-out and Computer Network Install), with Statement of Work (SOW)
Identify how the formal quote is to be submitted
Define special terms and conditions (Notice of cost overruns or schedule delays, approval of
subcontractors, customer-furnished equipment or information, termination, terms of payment,
penalty payments, implementing changes, inspections, renovation plans must be approved by the
city council, etc.)
Determine the type of contract to be used
2) Determine the metrics for a successful project
Project Planning- Part II
1) Work Breakdown Structure
2) Budget (Bottom Up)
3) Schedule (GANTT in MS Project)
Project Execution and Controlling
1) Identify risk for the work performed and develop a mitigation plan for the risks identified.
Risk identification consists of: determining which risks may adversely affect the project objective
and what the consequences of each risk might be if they occur.
Risk assessment consists of: determining the likelihood that the risk event will occur and the degree
of impact the event will have on the project objective. Develop an action plan to reduce the impact
or likelihood of each risk.
Develop contingency plans may require expenditure of additional funds for using additional
resources.
2) Prepare a list of potential risk events and develop a Risk Assessment Form. Also, prepare a Risk
Severity Matrix. Prepare a Failure Mode and Effects Assessment to stratify the risks.
3) Alternative solutions to unforeseen circumstances (your instructor will provide this information
budget cut, furniture out of stock, water leak, permit delay, contractor LAN technician out sick, etc.)
Project Closure
Complete a post implementation review. The following are suggested topics to be included:
Technical performance
Cost performance
Schedule performance
Project planning and control
Risk management
Customer relationships
Team relationships
Communications
Problem identification and resolution
Lessons learned
Recommendations
ProjectManagementDocs.com
WORK BREAKDOWN STRUCTURE (WBS) TEMPLATE
This Project WBS Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
ProjectManagementDocs.com
WORK BREAKDOWN STRUCTURE (WBS)
COMPANY NAME
STREET ADDRESS
CITY, STATE ZIP CODE
DATE
1
ProjectManagementDocs.com
INTRODUCTION
The WBS is a view into the project which shows what work the project encompasses. It is a tool
which helps to easily communicate the work and processes involved to execute the project.
The Project Manager and project team use the WBS to develop the project schedule, resource
requirements and costs. There are many ways you can present the WBS for your project; this
template provides many of the most popular layouts from which you can choose. Depending
on where in the Project Plan you’re putting the WBS a different layout may be more suitable for
you. For instance many Project Managers include a high level WBS within the project plan, then
a detailed version as an appendix to the plan. You may find that you prefer one layout for a
high level WBS and a different one for a detailed WBS.
In order to save space in this template we only developed the WBS examples down to the third
level. In your project you will want to develop them down to a much more detailed level using
the 8 to 80 rule (where the WBS is broken down to where a work package contains between 8
and 80 hours of work to complete).
The Work Breakdown Structure presented here represents all the work required to complete
this project.
OUTLINE VIEW
The outline view presents an easy to view and understand layout for the WBS. It is also a good
layout to use when developing the WBS because you can easily make changes, especially since
the Microsoft Word auto numbering feature updates the WBS Code automatically.
1. Widget Management System
1.1 Initiation
1.1.1 Evaluation & Recommendations
1.1.2 Develop Project Charter
1.1.3 Deliverable: Submit Project Charter
1.1.4 Project Sponsor Reviews Project Charter
1.1.5 Project Charter Signed/Approved
1.2 Planning
1.2.1 Create Preliminary Scope Statement
1.2.2 Determine Project Team
1.2.3 Project Team Kickoff Meeting
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
1.3 Execution
2
ProjectManagementDocs.com
1.3.1 Project Kickoff Meeting
1.3.2 Verify & Validate User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
1.4 Control
1.4.1 Project Management
1.4.2 Project Status Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
1.5 Closeout
1.5.1 Audit Procurement
1.5.2 Document Lessons Learned
1.5.3 Update Files/Records
1.5.4 Gain Formal Acceptance
1.5.5 Archive Files/Documents
HIERARCHICAL STRUCTURE
The hierarchal structure is similar to the outline view but without indentation. Although this
format is more difficult to read, it may be useful where you have many levels and indenting
each level would make the table to large to fit into a document.
3
ProjectManagementDocs.com
Level
1
2
3
3
3
3
3
2
3
3
3
3
3
3
2
3
3
3
3
3
3
3
3
3
2
3
3
3
3
2
3
3
3
3
3
4
WBS Code
1
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
Element Name
Widget Management System
Initiation
Evaluation & Recommendations
Develop Project Charter
Deliverable: Submit Project Charter
Project Sponsor Reviews Project Charter
Project Charter Signed/Approved
Planning
Create Preliminary Scope Statement
Determine Project Team
Project Team Kickoff Meeting
Develop Project Plan
Submit Project Plan
Milestone: Project Plan Approval
Execution
Project Kickoff Meeting
Verify & Validate User Requirements
Design System
Procure Hardware/Software
Install Development System
Testing Phase
Install Live System
User Training
Go Live
Control
Project Management
Project Status Meetings
Risk Management
Update Project Management Plan
Closeout
Audit Procurement
Document Lessons Learned
Update Files/Records
Gain Formal Acceptance
Archive Files/Documents
ProjectManagementDocs.com
TABULAR VIEW
The Tabular View is a nicely organized table view of the WBS. It is a good option for
organizations which prefer table formats.
Level 1
1 Widget
Management
System
5
Level 2
1.1 Initiation
Level 3
1.1.1 Evaluation & Recommendations
1.1.2 Develop Project Charter
1.1.3 Deliverable: Submit Project Charter
1.1.4 Project Sponsor Reviews Project Charter
1.1.5 Project Charter Signed/Approved
1.2 Planning
1.2.1 Create Preliminary Scope Statement
1.2.2 Determine Project Team
1.2.3 Project Team Kickoff Meeting
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
1.3 Execution
1.3.1 Project Kickoff Meeting
1.3.2 Verify & Validate User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
1.4 Control
1.4.1 Project Management
1.4.2 Project Status Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
1.5 Closeout
1.5.1 Audit Procurement
1.5.2 Document Lessons Learned
1.5.3 Update Files/Records
1.5.4 Gain Formal Acceptance
1.5.5 Archive Files/Documents
ProjectManagementDocs.com
TREE STRUCTURE VIEW
The Tree Structure View is the most popular format for the WBS. It presents an easy to
understand view into the WBS; however, it is also tricky to create without an application
specifically designed for creating this organizational chart structure. The Tree Structure below
was created using only Microsoft Word and the SmartArt graphics option under the insert
menu.
6
ProjectManagementDocs.com
Widget Mgmt.
System
1
Initiation
1.1
Planning
1.2
Execution
1.3
Control
1.4
Evaluation &
Recommendations
1.1.1
Create Preliminary
Scope Statement
1.2.1
Project Kickoff
Meeting
1.3.1
Project
Management
1.4.1
Audit Procurement
1.5.1
Develop Project
Charter
1.1.2
Determine Project
Team
1.2.2
Verify & Validate
User Requirements
1.3.2
Project Status
Meetings
1.4.2
Document Lessons
Learned
1.5.2
Deliverable:
Submit Project
Charter
1.1.3
Project Team
Kickoff Meeting
1.2.3
Design System
1.3.3
Risk Management
1.4.3
Update Files/
Records
1.5.3
Project Sponsor
Reviews Project
Charter
1.1.4
Develop Project
Plan
1.2.4
Procure
Hardware/Softwar
e
1.3.4
Update Project
Management Plan
1.4.4
Gain Formal
Acceptance
1.5.4
Project Charter
Signed/Approved
1.1.5
Submit Project Plan
1.2.5
Install
Development
System
1.3.5
Milestone: Project
Plan Approved
1.2.6
Testing Phase
1.3.6
Install Live System
1.3.7
User Training
1.3.8
Go Live
1.3.9
7
Closeout
1.5
Archive Files/
Documents
1.5.5
ProjectManagementDocs.com
WBS DICTIONARY
The WBS Dictionary contains all the details of the WBS which are necessary to successfully
complete the project. Most importantly it contains a definition of each Work Package which
can be thought of as a mini scope statement. Resources on the project will look at the WBS
dictionary to determine the scope of the Work Package they’ve been assigned, so it’s important
to be clear when writing the definition. Most WBS dictionaries contain more information than
we show in our sample. These things usually include Level of Effort, Cost Control Numbers,
Resource Assignments, Responsibility Assignments – just to name a few.
8
ProjectManagementDocs.com
Level
9
1
WBS
Code
1
2
3
1.1
1.1.1
3
1.1.2
3
1.1.3
3
1.1.4
3
1.1.5
2
1.2
3
1.2.1
3
1.2.2
3
1.2.3
3
1.2.4
3
1.2.5
3
1.2.6
2
1.3
Element Name
Widget Management System
Definition
All work to implement a new widget
management system.
Initiation
The work to initiate the project.
Evaluation & Recommendations Working group to evaluate solution
sets and make recommendations.
Develop Project Charter
Project Manager to develop the
Project Charter.
Deliverable: Submit Project
Project Charter is delivered to the
Charter
Project Sponsor.
Project Sponsor Reviews Project Project sponsor reviews the Project
Charter
Charter.
Project Charter
The Project Sponsor signs the Project
Signed/Approved
Charter which authorizes the Project
Manager to move to the Planning
Process.
The work for the planning process for
Planning
the project.
Create Preliminary Scope
Project Manager creates a Preliminary
Statement
Scope Statement.
The Project Manager determines the
project team and requests the
Determine Project Team
resources.
The planning process is officially
started with a project kickoff meeting
which includes the Project Manager,
Project Team and Project Sponsor
Project Team Kickoff Meeting
(optional).
Under the direction of the Project
Manager the team develops the
Develop Project Plan
project plan.
Project Manager submits the project
Submit Project Plan
plan for approval.
The project plan is approved and the
Project Manager has permission to
proceed to execute the project
Milestone: Project Plan Approval according to the project plan.
Execution
Work involved to execute the project.
ProjectManagementDocs.com
3
1.3.1
Project Kickoff Meeting
3
1.3.2
Verify & Validate User
Requirements
3
1.3.3
Design System
3
1.3.4
Procure Hardware/Software
3
1.3.5
Install Development System
3
1.3.6
3
1.3.7
Testing Phase
Install Live System
3
1.3.8
3
2
1.3.9
1.4
3
1.4.1
User Training
Go Live
Control
3
3
1.4.2
1.4.3
Project Management
Project Status Meetings
Risk Management
3
2
10
1.4.4
1.5
Update Project Management
Plan
Closeout
Project Manager conducts a formal
kick off meeting with the project team,
project stakeholders and project
sponsor.
The original user requirements is
reviewed by the project manager and
team, then validated with the
users/stakeholders. This is where
additional clarification may be needed.
The technical resources design the
new widget management system.
The procurement of all hardware,
software and facility needs for the
project.
Team installs a development system
for testing and customizations of user
interfaces.
The system is tested with a select set
of users.
The actual system is installed and
configured.
All users are provided with a four
hours training class. Additionally,
managers are provided with an
additional two hours class to cover
advanced reporting.
System goes live with all users.
The work involved for the control
process of the project.
Overall project management for the
project.
Weekly team status meetings.
Risk management efforts as defined in
the Risk Management Plan.
Project Manager updates the Project
Management Plan as the project
progresses.
The work to close-out the project.
ProjectManagementDocs.com
3
1.5.1
3
1.5.2
Audit Procurement
Document Lessons Learned
3
1.5.3
3
1.5.4
3
1.5.5
Update Files/Records
Gain Formal Acceptance
Archive Files/Documents
An audit of all hardware and software
procured for the project, ensures that
all procured products are accounted
for and in the asset management
system.
Project Manager along with the project
team performs a lessons learned
meeting and documents the lessons
learned for the project.
All files and records are updated to
reflect the widget management
system.
The Project Sponsor formally accepts
the project by signing the acceptance
document included in the project plan.
All project related files and documents
are formally archived.
GLOSSARY OF TERMS
It’s important that you provide a glossary of terms as some of the terms are not understood by
persons without a project management background. For instance what the PMI Practice
Standard for Work Breakdown Structures refers to as the WBS Code is commonly referred to as
the WBS number.
Level of Effort:
WBS Code:
Work Package:
WBS Component:
WBS Element:
11
Level of Effort (LOE) is how much work is required to complete a task.
A unique identifier assigned to each element in a Work Breakdown
Structure for the purpose of designating the elements hierarchical location
within the WBS.
A Work Package is a deliverable or work component at the lowest level of
its WBS branch.
A component of a WBS which is located at any level. It can be a Work
Package or a WBS Element as there’s no restriction on what a WBS
Component is.
A WBS Element is a single WBS component and its associated attributes
located anywhere within a WBS. A WBS Element can contain work, or it
can contain other WBS Elements or Work Packages.
ProjectManagementDocs.com
This free WBS Template is brought to you by www.ProjectManagementDocs.com
12
Purchase answer to see full
attachment
