The baseline is what change is measured against. Without one, scope creep is invisible and unbillable, and the engagement discovers its overrun at billing.
Deliverables are named here, which is what makes the quality stage able to assure something specific rather than assuring in general.
Open, 2 item(s)
State
What
Position or reason
Owner
assumed
This stage's automation position
Planning is judgement, though baseline creation from a template is not. Partly habit: the template exists and is often bypassed.
Engagement Lead
assumed
RUL-37 The budget is split across milestones
Assumed practice. Not enforced, so some engagements carry a single lump budget.
Engagement Lead
Boundary
Trigger (in)
A mobilised team.
Output (out)
A baselined plan with milestones, deliverables and a budget split.
Requires
team-mobilised
Produces
plan-baselined
Floor: can this run itself
Position
person
Manual because
habit
Basis
Planning is judgement, though baseline creation from a template is not. Partly habit: the template exists and is often bypassed.
Confirmed by
Engagement Lead
Behaviour: what runs it
Systems
Planning and baseline, Engagement register
Data
Dataset
Authoritative source
Also in
State
Owner
Engagement plan
Planning and baseline
settled
Engagement Lead
Deliverable
Planning and baseline
S, Y, S, -, D, M, S, -, W, O, R, K
settled
Engagement Lead
Engagement budget
Engagement register
S, Y, S, -, E, R, P, -, G, L
settled
Engagement Lead
Rules: what is decided here
ID
Rule
State
Enforced by
Basis
Owner
RUL-35
Every engagement is baselined before execution
defined
Planning and baseline
Gate in the planning module.
Engagement Lead
RUL-36
Deliverables are named in the baseline
defined
Planning and baseline
What makes quality assurance able to assure something specific.
Quality Lead
RUL-37
The budget is split across milestones
assumed
Planning and baseline
Assumed practice. Not enforced, so some engagements carry a single lump budget.