Development & Delivery
We build the solution iteratively through agile sprints, with regular feedback and refinement. Functionality is developed, tested, and released in increments, balancing progress with quality.
Roles
- Phase owner: Project Manager (delivery process), Tech Lead (technical output)
- Supported by: Design Lead, Backlog Steward
- Informed: Sponsor, AM, Projects Coordinator, Support Point of Contact
- Primary Client contact: Project Manager
Typical activities
- Backlog refinement, sprint planning, standups, and sprint demo and reviews
- Configuration management (see here: https://dev.docs.agile.coop/processes/config-management/)
- Agree specific technical processes and documentation (see here:: https://dev.docs.agile.coop/processes)
- Engagement with Support and AM
- Budget adherence review (regular check-in with Finance)
- Development and theming
- Content upload / migration
- Training
- Testing, QA, and accessibility checks (link to testing standards here: https://dev.docs.agile.coop/processes/testing-standards/)
- Deployment and UAT
- Go-live checklist
- Launch planning and go-live
- Documentation and knowledge transfer to client and Support team
Deliverables
| Deliverable | Owner | Shared With | Format | When |
|---|---|---|---|---|
| Sprint and phase reports | PM | Client + Sponsor | Written summary (email or doc) | After each sprint and phase |
| Finished product (live) | Tech Lead + Dev team (PM coordinates) | Client | Deployed environment | At go-live |
| Go-live checklist | PM + Tech Lead | Internal + Client | Checklist doc | Before go-live |
| Documentation / knowledge transfer | Tech Lead + PM | Client + Support team | Doc / training session | Before Transition |
Templates
| Template | Owner | Audience |
|---|---|---|
| Sprint planning, review and retro doc | PM | Internal |
Tools and platforms
- Gitlab / spreadsheet — sprint board and backlog management
- GitHub — version control and code review
- Harvest — time tracking and budget monitoring
- Staging / production environments — testing and deployment
- Project Rocket / Google Meet — standups and team communication
- Google Docs / Project Drive — documentation and knowledge base
Checkpoints
-
The agreed functionality is delivered and tested (including unit, integration and browser testing) ↳ Required output: Client signs off functionality agreed in last version of Statement of Work
-
Client signs off acceptance criteria on all features ↳ Required output: UAT sign-off from client documented
-
Outstanding issues and out-of-scope functionality are logged and prioritised ↳ Required output: Issues list in shared workspace
-
Documentation is delivered ↳ Required output: Client-facing and internal docs complete
-
The client understands what has been delivered and what has not ↳ Required output: Confirmed in writing or close-out meeting notes
Handover
| From | Project Manager and Tech Lead |
| To | Project Manager (continues) + Account Manager (takes over client relationship) |
| Mechanism | Close-out meeting with PM, AM, Tech Lead, and Support team. PM remains responsible for Transition; AM steps in to lead the ongoing client relationship. |
| PM | Own the Transition phase. Ensure documentation is complete, outstanding issues are communicated, and the Support team is briefed. Lead the internal retrospective. |
| Tech Lead | Confirm technical handover is complete. Brief Support on architecture, known issues, and ongoing considerations. |
| AM | Attend close-out. Take ownership of the forward client relationship. Identify next steps and opportunities. |
| Support team | Attend handover briefing. Confirm they have what they need to support the client going forward. |
Last updated: