Tech build
Tech workstream. 16 stages, 3 gates. Any stage that is not a gate can be skipped on a campaign.
Edit stages
Reorder the stages, rename them, set the owner role and the SLA in working hours, and mark the gates. A stage key is fixed once the stage is created. The request stage design has to stay on the process, because that is where requests land. A stage taken off here keeps working on every workstream that already carries it, since those stage rows were seeded when the workstream was created. Only new workstreams pick up this list.
#KeyNameOwner roleSLA hoursGateMoveRemove
1
receive_brief
2
technical_scope
3
sow_approval
4
finance_po
5
resource_scheduling
6
technical_kickoff
7
requirements
8
design
9
internal_qa
10
client_uat
11
fixes
12
final_signoff
13
deployment
14
post_launch
15
handover
16
close_out
#StageWhat happensOwnerSLAChecklists
1
Receive brief
- Brief received by Account
- Project Management
- Review objectives, requirements, functionality, platforms, integrations, timings and budget
- Identify technical requirements, dependencies and risks
- Identify any access, data or client information required
2
Scope and technical assessmentWorkbook: Scope & technical assessment
- Tech reviews the requirement
- Define technical approach and solution
- Identify integrations, data requirements, APIs, platforms, hosting, tracking etc.
- Identify technical dependencies and assumptions
- Estimate development
- technical resource required
- Confirm deliverables, testing requirements and timelines
3
SOW and commercial approvalGateWorkbook: SOW / commercial approval
- SOW
- quote prepared
- Confirm technical scope, deliverables, assumptions, dependencies, costs and timings
- Client approval secured
- Any additional requirements subject to change control
4
Finance and POGateWorkbook: Finance / PO
- PO requested
- obtained where required
- Finance confirms commercial approval
- Project financially cleared to proceed
5
Resource scheduling
- Approved scope automatically creates the required project tasks
- Tasks are mapped to the appropriate technical skills
- resource
- Estimated hours are allocated
- Project management system checks existing workload and capacity
- Development
- technical work is automatically scheduled
- Dependencies and deadlines are built into the schedule
- Capacity conflicts are flagged to PM
- Traffic
6
Internal technical kick offWorkbook: Internal technical kick-off
- Bring Tech, Account, Project Management and other relevant teams together
- Confirm requirements, scope, technical approach and responsibilities
- Review dependencies and risks
- Confirm milestones and delivery dates
- Confirm what is required from the client
7
Requirements and specificationWorkbook: Requirements & specification
- Finalise functional
- technical requirements
- Create technical specification where required
- Confirm user journeys, data flows, integrations and acceptance criteria
- Obtain required client access, credentials, assets and information
- Confirm requirements are sufficiently defined before development starts
8
Design and solution developmentRequests land hereWorkbook: Design / solution development
- Develop technical solution
- Configure platforms
- environments
- Build integrations, functionality, tracking or infrastructure
- Progress tracked through the project management system
- Issues and blockers flagged and assigned
9
Internal QA and testingWorkbook: Internal QA / testing
- Test functionality against agreed requirements
- Test integrations, data, tracking and user journeys
- Check different devices
- browsers
- environments where relevant
- Resolve technical issues
- Complete internal QA before client review
10
Client review and UATWorkbook: Client review / UAT
- Provide client access
- demonstration
- test environment where required
- Client tests against agreed acceptance criteria
- Capture consolidated feedback
- Separate defects from new requirements
- Additional requirements assessed against scope
11
Amendments and fixesWorkbook: Amendments / fixes
- Resolve agreed defects and amendments
- Re-test affected functionality
- Any new requirements outside scope go through change control
- additional SOW as required
12
Final sign offGateWorkbook: Final sign-off
- Client confirms solution meets agreed requirements
- Final technical approval secured
- Confirm all critical defects resolved
- Confirm launch
- deployment approval
13
Launch and deploymentWorkbook: Launch / deployment
- Complete deployment
- release
- Activate integrations, tracking or functionality
- Monitor initial performance
- Confirm live environment is working correctly
14
Post launch monitoringWorkbook: Post-launch monitoring
- Monitor for technical issues
- Check tracking, data and integrations
- Resolve any launch issues
- Confirm system is operating as expected
15
Handover
- Provide documentation
- credentials
- training where required
- Handover to Account
- client
- ongoing support team
- Confirm ownership and support arrangements
- Create any ongoing maintenance tasks
16
Close outWorkbook: Close-out
- Confirm all agreed deliverables completed
- Review actual resource against scope
- Capture additional
- out-of-scope work
- Document technical learnings
- Archive documentation
- Close project
SLA counts working hours, nine to half five Monday to Friday in the account timezone. A gate cannot be skipped, only passed with a note.