15 years of academic expertise Trusted by students in 27 countries
Student studying with an online tutor

Free 15-minute tutor consultation

A tutor reviews your brief and the Pass, Merit and Distinction criteria with you and gives you a clear plan for your own work.

HND Assignment Help logo
BM522 Project Management CW1: Critical Path, Gantt Charts & WBS

BM522 Project Management CW1: Critical Path, Gantt Charts & WBS

BM522 CW1 requires you to build a network diagram showing the critical path, convert it into a Gantt chart, and create a work breakdown structure. The critical path is the longest chain of dependent activities; Gantt charts visualise timescales; a WBS breaks the project into deliverable-driven components. Accuracy in calculations and clarity in presentation are marked heavily.

Stuck on Project Management - Critical Path, Gantt Charts and Work Breakdown Structure? Get free 1:1 guidance from a UK tutor – reply in minutes. 💬 Chat on WhatsApp
Qualification Pearson BTEC HND in Business
Level Level 5
Unit/Module BM522 Project Management
Assessment Type CW1 – Project Report
Typical Word Count 1,500–2,500 words
Key Deliverables Critical path analysis, Gantt chart, WBS, stakeholder analysis, risk register

What BM522 CW1 is really asking

BM522 Project Management CW1 is not a theoretical essay. It's a practical demonstration of planning tools applied to a real (or realistic) project scenario. Your markers are looking for:

  • Accuracy: Can you calculate the critical path without arithmetic errors?
  • Visual clarity: Does your Gantt chart make dependencies and timescales obvious?
  • Structural thinking: Can you decompose a complex project into logical, manageable parts?
  • Professional reasoning: Do you justify your choices—why these activities, why this timeline, why these risks?

The assessment typically splits into five or six tasks:

  1. Project Management Plan (PMP) – Justify the project, define scope and objectives, outline methodology.
  2. Network diagram and critical path – Calculate durations, dependencies, early/late start and finish times, identify slack.
  3. Gantt chart – Visualise the schedule, showing bars, dependencies (arcs), milestones, and critical path highlighting.
  4. Work Breakdown Structure (WBS) – Decompose deliverables hierarchically into work packages.
  5. Stakeholder analysis – Map power and interest; plan communication and management strategies.
  6. Risk analysis and quality expectations – Identify project threats, mitigation, and quality standards.

A sensible word and effort split

You have roughly 1,500–2,500 words to cover a lot of ground. Don't panic: diagrams, tables and charts count toward word count and reduce the burden of description.

Section Words Focus
Project justification & scope 300–400 Why is this project needed? What are the deliverables and constraints?
Critical path explanation 250–350 Explain the method, your activity list, durations, dependencies. Include or reference a table of forward/backward pass data.
Gantt chart and schedule 150–250 Describe the chart, highlight critical path activities, note key milestones and buffers.
WBS narrative 150–250 Explain how you broke down the project. Show the hierarchical structure visually (diagram or tree) and describe each level.
Stakeholder analysis 300–400 Identify key stakeholders, map their power and interest, describe management and communication strategies.
Risk & quality 250–350 Identify risks, assess likelihood and impact, propose mitigation, define quality standards.
Conclusion & reflection 100–150 Summarise your approach; reflect on project constraints and your learning.

Tip: Let visuals do the heavy lifting. A well-constructed network diagram, Gantt chart and WBS diagram can replace hundreds of descriptive words.

How to calculate the critical path without mistakes

This is where many students lose marks. Here's the step-by-step method.

Step 1: List your activities and durations

Create a table with activity codes (A, B, C... or 1, 2, 3...), descriptions, durations (in days, weeks, or relevant units), and predecessor(s).

Example:
Activity | Description             | Duration (days) | Predecessor(s)
A        | Establish project scope | 5                | —
B        | Design phase            | 10               | A
C        | Procurement             | 15               | A
D        | Build/develop           | 20               | B, C

Step 2: Forward pass (calculate early start and early finish)

Start from day 0 (or day 1—be consistent). For each activity:

  • Early Start (ES) = maximum Early Finish of its predecessor(s).
  • Early Finish (EF) = ES + Duration.

Key rule at merge points: When multiple paths meet (e.g., activity D depends on both B and C), the ES of D is the latest EF of its predecessors. This is a common error: students pick the earliest predecessor instead of waiting for all to finish.

Step 3: Backward pass (calculate late start and late finish)

Start from the final activity's EF (the project completion date). Working backwards:

  • Late Finish (LF) = minimum Late Start of its successor(s).
  • Late Start (LS) = LF − Duration.

Again, at split points (where one activity feeds multiple successors), LF is the minimum LS of all successors.

Step 4: Calculate slack (or float)

Slack (or Total Float) = LS − ES (or LF − EF).

  • Slack = 0 → Critical activity. Any delay slides the whole project.
  • Slack > 0 → Non-critical. This activity has buffer time.

The critical path is the continuous chain of activities from start to finish where every activity has zero slack.

The three merge points that trip students up

Merge 1: Multiple predecessors to one activity

If activity D depends on B (EF = day 15) and C (EF = day 20), then ES of D = day 20 (the latest). Don't use day 15.

Merge 2: Multiple successors from one activity

If activity E finishes on day 25 and feeds into G (LS = day 24) and H (LS = day 28), then LF of E = day 24 (the earliest). Don't use day 28.

Merge 3: Parallel paths converging

When two independent chains of activities meet, treat it as a single merge point. Use the latest EF from either chain for the ES of the next activity.

Pro tip: Build your forward and backward pass in an Excel spreadsheet or table. Use formulas to avoid re-calculating and catching errors becomes easier. Always double-check that your final EF matches your final LF at the project end.

Stuck on BM522 Project Management CW1: Critical Path, Gantt Charts & WBS?

Send us your brief. A UK tutor will explain what the marking criteria are asking for and help you plan your answer. Your first consultation is free.

WhatsApp a tutorGet a free quoteCall us

Turning the calculation into a Gantt chart

Now you've got your critical path; it's time to visualise it.

What your Gantt chart must show

  • Activity bars – One horizontal bar per activity, positioned at its ES and extending for its duration.
  • Critical path highlighting – Use red, bold or a distinct fill colour for critical activities.
  • Non-critical (slack) buffer – Show float visually, often as a lighter or dashed bar behind or alongside the main bar.
  • Dependencies – Draw arrows or lines linking predecessors to successors, or use task links if in Microsoft Project.
  • Milestones – Mark key dates (project start, design sign-off, go-live, etc.) as diamonds or vertical lines.
  • Time axis – Clearly label days, weeks, or months. Ensure your horizontal scale is consistent and easy to read.

Tools for building a Gantt chart

Microsoft Project: Industry standard. Automatically calculates critical path and displays Gantt charts professionally. If you have access, use it—but it's not essential.

Excel or Google Sheets: Build it manually using conditional formatting, stacked bar charts, or simply a grid with coloured cells. Clear and effective. Many markers prefer hand-built charts because they show your reasoning.

Online tools: Smartsheet, Asana, Monday.com, or even Lucidchart. These often auto-link dependencies, but you'll still need to input data accurately.

Key point: Pearson doesn't prescribe the tool. Accuracy, clarity, and your ability to interpret the chart matter far more than the software.

Building a coherent Work Breakdown Structure

A WBS is not a task list in sequence. It's a hierarchical decomposition of project deliverables.

How to structure a WBS

Level 1 (Root): The entire project (e.g., "Regent House Hotel Renovation Project").

Level 2 (Major phases or domains): Break into broad categories—often by project phase (Planning, Design, Build, Testing, Handover) or by business area (Technical, Commercial, HR, Compliance).

Level 3 (Work packages): Break each level 2 element into smaller, deliverable-focused chunks (e.g., "Design" → "Architectural Design," "MEP Design," "BIM Model Preparation").

Level 4+ (Optional): If the project is very complex, further decompose into tasks or activities. But don't over-elaborate.

Link WBS to your network diagram

Each work package or activity in your network diagram should trace back to a WBS element. This shows that you haven't invented random tasks; every activity contributes to a defined deliverable.

How to present your WBS

  • Tree diagram: Visual hierarchy, easy to scan. Use drawing tools or even PowerPoint SmartArt.
  • Indented outline: Simple text hierarchy (1.0 → 1.1 → 1.1.1, etc.).
  • Table: Columns for WBS code, description, associated activities, and deliverables.

Stakeholder analysis: power, interest and communication

Your BM522 coursework almost certainly includes a stakeholder analysis. Here's the framework:

The power-interest matrix

Plot each stakeholder on two axes:

  • Horizontal (Power): How much influence does this person or group have over the project?
  • Vertical (Interest): How much do they care about the outcome?

This gives four quadrants:

  • High Power, High Interest (Manage closely): Project sponsor, senior client contact. Weekly updates, seek approval on major decisions.
  • High Power, Low Interest (Keep satisfied): Senior budget holder, regulators. Monthly summary reports; flag risks early.
  • Low Power, High Interest (Keep informed): Project team, end users. Regular progress updates, involve in design decisions.
  • Low Power, Low Interest (Monitor): Occasional vendors, junior staff. Annual reviews or as needed.

Identify 4–6 key stakeholders. Justify your selection (why are they important to your project?). Then, for each, state:

  • Their role and position.
  • Their interest in the project outcome.
  • Their power or influence.
  • Your communication strategy (frequency, format, content).
  • How you'll manage their expectations or concerns.

Risk analysis: identify, assess, mitigate

A risk register is a table. For each identified risk:

  • Description: What could go wrong? (e.g., "Key team member resigns mid-project")
  • Likelihood: High, Medium, or Low (or 1–5 scale). Be realistic.
  • Impact: High, Medium, or Low. What happens if it occurs? Cost, schedule, quality, scope?
  • Risk Score: Likelihood × Impact. Prioritise those with the highest score.
  • Mitigation: What will you do to reduce likelihood or impact? (e.g., "Cross-train two team members on critical skills")
  • Owner: Who is responsible for monitoring this risk?
  • Status: Open, closed, or escalated?

Identify 6–10 risks. Quality beats quantity. Focus on risks that actually threaten your project's success, not generic fears.

Want a tutor to check your draft first?

Get clear written feedback on your own work before the deadline: structure, criteria coverage and referencing. Feedback on your own draft starts from £45, and tutoring from £32 an hour.

WhatsApp a tutorGet a free quoteCall us

Mark-maximising checklist

Before you submit:

  • Critical path: Have you calculated forward and backward pass correctly? Does your LF at project end equal your EF? Are all activities accounted for?
  • Gantt chart: Can anyone looking at it instantly spot the critical path? Are dependencies clear? Is the timescale readable?
  • WBS: Does it decompose by deliverables, not by task sequence? Can you trace each activity back to a WBS element?
  • Calculations: No arithmetic errors. Double-check slack calculations, especially at merge and split points.
  • Accuracy of durations and dependencies: Are your estimates realistic and justified? Do dependencies reflect true logical constraints, not just assumed sequence?
  • Stakeholder analysis: Do your chosen stakeholders make sense for this project? Have you justified their power and interest?
  • Risk register: Are risks specific to your project, not generic? Do mitigation strategies make sense?
  • Writing quality: Clear, professional language. No spelling or grammar errors. Use headings and tables to break up text.
  • References: Cite any sources you've used (project data, methodology frameworks, risk/stakeholder theory). Use Harvard referencing.
  • Presentation: Is the work easy to navigate? Can your markers quickly find what they're looking for?

Common mistakes to avoid

Arithmetic and logic errors in critical path

Using the earliest predecessor EF instead of the latest when activities converge. Using the latest successor LS instead of the earliest when activities split. Always pause at merge/split points and think carefully.

Confusing activity duration with calendar dates

If an activity takes 5 days and starts on day 10, it finishes on day 15—not "15 days into the calendar." Stick to relative day counts, not absolute dates (unless your brief specifically asks for calendar scheduling).

Critical path that changes with minor tweaks

If you recalculate and get a different critical path, something is wrong. The critical path shouldn't flip based on small changes in non-critical activities. Review your forward and backward pass.

WBS that mirrors the network diagram sequence

These are different tools. Your WBS is deliverable-driven and hierarchical. Your network diagram is task-driven and sequential. They must align logically, but they shouldn't have the same structure.

Vague stakeholder or risk analysis

Don't list stakeholders or risks without justification. "The client is important because they're the client" tells markers nothing. Explain why their power and interest matter, and what you'll do about it.

Missing references

If you cite methodology (e.g., critical path method, power-interest matrix, risk registers), reference your source. Use Harvard style. Even if you're recalling from lectures, cite your module handbook or the textbook.

A simple order of work

If you're starting from scratch, follow this sequence:

  1. Define the project scope and objectives. What are you building, delivering, or changing? What constraints exist? (1–2 hours)
  2. Create a preliminary WBS. Break the project into major deliverables. (30 minutes)
  3. List all activities and estimate durations. What tasks are needed to complete each work package? How long will each take? Use expert judgment, historical data, or analogous projects. (2–3 hours)
  4. Identify dependencies. Which activities must happen before others? Which can run in parallel? (1 hour)
  5. Calculate the critical path. Build your forward and backward pass table. Identify slack. Spot the critical path. (2–3 hours, including checks)
  6. Build the Gantt chart. Translate your calculations into a visual schedule. (1–2 hours, depending on tool)
  7. Identify key stakeholders and analyse their power and interest. (1 hour)
  8. Create a risk register. List threats, assess them, propose mitigation. (1–2 hours)
  9. Write the narrative and commentary. Explain your decisions, justify your approach. (2–3 hours)
  10. Proofread, check citations, review against the brief. (1 hour)

Total time commitment: 12–17 hours of focused work. If you're unfamiliar with the tools, add 2–3 hours for learning and practice.

Frequently asked questions

Which activities are on the critical path?

Critical path activities have zero slack—the difference between late finish and early finish is zero. These activities form the longest continuous chain of dependent tasks. If any slip, the whole project is delayed. Mark them clearly in your network diagram and Gantt chart.

What does the day 0 convention mean?

Day 0 is the project start. Activity durations begin counting from day 1. If activity A (5 days) starts on day 0, it finishes on day 5. This prevents off-by-one errors in your forward and backward pass calculations. Be consistent throughout.

Do I need MS Project for the Gantt chart?

No. Excel, Google Sheets, or even hand-drawn charts are acceptable if they clearly show task bars, dependencies, durations, and critical path activities. Pearson doesn't require proprietary software—clarity and accuracy matter more than the tool.

How many stakeholders do I need to analyse?

Analyse 4–6 key stakeholders: project sponsor, project manager, team members, end users, and external partners (clients, suppliers, regulators). Quality of analysis beats quantity. Use a power-interest matrix to justify each selection.

Should the WBS follow the activity order?

No. WBS is hierarchical by scope and deliverables, not by task sequence. Organise it by project phases or work packages (e.g., Planning, Execution, Monitoring). Then use the network diagram to sequence activities.

Is it acceptable to use AI tools for this coursework?

Use AI for research, brainstorming, and structure advice only. The critical path calculations, Gantt chart and WBS must be your own work—these demonstrate core competencies in planning. Check your institution's academic integrity policy.

What's the most common mistake students make?

Confusing activity duration with calendar dates, or incorrectly calculating slack at merge points (where multiple paths join). Double-check your forward and backward pass, especially where activities converge.

Deadline coming up?

Book a 1-to-1 online session today. Tutors are available 7 days a week, 8am–11pm, and usually reply within 2 hours.

WhatsApp a tutorGet a free quoteCall us

Key takeaways

  • The critical path is calculated through a disciplined forward and backward pass; accuracy at merge and split points is crucial.
  • Your Gantt chart must visually distinguish critical activities from non-critical ones, and show clear dependencies.
  • A WBS is deliverable-driven and hierarchical; it's not a task sequence.
  • Stakeholder and risk analysis show professional thinking; justify your selections and explain your strategies.
  • Always double-check calculations and present work clearly. Visual clarity often compensates for dense text.
  • Academic integrity: perform your own calculations and reasoning, though you may seek feedback or use tools to streamline presentation.

If you're writing a BM522 Project Management coursework and want feedback on your critical path calculations, Gantt chart, or WBS structure, the team at HND Assignment Help can review your work and offer practical guidance. Visit hndassignmenthelp.com to arrange a one-to-one tutorial or assignment review.

Good luck with your coursework.

===HTML===

Want an expert to check your plan for this assessment?

Share your brief on WhatsApp and a HND Assignment Help tutor will show you how to structure it, which criteria to target and what to fix – free first consultation, confidential.

💬 Get free guidance on WhatsApp

Share your brief

Send your unit brief and criteria. We match you with a tutor who knows your awarding body.

Free trial class

A 15–20 minute live session where the tutor breaks down the criteria and gives you a plan.

Learn and improve

Book more 1-to-1 sessions if it helps, and get feedback on your own drafts before you submit.