Editorial review: 9 October 2026
Manage a small project from scope to acceptance
Project-management practice should produce more than a list of methods and software names. Define the outputs, identify the work and dependencies, allocate actual available people, check the results and record who can accept them. A schedule is useful only when its assumptions and completion conditions are visible.
This guide follows an original fictional project to produce two internal reference sheets. It includes a complete baseline schedule, checked outputs and an owner-approved response to a requested addition. It does not describe a real client project or promise cost savings, certification or career advancement.
NASA's technical-planning guidance supports defining technical work, resources and scheduling dependencies in its engineering context. The example below applies those limited planning ideas to a small editorial exercise; it is not a NASA procedure or a universal workplace policy.
Define two deliverables and their acceptance checks
The fictional project owner, Mira, requests two sheets based on a supplied list of workshop materials. The source list is expressly fixed for this exercise:
| Material | Quantity |
|---|---|
| Notebook | 12 |
| Pen | 18 |
| Folder | 6 |
Deliverable one: a quantity sheet showing all three names and quantities in the supplied order, plus the total. Its acceptance check is exact source agreement and a correct sum.
Deliverable two: an alphabetical lookup sheet showing the same name–quantity pairs in alphabetical order. Its acceptance check is that names sort Folder, Notebook, Pen and each quantity remains attached to its original material.
The scope includes these two sheets and their checks. It excludes purchasing, stock verification, distribution and creating new material quantities. The table is an invented source, not an actual inventory. Mira owns acceptance; neither preparing a sheet nor checking arithmetic automatically authorises other activities.
Break the work into tasks with explicit resources
Two people are available continuously from 09:00: Tara and Vikram. Each can perform only one task at a time. Tasks are uninterrupted, and this simplified schedule assumes no breaks, setup delays or transition overhead.
The source is available at 09:00. Tara first spends 10 minutes confirming the three source pairs, and both sheets depend on that confirmation. Tara then prepares the quantity sheet in 20 minutes; Vikram prepares the alphabetical sheet in 15 minutes. After both sheets exist, Vikram needs 10 minutes for the defined checks. Mira is available for a five-minute acceptance review immediately after those checks.
| Task | Owner | Duration | Required predecessor |
|---|---|---|---|
| Confirm source pairs | Tara | 10 minutes | Source available |
| Prepare quantity sheet | Tara | 20 minutes | Source confirmation |
| Prepare alphabetical sheet | Vikram | 15 minutes | Source confirmation |
| Check both sheets | Vikram | 10 minutes | Both sheets prepared |
| Acceptance review | Mira | 5 minutes | Checks complete |
These durations are supplied assumptions, not estimates measured from a real team. If actual availability or work changes, the schedule needs revision rather than a claim that the original finish time remains guaranteed.
Calculate the dependency-aware baseline
Tara confirms the source from 09:00 to 09:10. The two preparation tasks can then run concurrently: Tara works 09:10–09:30, while Vikram works 09:10–09:25.
Vikram cannot start checking at 09:25 because the quantity sheet is not yet ready. He waits until 09:30, then checks both sheets from 09:30 to 09:40. Mira reviews acceptance from 09:40 to 09:45.
The baseline review finishes at 09:45, an elapsed 45 minutes from the assumed start. Summed task effort is 10 + 20 + 15 + 10 + 5 = 60 person-minutes. Those totals differ because two preparation tasks run in parallel.
The longest dependency chain is source confirmation, quantity-sheet preparation, checking and acceptance: 10 + 20 + 10 + 5 = 45 minutes. The alphabetical branch is shorter by five minutes under these particular assumptions. Giving someone a task board does not remove the need to check which predecessor actually controls the next start.
Produce the actual sheets in the exercise
The quantity sheet is:
Notebook — 12
Pen — 18
Folder — 6
Total — 36
The alphabetical lookup sheet is:
Folder — 6
Notebook — 12
Pen — 18
The sum check is 12 + 18 + 6 = 36. The lookup's order is Folder, Notebook, Pen, and its quantities match the original pairs. Sorting only the names while leaving quantities in their old row positions would produce incorrect pairings.
In the supplied completed-task record, Vikram confirms these exact checks at 09:40. Mira then explicitly accepts these two checked sheets at 09:45. This is the actual decision within the fictional example, not a claim that a real project was delivered to a client.
Acceptance covers the named sheets and checks. It does not verify physical stock, approve purchasing or establish that the workshop occurred. Defined completion keeps the project record tied to the requested outputs.
Respond to a requested addition after acceptance
For the next supplied event, Mira asks at 09:45 for a third sheet listing each material's share of the total. Tara can prepare it in 10 minutes, Vikram can check it in 5 minutes, and Mira can review it in 5 minutes. All three are available, in that order, from 09:45.
The addition is new scope. It does not erase the accepted state of the first two sheets or justify claiming that the third is already complete. The proposed schedule is preparation 09:45–09:55, checking 09:55–10:00 and acceptance review 10:00–10:05.
Mira expressly approves this addition and its review ending at 10:05. Approval establishes the agreed next work, not its execution. The original two-sheet project remains accepted at 09:45; the added sheet is an approved extension with checks still to perform in this record.
Work out the proposed third sheet without claiming execution
The fractions for the fixed source are:
| Material | Fraction of total | Percentage |
|---|---|---|
| Notebook | 12/36 = 1/3 | 33⅓% |
| Pen | 18/36 = 1/2 | 50% |
| Folder | 6/36 = 1/6 | 16⅔% |
The fractions sum to 1/3 + 1/2 + 1/6 = 1, so the exact shares sum to 100%. Keeping exact fractions avoids a rounding discrepancy. If a presentation uses decimal rounding, state that convention instead of silently changing the source quantities.
This table is the worked content for the proposed addition. No actual third-sheet completion or later acceptance is supplied. Keep those future states separate from the fact that its expected values can be calculated now.
Report progress using the agreed scope
A useful status note after the change decision is:
The original quantity and alphabetical sheets were checked and accepted at 09:45. Mira approved an added share-of-total sheet, with preparation, checking and acceptance review planned to finish at 10:05. The third sheet has not been recorded as completed or accepted. Physical stock, purchasing and workshop execution remain outside scope.
This report avoids one ambiguous completion percentage. The accepted baseline and approved addition have different states. If another person needs a percentage, first agree what work and acceptance conditions it would measure.
For purpose-specific written updates, see the workplace communication guide. For conflicting requirements and owner decisions, see the stakeholder management guide.
Develop the skill with changed conditions
For an independent planning variation, suppose the source becomes available at 09:10 instead of 09:00, while everyone remains available and all durations stay unchanged. Source confirmation becomes 09:10–09:20; the longer preparation task ends 09:40; checks end 09:50; baseline acceptance ends 09:55.
That result follows from the changed source availability, not from simply adding a universal buffer. In an actual project, check whether people remain available at those revised times and whether the change affects any other dependency.
Record the assumption changed, the affected tasks and the proposed response. No particular software or certificate substitutes for that reasoning. The risk-management guide covers uncertainty and response monitoring as a distinct task.
Frequently asked questions
Why is elapsed time 45 minutes but effort 60 person-minutes? The two preparation tasks run concurrently after source confirmation.
Does a prepared sheet count as accepted? Not in this exercise. The specified checks and Mira's explicit acceptance are required.
Does an approved change mean the new sheet is finished? No. Approval, preparation, checking and acceptance have separate states.
Should every project use this schedule or method? No. These are stated assumptions for a small fictional exercise. Use actual scope, dependencies, availability and authority for the real project.