Free float and total float - PMP/CAPM from PMIMudassir Iqbal
https://www.mudassiriqbal.net/project-management-terms-and-concepts
There are many concepts and definitions which require special attention by all PMP Aspirants as the terminologies are largely used interchangeably in the real world.
MỌI CHI TIẾT XIN LIÊN HỆ ĐỂ ĐƯỢC TƯ VẤN MIỄN PHÍ
CÔNG TY CỔ PHẦN TƯ VẤN ĐẦU TƯ DỰ ÁN VIỆT
Địa Chỉ: 28B Mai Thị Lựu - Phường Đakao – Quận 1 – Tp. HCM
Website: http://duanviet.com.vn
Email: tuvandunviet@gmail.com
Hotline: 0918755356
Dịch Vụ Lập Dự Án Đầu Tư
Xin Chủ Trương Đầu Tư
Vay Vốn Ngân HàngKêu Gọi Đầu Tư
Tư vấn các thủ tục môi trường
Lập báo cáo đánh giá tác động môi trường (DTM)
Báo cáo giám sát môi trường Xin phép xả thải
Thiết kế thi công hệ thống xử lý nước thải, nước cấp
Tags:0918755356, duanviet, lap du an, lap du an dau tu, tu van lap du an, lập dự án, lập dự án đầu tư, cong ty moi truong, lap du an dau tu du an viet, lap du an dau tu mien phi, tai lieu lap du an, lap du an tai lieu
Activity network diagram helps to schedule a project efficiently. It gives an idea of the minimum and maximum time to complete a project. The 7th tool among the New 7 management development tool.
Free float and total float - PMP/CAPM from PMIMudassir Iqbal
https://www.mudassiriqbal.net/project-management-terms-and-concepts
There are many concepts and definitions which require special attention by all PMP Aspirants as the terminologies are largely used interchangeably in the real world.
MỌI CHI TIẾT XIN LIÊN HỆ ĐỂ ĐƯỢC TƯ VẤN MIỄN PHÍ
CÔNG TY CỔ PHẦN TƯ VẤN ĐẦU TƯ DỰ ÁN VIỆT
Địa Chỉ: 28B Mai Thị Lựu - Phường Đakao – Quận 1 – Tp. HCM
Website: http://duanviet.com.vn
Email: tuvandunviet@gmail.com
Hotline: 0918755356
Dịch Vụ Lập Dự Án Đầu Tư
Xin Chủ Trương Đầu Tư
Vay Vốn Ngân HàngKêu Gọi Đầu Tư
Tư vấn các thủ tục môi trường
Lập báo cáo đánh giá tác động môi trường (DTM)
Báo cáo giám sát môi trường Xin phép xả thải
Thiết kế thi công hệ thống xử lý nước thải, nước cấp
Tags:0918755356, duanviet, lap du an, lap du an dau tu, tu van lap du an, lập dự án, lập dự án đầu tư, cong ty moi truong, lap du an dau tu du an viet, lap du an dau tu mien phi, tai lieu lap du an, lap du an tai lieu
Activity network diagram helps to schedule a project efficiently. It gives an idea of the minimum and maximum time to complete a project. The 7th tool among the New 7 management development tool.
Download luận văn thạc sĩ ngành quản lí công với đề tài: Quản lý nhà nước đối với các dự án đầu tư xây dựng cơ bản từ vốn ngân sách Nhà nước tại tỉnh Quảng Ngãi
This presentation is prepared as part of the Course assignment of "HSM 612 Health Project Management” for the Master's Degree of Public Health (MPH), Pokhara University and can be used as reference materials. This Presentation is prepared by Jagat Prasad Upadhyay
Awadesh pratap singh university prospectus 2016 17 educationiconnect.com 78...00007123
student can check here all information about prospectus Awadesh pratap singh university prospectus 2016 17, educationiconnect.com 7862004786,Awadesh pratap singh university
Dịch vụ lập báo cáo môi trường ĐTM | Xử lý nước thải | 0918755356
Thiết kế quy hoạch
Lập báo cáo môi trường
Lập dự án
Xử lý nước thải
http://lapduandautu.com.vn
Planning and Project Controls under NEC4 – the choice isn’t yours! by "Glenn ...Project Controls Expo
Planning and Project Controls under NEC4 – the choice isn’t yours! by Glenn Hide - Director for GMH Planning Ltd, UK
Hezron Ricketts - Senior Manager, Senior Counsel to the Board for Th3rd Curve, UK at at Project Controls Expo 2017, Arsenal Stadium, London
Work Breakdown Structure (WBS) TemplateThis Project WB.docxambersalomon88660
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:
www.ProjectManagementDocs.com
Work Breakdown Structure
(WBS)
<Project Name>
Company Name
Street Address
City, State Zip Code
Date
Work Breakdown Structure (WBS) Template
www.ProjectManagementDocs.com
4
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
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.
Download luận văn thạc sĩ ngành quản lí công với đề tài: Quản lý nhà nước đối với các dự án đầu tư xây dựng cơ bản từ vốn ngân sách Nhà nước tại tỉnh Quảng Ngãi
This presentation is prepared as part of the Course assignment of "HSM 612 Health Project Management” for the Master's Degree of Public Health (MPH), Pokhara University and can be used as reference materials. This Presentation is prepared by Jagat Prasad Upadhyay
Awadesh pratap singh university prospectus 2016 17 educationiconnect.com 78...00007123
student can check here all information about prospectus Awadesh pratap singh university prospectus 2016 17, educationiconnect.com 7862004786,Awadesh pratap singh university
Dịch vụ lập báo cáo môi trường ĐTM | Xử lý nước thải | 0918755356
Thiết kế quy hoạch
Lập báo cáo môi trường
Lập dự án
Xử lý nước thải
http://lapduandautu.com.vn
Planning and Project Controls under NEC4 – the choice isn’t yours! by "Glenn ...Project Controls Expo
Planning and Project Controls under NEC4 – the choice isn’t yours! by Glenn Hide - Director for GMH Planning Ltd, UK
Hezron Ricketts - Senior Manager, Senior Counsel to the Board for Th3rd Curve, UK at at Project Controls Expo 2017, Arsenal Stadium, London
Work Breakdown Structure (WBS) TemplateThis Project WB.docxambersalomon88660
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:
www.ProjectManagementDocs.com
Work Breakdown Structure
(WBS)
<Project Name>
Company Name
Street Address
City, State Zip Code
Date
Work Breakdown Structure (WBS) Template
www.ProjectManagementDocs.com
4
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
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.
Work breakdown structure WBS Columbia Southe.docxericbrooks84875
Work breakdown structure
WBS
Columbia Southern University
Tiffany Williams
The work breakdown structure is a key project deliverable that organizes the team's work into
manageable sections. Is a "deliverable oriented hierarchical decomposition of the work to be executed
by the project team." The work breakdown structure visually defines the scope into manageable chunks
that a project team can understand, as each level of the work breakdown structure provides further
definition and detail. (Work Breakdown Structure (WBS). (n.d.). Retrieved from
https://www.workbreakdownstructure.com)IN this case, I would use a three level work breakdown to
illustrate the processes in the construction project. In the paper am going to outline the work break
down structure for the construction project of a warehouse showing the various stages, participants, the
budget, as well as project timeline and constraints.
The depiction of the WBS will be using both charts and tables indicating codes for the various activities.
The idea process can be illustrated in the diagram below together with the OBS
WBS #: 1.1.1 Task: Create Plan
Est. Level of
Effort:
40 hrs Owner: Project Manager
Resources Needed: Subject Matter Experts Work
Products:
MS Project Plan
Description of
Task:
Development of a detailed project plan that lists all key resources,
tasks, milestones, dependencies, and durations.
Input: 1. Approved Project Charter
2. SMEs
Dependencies: 3. Approval of Budget
Risk: 4. Changes to IT Apps plans and deliverables
5. IT Apps implementation releases, which conflict with
implementation
WBS #: 1.1.2 Work Item: Make Budget
Est. Level of
Effort:
16 hrs. Owner: Project Manager
Resources Needed: CFO, CIO, Executive
Sponsor
Work
Products:
ITPR
Description of
Task:
Development and documentation of the project budget based on
plan and resources.
Input: 6. Approved Project Charter
7. SMEs
Dependencies: 8. Approval of Project Charter
Risk: 9. Collapse of house
WBS FIELDS
WBS
#
Task Description of Task
Work
Products
Owners
Est. Level
of Effort
1 PLANNIN
G
All task management and
management activities
1.1 Plan and
Supervise
Roll-up Task Project
Manager
N/A
1.1.
1
Create Plan Development of WBS, work
package identification,
schedule formulation,
staffing projection, resource
estimation. Followed by
development of a detail
project plan that list all the
key resources, task,
milestones, dependencies,
and duration.
WBS,
WBS
Dictionary,
MS Project
Plan
Project
Manager
40 hrs
1.1.
2
Create
Budget
Development and
documentation of the project
budget based on plan and
resources
ITPR Project
Manager
40 hrs
1.1.
3
Prepare
Disburseme
nt /
Reconciliati
on
Development of
disbursement process for the
project including
acceptan.
People are facing great deal of difficulties on Project Management such as steep learning curve and high costs hiring certified professionals. Visual Paradigm's unique lifecycle guide-through process provides all the help and guidance for jumpstarting IT project management with minimal costs. Learn More: https://www.visual-paradigm.com
Comparing Stability and Sustainability in Agile SystemsRob Healy
Copy of the presentation given at XP2024 based on a research paper.
In this paper we explain wat overwork is and the physical and mental health risks associated with it.
We then explore how overwork relates to system stability and inventory.
Finally there is a call to action for Team Leads / Scrum Masters / Managers to measure and monitor excess work for individual teams.
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies™ in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
Public Speaking Tips to Help You Be A Strong Leader.pdfPinta Partners
In the realm of effective leadership, a multitude of skills come into play, but one stands out as both crucial and challenging: public speaking.
Public speaking transcends mere eloquence; it serves as the medium through which leaders articulate their vision, inspire action, and foster engagement. For leaders, refining public speaking skills is essential, elevating their ability to influence, persuade, and lead with resolute conviction. Here are some key tips to consider: https://joellandau.com/the-public-speaking-tips-to-help-you-be-a-stronger-leader/
A presentation on mastering key management concepts across projects, products, programs, and portfolios. Whether you're an aspiring manager or looking to enhance your skills, this session will provide you with the knowledge and tools to succeed in various management roles. Learn about the distinct lifecycles, methodologies, and essential skillsets needed to thrive in today's dynamic business environment.
Employment PracticesRegulation and Multinational CorporationsRoopaTemkar
Employment PracticesRegulation and Multinational Corporations
Strategic decision making within MNCs constrained or determined by the implementation of laws and codes of practice and by pressure from political actors. Managers in MNCs have to make choices that are shaped by gvmt. intervention and the local economy.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
Integrity in leadership builds trust by ensuring consistency between words an...Ram V Chary
Integrity in leadership builds trust by ensuring consistency between words and actions, making leaders reliable and credible. It also ensures ethical decision-making, which fosters a positive organizational culture and promotes long-term success. #RamVChary
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Enriching engagement with ethical review processesstrikingabalance
New ethics review processes at the University of Bath. Presented at the 8th World Conference on Research Integrity by Filipa Vance, Head of Research Governance and Compliance at the University of Bath. June 2024, Athens
1. Page 1 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
The WBS is a view into the project that illustrates the work the project encompasses. 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 some of the popular layouts
from which you can choose. Different layouts may be more suitable for different purposes (presentations vs.
plan documentation, for example).
In order to save space in this template we only developed the WBS examples down to the third level. In your
project you may want to develop them further.
Note: Instructions for what to include in each section appear in gold italics.
WORK BREAKDOWN STRUCTURE:
PROJECT NAME
CONTENTS
Outline View .........................................................................................................................................................................2
Hierarchical Structure.........................................................................................................................................................3
Tabular View.........................................................................................................................................................................4
Tree Structure View.............................................................................................................................................................5
WBS Dictionary....................................................................................................................................................................5
Glossary of Terms................................................................................................................................................................7
2. Page 2 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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
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
3. Page 3 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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
too large to fit into a document.
Level WBS Code Element Name
1 1 Widget Management System
2 1.1 Initiation
3 1.1.1 Evaluation & Recommendations
3 1.1.2 Develop Project Charter
3 1.1.3 Deliverable: Submit Project Charter
3 1.1.4 Project Sponsor Reviews Project Charter
3 1.1.5 Project Charter Signed/Approved
2 1.2 Planning
3 1.2.1 Create Preliminary Scope Statement
3 1.2.2 Determine Project Team
3 1.2.3 Project Team Kickoff Meeting
3 1.2.4 Develop Project Plan
3 1.2.5 Submit Project Plan
3 1.2.6 Milestone: Project Plan Approval
2 1.3 Execution
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 Testing Phase
3 1.3.7 Install Live System
3 1.3.8 User Training
3 1.3.9 Go Live
2 1.4 Control
3 1.4.1 Project Management
3 1.4.2 Project Status Meetings
3 1.4.3 Risk Management
3 1.4.4 Update Project Management Plan
2 1.5 Closeout
3 1.5.1 Audit Procurement
3 1.5.2 Document Lessons Learned
3 1.5.3 Update Files/Records
3 1.5.4 Gain Formal Acceptance
3 1.5.5 Archive Files/Documents
4. Page 4 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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 Level 2 Level 3
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 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
5. Page 5 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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. Microsoft Visio is also useful for creating this view.
WBS DICTIONARY
Widget Mgmt. System
1
Initiation
1.1
Evaluation &
Recommendations
1.1.1
Develop Project Charter
1.1.2
Deliverable: Submit
Project Charter
1.1.3
Project Sponsor Reviews
Project Charter
1.1.4
Project Charter
Signed/Approved
1.1.5
Planning
1.2
Create Preliminary Scope
Statement
1.2.1
Determine Project Team
1.2.2
Project Team Kickoff
Meeting
1.2.3
Develop Project Plan
1.2.4
Submit Project Plan
1.2.5
Milestone: Project Plan
Approved
1.2.6
Execution
1.3
Project Kickoff Meeting
1.3.1
Verify & Validate User
Requirements
1.3.2
Design System
1.3.3
Procure
Hardware/Software
1.3.4
Install Development
System
1.3.5
Testing Phase
1.3.6
Install Live System
1.3.7
User Training
1.3.8
Go Live
1.3.9
Control
1.4
Project Management
1.4.1
Project Status Meetings
1.4.2
Risk Management
1.4.3
Update Project
Management Plan
1.4.4
Closeout
1.5
Audit Procurement
1.5.1
Document Lessons
Learned
1.5.2
Update Files/ Records
1.5.3
Gain Formal Acceptance
1.5.4
Archive Files/ Documents
1.5.5
6. Page 6 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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.
Level WBS Code Element Name Definition
1 1 Widget Management System All work to implement a new widget management system.
2 1.1 Initiation The work to initiate the project.
3 1.1.2 Develop Project Charter Project Manager to develop the Project Charter.
3 1.1.4 Project Sponsor Reviews Project Charter Project sponsor reviews the Project Charter.
3 1.1.5 Project Charter Signed/Approved The Project Sponsor signs the Project Charter which authorizes the Project
Manager to move to the Planning Process.
2 1.2 Planning The work for the planning process for the project.
3 1.2.1 Create Preliminary Scope Statement Project Manager creates a Preliminary Scope Statement.
3 1.2.2 Determine Project Team The Project Manager determines the project team and requests the
resources.
3 1.2.3 Project Team Kickoff Meeting The planning process is officially started with a project kickoff meeting
which includes the Project Manager, Project Team and Project Sponsor
(optional).
3 1.2.4 Develop Project Plan Under the direction of the Project Manager the team develops the project
plan.
3 1.2.5 Submit Project Plan Project Manager submits the project plan for approval.
3 1.2.6 Milestone: Project Plan Approval The project plan is approved and the Project Manager has permission to
proceed to execute the project according to the project plan.
2 1.3 Execution Work involved to execute the project.
3 1.3.1 Project Kickoff Meeting Project Manager conducts a formal kick off meeting with the project team,
project stakeholders and project sponsor.
3 1.3.2 Verify & Validate User Requirements 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.
3 1.3.3 Design System The technical resources design the new widget management system.
3 1.3.4 Procure Hardware/Software The procurement of all hardware, software and facility needs for the project.
3 1.3.6 Testing Phase The system is tested with a select set of users.
3 1.3.7 Install Live System The actual system is installed and configured.
3 1.3.8 User Training All users are provided with a four hours training class. Additionally,
managers are provided with an additional two hours class to cover advanced
reporting.
3 1.3.9 Go Live System goes live with all users.
2 1.4 Control The work involved for the control process of the project.
3 1.4.1 Project Management Overall project management for the project.
3 1.4.2 Project Status Meetings Weekly team status meetings.
3 1.4.3 Risk Management Risk management efforts as defined in the Risk Management Plan.
2 1.5 Closeout The work to close-out the project.
3 1.5.1 Audit Procurement 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.
3 1.5.2 Document Lessons Learned Project Manager along with the project team performs a lessons learned
meeting and documents the lessons learned for the project.
3 1.5.3 Update Files/Records All files and records are updated to reflect the widget management system.
3 1.5.4 Gain Formal Acceptance The Project Sponsor formally accepts the project by signing the acceptance
document included in the project plan.
7. Page 7 of 7
WORK BREAKDOWN STRUCTURE: < PROJECT
NAME>
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.
Level of Effort: Level of Effort (LOE) is how much work is required to complete a task.
WBS Code: A unique identifier assigned to each element in a Work Breakdown Structure for the purpose
of designating the elements hierarchical location within the WBS.
Work Package: A Work Package is a deliverable or work component at the lowest level of its WBS branch.
WBS Component: 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.
WBS Element: 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.