Sprint Work Order
Agreed roles, rhythm, priorities and what is out of scope for this sprint.
Recruitment as a ServiceRecruitment as a Service
Momentum
Pipeline rhythm at scale
Several roles or hiring waves need to move together — Momentum runs them in a capped sprint with lane limits, fixed reviews and accountable status. Not more recruiters dropped in: a controlled cadence where priorities, blockers and decisions are recorded every cycle. For recurring demand when one Hire lane cannot carry the load.
Overview
03
Sprint cadence
Typical focus
Two or more role families or repeated hiring waves
What you receive
Sprint work order, lane plan, status taxonomy, tracker, review notes, blocker log, learning log and acceptance summary
What it is not
Unlimited support or deep one-off search outside the lane plan
Typical timeline
6–12 weeks per sprint cycle
Momentum keeps several approved roles moving in a clear rhythm — with lane limits, regular reviews and visible status.
FitFit
Is this the right starting point?
The right entry depends on what is blocking you — not the label on the proposal.
Works well when
- Two or more role families or repeated hiring waves
- Someone on your side owns priorities and joins reviews
- You have a shared place to track status
- Recurring demand — not a single urgent role
Usually not the right start
What done looks like
You sign off on sprint outputs and the next priorities — or list defects within five business days.
Next stepNext step
See whether Momentum fits your hiring rhythm
Bring your role families, review owner and tracking system — we will tell you honestly if sprint cadence is the right mode.
A short conversation about rhythm and capacity — not open-ended support.
What you receive
Clear sprint outputs — with limits on how many roles run at once.
Done when: You sign off on sprint outputs and the next priorities — or list defects within five business days.
Active Lane Plan
Which roles are active, who owns them and what progress looks like.
Status Taxonomy
One language for progress across teams and tools.
Sprint Tracker
Live view of status, blockers and decisions.
Review Notes
Written decisions from every sprint review.
Blocker Log
Blockers with owners — not a list that sits untouched.
Learning Log
What worked, what did not, and what to prioritise next.
Sprint Acceptance Summary
Sign-off on sprint outputs and whether to continue.
More about each item
1
The contract for one sprint — lane cap, review cadence and exclusions written before work begins.
- Priority order across role families
- Active lane cap and sponsor accountability
- Review cadence and escalation path
Complete when: A sprint starts only when the work order is approved.
2
Every active lane has an owner and target status — nothing runs without agreement.
- Named owner per active lane
- Target status and timeline per lane
- Capacity view against the agreed cap
Complete when: Zero unapproved lanes — every active role is on the plan.
3
Shared definitions so reviews do not argue about what “in progress” means.
- Core status definitions for hiring stages
- Mapping to your system of record
- Rules for when status may change
Complete when: Every core status has a written definition your teams share.
4
Tied to the system you already use — not a parallel shadow tracker.
- Lane status against the taxonomy
- Decision history per review
- Blocker visibility between reviews
Complete when: 100% of active lanes show owner and current status.
5
Every review ends with captured decisions — not verbal agreements that fade.
- Decisions and rationale per review
- Next actions with owners
- Priority shifts documented explicitly
Complete when: Every review creates decision notes within the agreed cadence.
6
When something stalls, it is logged with an owner and escalation path.
- Blocker description and impact
- Named owner on your side or ours
- Escalation when SLA is at risk
Complete when: Every blocker has an owner; missed reviews trigger pause rules.
7
Sprint-level learning — not project history buried in inboxes.
- Patterns across lanes
- Failed assumptions and course corrections
- Input for the next sprint priorities
Complete when: Learning is captured before the next sprint is scoped.
8
A clear end to the sprint — with defects listed or acceptance signed.
- Output summary against the work order
- Open defects and owners
- Recommendation for next sprint or handoff
Complete when: Sprint acceptance signed within five business days.
Operating depthOperating depth
Same product — different ways to work together
Products define what we solve. Delivery defines how deeply Talentpark works inside your system.
How Momentum can show up at each depth:
Sprint design
About advisoryProject
Common startHiring sprint setup
About projectEmbedded
Common startEmbedded Momentum
About embedded
Process
How the sprint rhythm works
Typical rhythm when delivered as a bounded project — advisory is shorter, embedded runs inside your live cadence.
- 01
Fit
We clarify demand, cadence, owners and blockers. One urgent role alone usually points to Hire.
- 02
Setup
We lock active lanes, rhythm, metrics, status taxonomy and exclusions. The sprint does not start before sign-off.
- 03
Planning
Lane plan, status model and capacity against the agreed cap.
- 04
Sprint
Status, blockers, decisions and next actions — every review ends with written notes.
- 05
Sign-off
Outputs, learning and whether to continue the next sprint — or hand off to Hire, Command or Hyron.
BoundariesBoundaries
What is included — and what comes next
Clear expectations from day one — including what we do not take on in this mode.
Not included
Common questions about Momentum
What a sprint includes, what it does not — and how lane limits protect quality.
FAQFAQ
Common questions about Momentum
1
No. Momentum is sprint-based with an active lane cap, review cadence and written acceptance. Unlimited support is not sold.
2
The sprint work order defines the active lane cap. Roles beyond the cap need an explicit capacity decision — not silent scope creep.
3
When only one role is open, the role thesis is unclear, or process ownership blocks reviews. Hire, Signal or Command may fit better.
4
Missed reviews trigger pause rules agreed in the work order. Cadence is part of the product — not optional overhead.
RelatedRelated
Other system entries
Each product targets a different hiring failure layer — compare fit before you choose scope or operating depth.
