E055 Project Scoping and Scheduling, catalog number PJMG 2105, is the three-competency-unit course where WGU's project management sequence stops describing projects and starts decomposing them. The work is a work breakdown structure with real activities under it, then the dependency logic that turns that structure into a schedule. It is the most mechanical course in the sequence and, for that reason, the one where returns are most avoidable. The decomposition either holds together or it does not, and a reader can tell in about ninety seconds.
What PJMG 2105 is actually testing
A work breakdown structure looks like an organizational chart and behaves like a contract. Every box is a piece of the project's total scope, every level down is a smaller piece of the box above it, and when you reach the bottom you have work packages small enough that somebody could estimate and own each one. The test in E055 is whether you understand that decomposition is subtraction, not addition. Nothing may appear at a lower level that was not already contained in the level above, and nothing contained above may go missing below.
That rule has a name in practice, and it is the fastest diagnostic anyone can run on your structure. Add up everything at the bottom of a branch. If it does not fully account for the parent, your structure leaks. If it accounts for more than the parent, your scope has quietly grown. Evaluators reading a scoping deliverable check exactly this, and the check takes them very little time.
The scheduling half tests something related but different: whether you can tell a genuine dependency from a preference. Work that physically cannot start until other work finishes is a dependency. Work you would rather do second is a sequencing choice. Submissions that mark every relationship as a hard finish-to-start link produce schedules with no parallelism at all, which reads as a student who built a list and drew arrows down it. The stronger deliverables show at least some concurrent work with a stated reason it can run in parallel.
Reading the rubric as a build order
The scoring detail for E055 lives in your Course of Study, not in the public catalog. Open it and count the aspects before you draw a single box. Each aspect is scored on its own against a three-point scale, a 2 in each one passes the task, and there is no averaging between them. That matters more in a scoping course than in a writing course, because the artifact and the explanation are usually scored separately. A beautiful structure with no written justification and a strong justification of a broken structure fail for opposite reasons.
If your course is assessed by a performance assessment, build in rubric order rather than in logical order. It feels backwards to write the narrative before the diagram is finished, but the narrative is where the aspects live, and the diagram exists to be referenced by it.
The word budget, worked. Suppose the rubric shows six scored aspects and the directions call for roughly 1,600 words of written explanation alongside your structure and schedule artifacts. Reserve 120 words to restate the project and its boundary, leaving about 1,480 across six aspects, or 245 words each. Two of those aspects will be doing heavier lifting than the rest: the one asking you to justify your decomposition logic and the one asking you to justify your dependencies. Move 60 words out of each of the lighter descriptive aspects and add 120 to each of those two.
An aspect answered in 80 words in a scoping course is nearly always a restatement of the artifact rather than a justification of it. Describing what the reader can already see in your diagram earns nothing. Saying why you cut the branch where you did earns the aspect.
A structure that fits a scoping and scheduling deliverable
Scoping work usually arrives as an artifact plus a written companion. Task directions govern the format where they specify one. Where they do not, this arrangement keeps the artifact and the argument aligned.
| Section | What belongs in it | How it tends to be scored |
|---|---|---|
| Scope statement | What is in, what is explicitly out, and the acceptance conditions | The exclusions carry as much weight as the inclusions |
| Decomposition logic | Why you split the project the way you did, level by level | Scored on reasoning; a diagram with no rationale is an unanswered aspect |
| Work breakdown structure | The hierarchy itself, numbered, down to work packages | Checked for completeness against the parent level and for consistent depth |
| Activity definition | The activities under each work package, each with a verb and a deliverable | Scored for being executable; nouns alone are not activities |
| Dependencies | Which activities constrain which, and the relationship type for each | Scored for genuine constraint, not preference; parallelism is expected |
| Schedule | Durations, sequence and the longest path through the network | Scored for arithmetic consistency with the dependencies you declared |
| Assumptions | What you had to assume about resources, calendars and availability | Protects several other aspects; omitting it makes estimates look arbitrary |
Number the structure and then use those numbers everywhere else. When the dependency table refers to activity 3.2.1 and the schedule refers to the same identifier, an evaluator can trace your logic without reconstructing it. When each section renames the work, they cannot.
Evidence craft when the deliverable is mostly structure
A scoping deliverable is short on prose and long on claims, which changes what evidence looks like. Most of your assertions are estimates, and estimates need a stated basis rather than a citation.
- Give every duration a basis. Analogy to similar work, a rate applied to a quantity, or an expert judgment assumption. A number with no basis reads as invented, and in a scoping course that costs an aspect.
- State the calendar. Five working days is not one week if the scenario runs a six-day operation, and schedules built on unstated calendars produce arithmetic an evaluator cannot reproduce.
- Label each dependency type explicitly. Finish-to-start is the default assumption in most readers' heads, so any other relationship needs to be named and justified.
- Trace back to the scope statement. Every branch of the structure should be answerable to a line in scope, and anything in scope should appear somewhere in the structure.
- Cite the framework where the rubric asks for one. If your decomposition follows a published approach, it gets an in-text citation and an APA reference.
- Keep exclusions visible. The out-of-scope list is evidence of boundary discipline and is often the cheapest aspect to secure.
The habit that separates strong scoping submissions is arithmetic self-checking. Before submitting, walk the longest path yourself, add the durations by hand, and confirm the total matches what your schedule claims. Evaluators do this. It takes them two minutes and it catches the most common single fault in the course.
What separates Competent from a returned scoping task
Work here is Competent or Not Competent, with no letter grades and no ordinary grade point average behind it. Performance assessment work can be revised and resubmitted with no grade penalty, so the real cost of a return is calendar time in a six-month flat-rate term.
Scoping tasks that clear on the first read usually share these traits:
- Each branch of the structure fully accounts for its parent, with nothing added and nothing lost between levels.
- Work packages sit at a consistent depth rather than some branches running four levels while others stop at two.
- Activities are written as verb plus object, so a reader can tell who would do what.
- At least some activities run concurrently, with a sentence explaining why they can.
- The schedule arithmetic reproduces exactly from the durations and dependencies as stated.
- Identifiers are consistent across the structure, the dependency table and the schedule.
Where an objective assessment appears in your plan for this course, the line is absolute. Proctored exams are yours to sit alone. We drill the terminology, work practice network diagrams with you and give a straight readiness verdict. We do not sit assessments and we never ask for portal credentials.
Six mistakes that send E055 tasks back
- Building a task list and calling it a work breakdown structure. A list has no hierarchy and cannot be checked against a parent. The hierarchy is the point.
- Decomposing by department. Structures organized around who does the work rather than what gets produced tend to leave gaps at the seams between teams.
- Making every relationship finish-to-start. A schedule with zero parallelism is almost never a real schedule, and evaluators read it as a student who did not analyze the work.
- Estimating durations without a stated basis. Round numbers with no reasoning behind them undermine every downstream calculation.
- Letting the artifact and the narrative drift apart. If the diagram shows six work packages and the text discusses five, the reader stops trusting both.
- Skipping the exclusions. Out-of-scope statements are quick to write, easy to score and routinely left out.
How support works on this course
E055 is the most checkable course in the sequence, which makes it the one where a review pass pays for itself fastest. Send the rubric from your Course of Study, the task directions and whatever scenario the task supplies, and the work comes back with the decomposition tested against its parents, the dependency logic argued rather than asserted, and the schedule arithmetic verified by hand.
What you keep afterwards is the checking routine itself, because E056 through E062 all inherit the structure you build here. A clean breakdown in E055 makes the budgeting course substantially shorter.
Questions students ask about E055
Is E055 the same course as PJMG 2105?
How detailed does the work breakdown structure need to be?
Do I need scheduling software for E055?
Stuck on a work breakdown structure?
Send the rubric, the task directions and your draft structure. You get decomposition checked against every parent level, dependency logic argued in writing, and the schedule arithmetic verified.
Where E055 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.