Attachment # 00007788 - Work-Breakdown-Structure_(1).doc
Work-Breakdown-Structure_(1).doc (172.5 KB)
Raw Preview of Attachment:
(refer to the detailed question and attachment below)
HYPERLINK http//www.projectmanagementdocs.com INCLUDEPICTURE http//www.120society.com/templates/fast_plans/images/logo.jpg MERGEFORMATINET 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 HYPERLINK http//www.ProjectManagementDocs.com www.ProjectManagementDocs.com Work Breakdown Structure (WBS) Project Name Company Name Street Address City, State Zip Code Date 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 youre 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. 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 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. LevelWBS CodeElement Name11Widget Management System21.1Initiation31.1.1Evaluation Recommendations31.1.2Develop Project Charter31.1.3Deliverable Submit Project Charter31.1.4Project Sponsor Reviews Project Charter31.1.5Project Charter Signed/Approved21.2Planning31.2.1Create Preliminary Scope Statement31.2.2Determine Project Team31.2.3Project Team Kickoff Meeting31.2.4Develop Project Plan31.2.5Submit Project Plan31.2.6Milestone Project Plan Approval21.3Execution31.3.1Project Kickoff Meeting31.3.2Verify Validate User Requirements31.3.3Design System31.3.4Procure Hardware/Software31.3.5Install Development System31.3.6Testing Phase31.3.7Install Live System31.3.8User Training31.3.9Go Live21.4Control31.4.1Project Management31.4.2Project Status Meetings31.4.3Risk Management31.4.4Update Project Management Plan21.5Closeout31.5.1Audit Procurement31.5.2Document Lessons Learned31.5.3Update Files/Records31.5.4Gain Formal Acceptance31.5.5Archive Files/Documents 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 1Level 2Level 31 Widget Management System1.1 Initiation1.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/Approved1.2 Planning1.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 Approval1.3 Execution1.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 Live1.4 Control1.4.1 Project Management 1.4.2 Project Status Meetings 1.4.3 Risk Management 1.4.4 Update Project Management Plan1.5 Closeout1.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 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. SHAPE MERGEFORMAT 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 theyve been assigned, so its 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. LevelWBS CodeElement NameDefinition11Widget Management SystemAll work to implement a new widget management system.21.1InitiationThe work to initiate the project.31.1.1Evaluation RecommendationsWorking group to evaluate solution sets and make recommendations.31.1.2Develop Project CharterProject Manager to develop the Project Charter.31.1.3Deliverable Submit Project CharterProject Charter is delivered to the Project Sponsor.31.1.4Project Sponsor Reviews Project CharterProject sponsor reviews the Project Charter.31.1.5Project Charter Signed/ApprovedThe Project Sponsor signs the Project Charter which authorizes the Project Manager to move to the Planning Process.21.2PlanningThe work for the planning process for the project.31.2.1Create Preliminary Scope StatementProject Manager creates a Preliminary Scope Statement.31.2.2Determine Project TeamThe Project Manager determines the project team and requests the resources.31.2.3Project Team Kickoff MeetingThe planning process is officially started with a project kickoff meeting which includes the Project Manager, Project Team and Project Sponsor (optional).31.2.4Develop Project PlanUnder the direction of the Project Manager the team develops the project plan.31.2.5Submit Project PlanProject Manager submits the project plan for approval.31.2.6Milestone Project Plan ApprovalThe project plan is approved and the Project Manager has permission to proceed to execute the project according to the project plan.21.3ExecutionWork involved to execute the project.31.3.1Project Kickoff MeetingProject Manager conducts a formal kick off meeting with the project team, project stakeholders and project sponsor.31.3.2Verify Validate User RequirementsThe 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.31.3.3Design SystemThe technical resources design the new widget management system.31.3.4Procure Hardware/SoftwareThe procurement of all hardware, software and facility needs for the project.31.3.5Install Development SystemTeam installs a development system for testing and customizations of user interfaces.31.3.6Testing PhaseThe system is tested with a select set of users.31.3.7Install Live SystemThe actual system is installed and configured.31.3.8User TrainingAll users are provided with a four hours training class. Additionally, managers are provided with an additional two hours class to cover advanced reporting.31.3.9Go LiveSystem goes live with all users.21.4ControlThe work involved for the control process of the project.31.4.1Project ManagementOverall project management for the project.31.4.2Project Status MeetingsWeekly team status meetings.31.4.3Risk ManagementRisk management efforts as defined in the Risk Management Plan.31.4.4Update Project Management PlanProject Manager updates the Project Management Plan as the project progresses.21.5CloseoutThe work to close-out the project.31.5.1Audit ProcurementAn audit of all hardware and software procured for the project, ensures that all procured products are accounted for and in the asset management system.31.5.2Document Lessons LearnedProject Manager along with the project team performs a lessons learned meeting and documents the lessons learned for the project.31.5.3Update Files/RecordsAll files and records are updated to reflect the widget management system.31.5.4Gain Formal AcceptanceThe Project Sponsor formally accepts the project by signing the acceptance document included in the project plan.31.5.5Archive Files/DocumentsAll project related files and documents are formally archived. Glossary of Terms Its 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 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 theres 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. This free WBS Template is brought to you by HYPERLINK http//www.ProjectManagementDocs.com www.ProjectManagementDocs.com HYPERLINK http//www.120society.com/ INCLUDEPICTURE http//www.120society.com/templates/fast_plans/images/logo.jpg MERGEFORMATINET Work Breakdown Structure (WBS) Template HYPERLINK http//www.ProjectManagementDocs.com www.ProjectManagementDocs.com PAGE PAGE 8 Control 1.4 Execution 1.3 Planning 1.2 Initiation 1.1 Widget Mgmt. System 1 Create Preliminary Scope Statement 1.2.1 Closeout 1.5 Project Charter Signed/Approved 1.1.5 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 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 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 Project Management 1.4.1 Project Status Meetings 1.4.2 Risk Management 1.4.3 Update Project Management Plan 1.4.4 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 wu_KO 5,WQ6rDjShZPVM, L(J DSQZx9i-c1zZSaF7iH A7sxm15TK)e5W-56Yj/fQbbxd/o/NZsOnY--k1u(iS.SkV vhXaY-zHFY_5kdJ1tWERIJcIQdhXQ LUnI@H_WfhKrSOJjA8aYt_OVYhthK Utw3RKYEu VR,NgW . oBo3EImCeYV7TPlX9 9(kfiH /)TZ/NhWr5gRh4C5J FD ovNEdlGmowQw wW5.WXbYxIDTH PKplKEZ_lfZDQ,DZ)F-4aT8gddXhsGKJQTWL(90quoP2J)JkK5_XR -6BE-Zl-6)8q9h EKarGEukR8A4dfd2 dj8lqi6Kg)) x(Vu99NIj5Cws5Nq3ikZvZ BTRmygaAU6DSyw/.iuG9lt h0Fu f Z I6l8MI ,Vp UNvF mLkjMiSJFUhF)B/k_5aCJGoZRtBVXHpyB10sa8TPKZm5y94RGjXJIIUKUPZl33)OLDCClxj/ZlvNTVT/(E P,ZDxpZ@h6C@ J2fbI_IWV43zqU_iYFYs -4y GnC wu_KO 5,WQ6rDjShZPVM, L(J DSQZx9i-c1zZSaF7iH A7sxm15TK)e5W-56Yj/fQbbxd/o/NZsOnY--k1u(iS.SkV vhXaY-zHFY_5kdJ1tWERIJcIQdhXQ LUnI@H_WfhKrSOJjA8aYt_OVYhthK Utw3RKYEu VR,NgW . oBo3EImCeYV7TPlX9 9(kfiH /)TZ/NhWr5gRh4C5J FD ovNEdlGmowQw wW5.WXbYxIDTH PKplKEZ_lfZDQ,DZ)F-4aT8gddXhsGKJQTWL(90quoP2J)JkK5_XR -6BE-Zl-6)8q9h EKarGEukR8A4dfd2 dj8lqi6Kg)) x(Vu99NIj5Cws5Nq3ikZvZ BTRmygaAU6DSyw/.iuG9lt h0Fu f Z I6l8MI ,Vp UNvF mLkjMiSJFUhF)B/k_5aCJGoZRtBVXHpyB10sa8TPKZm5y94RGjXJIIUKUPZl33)OLDCClxj/ZlvNTVT/(E P,ZDxpZ@h6C@ J2fbI_IWV43zqU_iYFYs -4y GnC Y, dXiJ(x( I_TS 1EZBmU/xYy5g/GMGeD3Vqq8K)fw9 xrxwrTZaGy8IjbRcXI u3KGnD1NIBs RuKV.ELM2fi V vlu8zH (W )6-rCSj id DAIqbJx 6kASht(QpmcaSlXP1Mh9MVdDAaVBfJP8 AVf 6Q

assignment 1-assignment

Question # 00122461 Posted By: Newguy Updated on: 10/23/2015 12:30 AM Due on: 10/27/2015
Subject Business Topic General Business Tutorials:
Question
Dot Image
assignment 1-assignment

assignment 1-assignment
Dot Image
Tutorials for this Question
  1. Tutorial # 00117143 Posted By: Davidcharles Posted on: 10/23/2015 08:26 PM
    Puchased By: 5
    Tutorial Preview
    The solution of WBS Dictionary...
    Attachments
    WBS_Dictionary._.docx (18.53 KB)
Whatsapp Lisa