Loading…
Milestone map
3 milestones
Define Project Scope and Stakeholder Requirements
2–3 weeks (3–4 hrs/week)
Select a real or realistic engineering project to plan — a product development, infrastructure upgrade, system implementation, or similar. Define the project scope through a Work Breakdown Structure (WBS) that decomposes the project into ≥15 work packages. Identify all stakeholders and their requirements. A clear WBS and stakeholder map prevent scope creep — the leading cause of engineering project failure.
Proof required
Submit your scope document: WBS with ≥15 work packages (at least 3 levels of decomposition), stakeholder register (name, role, requirement, influence level), and project objectives statement (specific, measurable, achievable, relevant, time-bound).
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Build the Schedule, Resource Plan, and Risk Register
3–4 weeks (4–5 hrs/week)
Using the WBS from M1, build a project schedule: estimate durations for each work package, establish task dependencies, and produce a Gantt chart identifying the critical path. Build a resource plan: assign people, equipment, or materials to each task with hours and costs. Build a risk register: identify ≥8 project risks, assess likelihood and impact (1–5 scale), and define a mitigation action for each risk above a threshold score. These three documents together constitute a project baseline that can be managed against.
Proof required
Submit your project schedule (Gantt chart with critical path highlighted), resource plan (resource histogram or hours/cost table per task), and risk register (≥8 risks with likelihood, impact, score, and mitigation).
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Write the Project Plan Document and Present for Review
2–3 weeks (2–3 hrs/week)
Compile all three documents (WBS/scope, schedule/resource plan, risk register) into a single integrated project plan document (2,000–3,000 words plus appendices). Add sections for: quality plan (how deliverables will be checked), communication plan (who gets what information, how often), and change control process (how scope changes will be managed). Present the plan to a reviewer with project management or engineering management experience. A plan that cannot survive a review challenge is not yet a plan.
Proof required
Submit your project plan document (2,000–3,000 words plus appendices) and review record: reviewer name, role, ≥3 challenge questions asked, and your responses.
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Part of