Section_J_Attachment_4_Notional_CWBS.DOCX

DOCX document 19 KB Posted

Attached to
Joint Service Provider Software Defined Networking (SDN) Federal contract opportunity
Solicitation number
18-233-SOL-00004
Issued by
Department of Health and Human Services Program Support Center

About this file

Section J_Attachment 4_Notional CWBS

View the file

Other files for this federal contract opportunity

Other files attached to Joint Service Provider Software Defined Networking (SDN), newest first.
File Type Posted
GOVT_CLARIFICATIONS_7_May_2018.xlsx XLSX spreadsheet
Amendment_A0002_Section_J_Attachment_1_SOO_TRACKED_CHANGES.pdf PDF
Amendment_A0001_Section_J_Attachment_1_SOO_TRACKED_CHANGES.pdf PDF
18-233-SOL-00004-A0002_REQUEST_FOR_PROPOSAL_CONFORMED_COPY.pdf PDF
Amendment_A0002_Section_J_Attachment_2b_dd0254_form.pdf PDF
GOV'T_RESPONSE_TO_QUESTIONS_23_Apr_2018.xlsx XLSX spreadsheet
Amendment_A0001_Section_J_Attachment_11_SDN_Enviornmental_Doc.pdf PDF
18-233-SOL-00004-Amendment_A0001_RFP_23_April_2018.pdf PDF
Amendment_A0001_Section_J_Attachment_1_Statement_Of_Objectives.pdf PDF
Section_J_Attachment_3_Notional_Contractor_PWS.doc DOC document
Section_J_Attachment_2a_dd0254-Inst.pdf PDF
Section_J_Attachment_9_Disclosure_of_Lobbying_Activities_Form.pdf PDF
Section_J_Attachment_8_Past_Performance_Questionnaire.docx DOCX document
Section_J_Attachment_5a_Sample_Project_Management_Plan_Template.doc DOC document
Section_J_Attachment_12_-_Wage_Determination.pdf PDF
Section_J_Attachment_11_SDN_Environmental_Document.pdf PDF
Section_J_Attachment_6_Quality_Control_Quality_Assurance_Plan.doc DOC document
Section_J_Attachment_10_HHS_508_Product_Accessibility_Template.dotx DOTX file
18-233-SOL-00004_REQUEST_FOR_PROPOSAL.pdf PDF
Section_J_Attachment_5b_Sample_Project_Plan_Template.xls XLS spreadsheet
Section_J_Attachment_7_Staffing_Allocation_and_Management_Plan_Template.xls XLS spreadsheet
Section_J_Attachment_1_Statement_Of_Objectives_-SOO.pdf PDF
Section_J_Attachment_2b_dd0254_form.pdf PDF
18_233_00004_Pre-Solicitation_Notice_JSP_NETMOD.docx DOCX document
JSP_Site_Visit_Instructions__2_Oct_2017.pdf PDF
Show all 25

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

WORK BREAKDOWN STRUCTURE (WBS) TEMPLATE

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 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.7Install 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.

Level
WBS Code
Element Name
1
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

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 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.7Install 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

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.

File details come from the government source that posted it.