Backlog Prioritization Skill Guidance

Use When

ranking an approved backlog with MoSCoW and WSJF and assigning release or sprint order; use story-mapping when the user journey and walking skeleton are not yet visible.
Use this procedure when the required source artefacts are available and Prioritised backlog and release allocation is the next lifecycle deliverable.

Use story-mapping when that neighbouring route owns the decision or deliverable.
Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.

Artefact	Source or provider	Required?	Behaviour when missing
Approved backlog, dependencies, capacity, cost of delay, and release goal	Product owner, delivery team, and business context	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.