E062 Applied Project Management Capstone, catalog number PJMG 3100, is the four-competency-unit course that closes WGU's project management sequence by asking you to do all of it at once on a single real-world project. Everything the earlier courses taught separately arrives here as one connected artifact set: scope decomposed, schedule built, budget derived, risks registered, stakeholders planned for, an approach chosen and defended. The failure mode is almost never ignorance. It is internal inconsistency, because seven separate assignments have been stapled together instead of built from one spine.
What PJMG 3100 is actually testing
A capstone tests integration, and integration is checkable. If your work breakdown structure contains eleven work packages, your budget should cost eleven work packages. If your risk register names a vendor delay as your top exposure, your schedule should show the activities that would slip and your contingency should be sized against it. If you chose an adaptive approach in the methodology section, your reporting plan should not describe a monthly phase-gate review. Evaluators reading a capstone move between artifacts on purpose, and every mismatch they find weakens the aspect covering the artifact they found it in.
The second thing under test is realism. Capstones ask for a real-world project, which usually means one you can describe with actual constraints rather than an invented scenario with convenient numbers. Real projects have awkward dependencies, unavailable people and budgets that do not divide neatly. A capstone with round figures, evenly spaced milestones and no resource conflicts reads as constructed backwards from a template.
The third is professional voice. At capstone level the reader is not a professor being shown that you learned things. The reader is a sponsor deciding whether to fund the plan in front of them. That changes sentence construction: fewer statements about what project management theory says, more statements about what this project will do and what happens if it does not.
Turning the rubric into an integrated build order
Capstone scoring detail lives in your Course of Study rather than the catalog, and in a capstone the aspect count is usually higher than in the courses feeding it. Each aspect is scored independently against a three-point scale, and a 2 in each aspect passes the task. That means a capstone can be excellent in eight aspects and still come back for one, which is precisely why the artifact-by-artifact consistency check matters so much.
Where the course is assessed by performance assessment, do not write in document order. Write in dependency order: scope first, then decomposition, then estimates, then schedule, then risk, then communications, then the approach justification that has to be consistent with all of it. Writing the methodology section first is how students end up defending an approach their own schedule contradicts.
The word budget, worked. Assume nine scored aspects and directions calling for roughly 3,000 words of narrative alongside your artifacts. Reserve 200 for a project introduction and 200 for a closing on how success will be measured after handover. That leaves 2,600 across nine aspects, or about 290 each. Then move weight to the two aspects that carry a capstone: the integration or justification aspect, which usually deserves 450, and the reflection or lessons aspect if your rubric has one, which deserves 350 because it is scored on insight rather than description.
Before submitting, do a numbers pass in which you read only the figures. Every number that appears in more than one artifact should be identical in both places. This pass takes twenty minutes and catches the majority of capstone returns.
A structure that fits an integrated capstone
Your task directions define the required components and they override everything below. Where the arrangement is yours, this order keeps the artifacts consistent because each one is built from the one above it.
| Component | What belongs in it | What it must agree with |
|---|---|---|
| Project and business case | The organization, the problem, the benefit and the sponsor's decision | Sets the goal every later justification refers back to |
| Scope and exclusions | Deliverables, acceptance conditions and what is deliberately outside | The work breakdown structure, which may contain nothing outside this |
| Work breakdown structure | Numbered hierarchy down to work packages | Budget lines and schedule activities, one to one |
| Schedule | Activities, durations, dependencies and the longest path | The risk register's delay exposures and the phased budget |
| Budget | Resource-derived cost by package, phased across time, with reserves | The structure above it and the contingency in the risk plan |
| Risk register | Cause, event, consequence, rating, owner, response, trigger | Schedule float, reserve sizing and stakeholder concerns |
| Communications plan | Audience, message, channel, frequency, sender, feedback route | The approach you selected and the governance it implies |
| Approach justification | The methodology chosen and why, given this project's characteristics | Every artifact above, especially reporting and change handling |
Number your work packages once and use those identifiers in every artifact afterwards. It is the cheapest possible integration device and it makes the evaluator's cross-checking work in your favour rather than against you.
Evidence craft in a capstone
Capstones carry the heaviest evidence load in the sequence because they make the most claims. The standard rises accordingly.
- Document the real project honestly. Where you cannot disclose organizational detail, anonymize and say that you have, rather than inventing replacements that make the numbers behave.
- Give every estimate a basis, and keep the bases in one place so an evaluator can find them without hunting.
- Trace each artifact to the one before it. A short sentence saying where a figure came from prevents an entire category of doubt.
- Cite standards and frameworks in APA where the rubric names citation, and apply them rather than summarizing them.
- Keep quoted material minimal and attributed. WGU scans submissions for authenticity, and capstones are long enough that borrowed passages stand out.
- Include a limitations paragraph. Capstone projects have gaps, and naming them reads as command of the material rather than as weakness.
If your capstone includes reflection, write it as analysis rather than gratitude. What surprised you, which assumption failed first, and what you would decide differently with the same information are the sentences that score.
What separates Competent from a returned capstone
A capstone resolves to Competent or Not Competent like everything else at WGU, with no letter grades and no ordinary grade point average. Performance assessment work can be revised and resubmitted without a grade penalty, but a capstone return is the most expensive kind because the document is long and the evaluator queue sits between each attempt.
Capstones that pass on the first read consistently show:
- One set of identifiers used across every artifact.
- Budget totals that reconcile to the work breakdown structure exactly.
- Schedule arithmetic that reproduces from the stated durations and dependencies.
- Risk responses whose costs appear somewhere in the budget.
- A communications plan consistent with the governance implied by the chosen approach.
- A justification section that argues from this project's characteristics rather than from methodology preference.
Closing a four-CU capstone inside the term you started it is what makes the flat-rate structure pay. Terms run six months at one price, so the difference between finishing in month five and slipping into a new term is the entire cost of another term.
Six mistakes that send capstones back
- Stapling the earlier assignments together. Seven good documents that disagree with each other score worse than one coherent plan.
- Renaming the work between artifacts. If the budget calls it site preparation and the schedule calls it groundwork, the evaluator cannot verify either.
- Choosing the approach first. Justification written before the artifacts almost always ends up contradicting them.
- Round numbers everywhere. Real projects do not produce even totals, and evenness signals a scenario built to be easy.
- Leaving risk responses uncosted. A mitigation with a real action and no money behind it is not a plan.
- Writing reflection as summary. Restating what you did earns nothing. Naming what you got wrong and why earns the aspect.
How support works on this course
Capstone support is mostly consistency work, because that is where capstones fail. Send the rubric from your Course of Study, the task directions and every artifact you have drafted. The work comes back with a cross-artifact reconciliation: identifiers unified, budget totals recomputed against the structure, schedule arithmetic checked by hand, risk responses matched to reserve lines, and the approach justification rewritten so it argues from your own project's characteristics.
The aim is one submission rather than three. In a four-CU capstone at the end of a six-month term, the difference between one clean pass and two rounds through the evaluator queue is frequently the difference between finishing the program this term and paying for another one.
Questions students ask about E062
Is E062 the same course as PJMG 3100?
Can I use a project from my job for the capstone?
What is the single most common reason a capstone comes back?
Capstone artifacts contradicting each other?
Send the rubric, the task directions and every draft artifact. You get a full cross-artifact reconciliation with totals recomputed, schedules checked by hand and identifiers unified.
Where E062 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.