SteadyMast

A name with possibilities.

A larger remaining list does not erase completed work

Begin with a fictional baseline containing six distinct tasks: A, B, C, D, E and F. Tasks A, B and C are completed; D, E and F are unfinished. A later scope decision removes unfinished task F and adds new tasks G and H, both unfinished. Assume each identifier represents one task throughout this example. Count tasks equally for this worksheet, without claiming that they require equal effort. Preserve the original baseline and create a separate current-scope list.

SteadyMast.com
Rebuild the current task set in the SteadyMast scope-change worksheetBaseline: A · B · C · D · E · FRemove unfinished FAdd unfinished G and HCurrent: A · B · C · D · E · G · H6 baseline − 1 removal + 2 additions = 7

01

Rebuild the current list from the recorded changes

Start with the six baseline identifiers. Remove F, then add G and H. The current scope is A, B, C, D, E, G and H, containing seven tasks. The count also follows from six minus one plus two, which equals seven. Keep F in the change record with its removed status; do not mark it completed merely because it no longer appears in the current list. The change record explains why the current scope differs from the baseline and prevents a missing identifier from being mistaken for an accidental omission.

Separate completion from removal in the SteadyMast scope-change worksheetCompleted remains A · B · CCurrent unfinished: D · E · G · H3 completed + 4 unfinished = 7 currentF is removed, not completedThe scope changed; completed work remains

02

Reconcile completion against the current scope

The completed set remains A, B and C because the scope change did not alter their status. The current unfinished set is D, E, G and H, containing four tasks. Three completed plus four unfinished equals the seven-task current scope. Before the revision there were three unfinished tasks; afterward there are four. That increase does not undo the three completions. It reflects one unfinished removal and two unfinished additions. A single remaining-count chart would not explain the difference unless it also showed the scope decisions that changed the underlying list.

Preserve a scope handoff in the SteadyMast scope-change worksheetKeep a scope-change handoffPreserve baseline and current versionsRecord additions, removals, dates and reasonsNext work: D · E · G · HTask counts are not effort estimates

03

Save a handoff with both versions and the reason

A reusable scope sheet records the baseline version, baseline identifiers, completed identifiers, additions, removals, current scope and current unfinished set. Add a reason and decision date for each change. For this example, the next work is D, E, G and H, while F remains recorded as removed. If a later revision changes a completed task substantially, decide explicitly how to represent the new work rather than silently preserving its completed status. The worksheet counts items, not effort or value, so any workload estimate belongs in a separate field with its own assumptions.

steadymast.com

Explore SteadyMast

Held for potential development. Acquisition inquiries may be considered.

Domain inquiry ↗