MGMT 625 Week 6 Work Breakdown Structure Example

Reviewed by Thomas Kerrigan, MBA, CPA · Liberty University · Updated

This MGMT 625 Week 6 sample is the Work Breakdown Structure, the 135-point assignment in Liberty University MGMT 625 that turns the Week 4 Project Management Plan into deliverables, written for the MS in Project Management with Wilson's chapters 8 and 9. The guide asks for one to two pages, in hierarchical or mind map form, giving a WBS or a Gantt chart for the project already planned, built in Excel, Word or Microsoft Project. This sample breaks the city's 14,200-light LED and smart-control conversion into six level-two deliverables and 31 work packages, numbered in outline form, with installation divided by the city's eight maintenance districts. A short summary schedule shows when each deliverable runs across the fourteen months, and a note explains how the structure follows the 100 percent rule.

CourseMGMT 625 Project Planning & Scheduling (MGMT625)
Module/Week6
AssignmentWork Breakdown Structure
Paper typeWork breakdown structure in hierarchical outline form with summary schedule
Lengthabout 465 words, 2 double-spaced pages plus title page and references. Course guide: per the course guide, a 1-2-page work breakdown structure or Gantt chart in hierarchical or mind map format for the project in the student's Project Management Plan, created in Excel, Word or Microsoft Project
FormatAPA 7 student paper
Points135
SchoolLiberty University Online
ProgramMS in Project Management
Where it sitsModule/Week 6 in Liberty's published MGMT 625 course guide; current sections can differ
UpdatedOctober 2026

Free sample paper for MGMT 625 Week 6

1

Work Breakdown Structure: The City Streetlight LED Conversion

 

[Student Name]

School of Business, Liberty University

MGMT 625: Project Planning & Scheduling

Work Breakdown Structure

[Instructor Name]

[Date]

 

The streetlight project and its figures are the composite planned in this sample's Week 4 Project Management Plan; the PMBOK Guide, Wilson's text and the study cited are real; the requirements follow Liberty's public course guide for MGMT 625.

2

Work Breakdown Structure: The City Streetlight LED Conversion

How the Structure Was Built

Why this part earns its pointsThe note explains where the structure came from, the plan's scope lists, so the grader can check the two documents against each other.
3

The structure decomposes the scope statement of the Project Management Plan, using its list of included deliverables and leaving out everything on its exclusion list, such as pole replacement and the downtown decorative lights. It is organized by deliverable, as the PMBOK Guide recommends, so that each element names something the project produces (Project Management Institute, 2017), and installation is broken down by maintenance district because districts are the units the city schedules and reports.

Work Breakdown Structure

  • 1. 1.0 City Streetlight LED Conversion
  • 1.1 Managing the Conversion: 1.1.1 Approved schedule, budget and scope baselines; 1.1.2 Biweekly sponsor reports and quarterly council briefings; 1.1.3 Risk register and change control; 1.1.4 Closeout report
  • 1.2 Design and Procurement: 1.2.1 Fixture and node specifications; 1.2.2 Installation contract award; 1.2.3 Fixture and node purchase in monthly lots; 1.2.4 Pole ownership survey with the utility
  • 1.3 Pilot: 1.3.1 Pilot installation on two residential streets; 1.3.2 Resident meeting and feedback; 1.3.3 Pilot evaluation and specification adjustment
  • 1.4 Installation by District: 1.4.1 District 1 (priority); 1.4.2 District 2 (priority); 1.4.3 District 3; 1.4.4 District 4; 1.4.5 District 5; 1.4.6 District 6; 1.4.7 District 7; 1.4.8 District 8. Each district package includes resident notices, fixture replacement, control node installation and city inspection.
  • 1.5 Control System: 1.5.1 Security review and approval; 1.5.2 Central management software configuration; 1.5.3 Network gateway installation; 1.5.4 District integration and node testing; 1.5.5 Work order system integration
  • 1.6 Verification and Handover: 1.6.1 Photometric survey of 40 sample streets; 1.6.2 Public works staff training; 1.6.3 Punch list repairs; 1.6.4 Final acceptance and contract closeout

Summary Schedule

Why this part earns its pointsThe summary schedule shows every level-two deliverable placed in time, proof that the structure can be scheduled.
4

The table places each level-two deliverable in the fourteen-month schedule, so the structure can be checked against the plan's phases.

DeliverableMonths 1-2Months 3-6Months 7-10Months 11-12Months 13-14
1.1 Managing the ConversionXXXXX
1.2 Design and ProcurementXX
1.3 PilotX
1.4 Installation (Districts 1-8)Districts 1-4Districts 5-7District 8
1.5 Control SystemXXXX
1.6 Verification and HandoverX

Notes on the Structure

Why this part earns its pointsThe closing note ties the structure to the 100 percent rule and to change control, which shows the WBS is a management tool rather than a drawing.
5

The structure contains 31 work packages, counting each of the eight district packages once. Every work package has a single owner named in the plan's responsibility matrix: the contractor for district installation, the IT lead for the control system packages, the lighting engineer for specifications and the photometric survey, and the project manager for the rest. The structure follows the 100 percent rule: the six level-two deliverables together contain all of the project's scope, and nothing the plan excludes appears in it. Wilson (2014) treats the WBS as the base for the cost and schedule baselines, and each work package here will carry its own budget and dates in the detailed schedule. If a change adds or removes scope, the WBS changes first, and the schedule and budget follow it. The district packages also give the city a simple measure of progress, eight milestones that residents and council members can see, which supports the communication plan's quarterly briefings. The contingency, sized from comparable city conversions as Flyvbjerg (2006) suggests, is held at the project level rather than inside any work package, so that it can be tracked as one reserve.

6

References

Flyvbjerg, B. (2006). From Nobel Prize to project management: Getting risks right. Project Management Journal, 37(3), 5-15. https://doi.org/10.1177/875697280603700302

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.).

Wilson, R. (2014). A comprehensive guide to project management schedule and cost control. Pearson FT Press.

What the MGMT 625 Week 6 instructions ask

The Work Breakdown Structure is due in Module/Week 6 of MGMT 625, with Wilson's chapters 8 and 9, two presentations and the Forum 3 replies, and it is worth 135 points, second only to the Project Management Plan. The guide's instructions are short. Students submit either a breakdown structure or a Gantt view of the project from their Project Management Plan, in a hierarchical or mind map format, one to two pages long, built in Microsoft Excel, Word or Project. Because the plan has already defined the scope, the WBS should break down exactly that scope, so a reader can compare the two documents and find every deliverable of the plan in the structure and nothing that the plan excluded. A brief summary schedule helps show that the structure can be scheduled.

How this MGMT 625 Week 6 example is built

The sample opens with two sentences on how the structure was built, from the plan's scope statement and its in and out lists. The outline then gives the project at level one and six deliverables at level two: project management, design and procurement, a pilot, installation, the control system, and verification and handover. Installation is broken down by maintenance district, because districts are the units the city sequences and reports, and each district package names its four elements, notices, fixtures, nodes and inspection. The control system has its own branch, since its security review and integration run on a different path. A summary schedule table places each deliverable in the fourteen months, and a closing note ties the structure to the 100 percent rule and to the plan's change thresholds.

MGMT 625 Week 6 grading rubric: where the points go

The WBS is graded on whether it decomposes the planned project correctly and clearly. Graders look for a hierarchy that starts from the whole project, breaks into major deliverables and bottoms out in packages one owner could price and schedule; for consistency with the Project Management Plan's scope; and for a format the guide accepts, hierarchical, mind map or Gantt, within one to two pages. A structure organized by deliverable rather than by department, with clear numbering, scores better than a task list. Covering the planned scope completely without adding to it, as the 100 percent rule requires, shows command of the concept, and a summary schedule or Gantt view shows that the structure can actually be scheduled.

MGMT 625 Week 6 help: mistakes that cost points

The most frequent error is a WBS that lists activities in time order, such as plan, buy, install, test, without showing what is delivered. Name deliverables, written as nouns, and break them down until each piece could be estimated and assigned to one owner. Check the structure against the plan's scope: every included item should appear and every excluded item should be absent. Do not exceed two pages; if the outline grows, keep work packages at a sensible size rather than listing every task. Number every element in one consistent outline style, so a grader can match the WBS to the plan line by line. If you add a Gantt view, keep it at the level of deliverables so it fits, and make sure its durations agree with the plan's schedule.

Related MGMT 625 sample papers

Other MGMT 625 weeks

More MS in Project Management sample papers

MGMT 625 Week 6 questions, answered

What is the MGMT 625 Work Breakdown Structure assignment?

A 135-point Module/Week 6 assignment: a one-to-two-page WBS or Gantt chart, in hierarchical or mind map format, for the project in the student's Project Management Plan.

Where can I find a free MGMT 625 Week 6 sample paper?

A complete MGMT 625 Week 6 work breakdown structure for a city's streetlight LED conversion, with numbered work packages and a summary schedule, is reproduced on this page.

Can the MGMT 625 WBS be a Gantt chart?

Yes; a Gantt chart is as acceptable to the guide as a breakdown outline, presented in hierarchical or mind map format, built in Excel, Word or Microsoft Project.

How detailed should a work breakdown structure be?

Detailed enough that each lowest-level work package can be estimated, scheduled and assigned to one owner, but not so detailed that it becomes a list of individual tasks.

Should a WBS follow the project management plan?

It should decompose exactly the scope the plan defines, so every included deliverable appears in the WBS and nothing the plan excluded does.

Use it as a model, or ask for your own

This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.