Work Intake & Release — Process Demo

Four parallel processes: Intake → Scheduling → Build, with SOW running alongside.

Speed
1

Work Intake

Form → IT Review → Vendor Estimate → Route
Business Submits RequestForm
IT Review (Completeness)Vetting
Vendor EstimateSizing
Routing Decision>20h → SOW/Project · ≤20h → Support
Ready to ScheduleParked
Requests stay parked here until the next Release Planning meeting picks them up, subject to capacity.
2

Release Schedule

Monthly plan built from parked requests, bounded by capacity
Monthly Capacity 0 / hrs
Release # 1 Planning
Next release capacity
Planning MeetingIT reviews parked items
Scheduled for ReleaseLocked
Once locked, scope cannot change except for true emergencies. Release freezes the hours against capacity.
3

Build Process (Support)

Scheduled items · Tech reqs → Dev → UAT → Deploy
Technical RequirementsAuthoring
Tech Req ReviewPeer review
DevelopmentImplementation
UAT (Formal Signoff)Business signs
DeployedLive
4

SOW Process

Runs in parallel — releases align with monthly cycle
Draft Formal EstimateVendor
SOW ReviewIT / Legal
SOW SignoffBusiness signs
SOW Complete → Ready to ScheduleParked
Only requests estimated at >20 hours enter this lane. Once signed, project work starts immediately in lane 5 — it does not wait in the monthly queue.
5

Project Build

Runs in parallel · Deploy aligns with monthly release
Technical RequirementsAuthoring
Tech Req ReviewPeer review
DevelopmentImplementation
UAT (Formal Signoff)Business signs
Awaiting Release WindowReady, parked for deploy
DeployedLive
Projects do not compete for the 50-hour monthly support capacity. They build in parallel, then wait for the next Lock & Release to ride along with the monthly deployment.