Project playbook
The parent project wiki home page template for aggregating team information, scope, team rituals, and responsibilities.
Introduction
This project playbook provides a repository and overview of all project related material for CUSTOMER PROJECT. Its structure follows the Customer Obsessed Engineering Delivery Playbook.
This playbook is organized in sections corresponding to the Delivery Playbook chapters, activities and subway map.
Organization
| Resource | Description |
|---|---|
| Index | Comprehensive index of project assets. |
| JIRA | Project work item tracking (includes epics, stories, and acceptance criteria and links directly to test outcomes). Work items are cross linked to Confluence. |
| Confluence | This project wiki. Contains all project documentation. Documents are cross linked to JIRA. |
| GitHub | Source code repository (all project source code and IaC/CI/CD code). |
| Slack | Project comms. Join the #LAUNCH channel and #WaterCooler to get started. |
Statement of work
We are engaging to provide DESCRIPTION OF GOALS AND WORK PRODUCT, working collaboratively on the following joint objectives:
| Goals | Work Product |
|---|---|
| Current state assessment | Assess the current state versus target state, and make recommendations regarding cloud-native architecture. Implement [specific product features], etc. |
| Service Item | Description of service item. |
| Delivery Report | A summary report documenting the application/architecture disposition and key areas of improvement, the project roadmap, resourcing plan and delivery plan. |
Initial scope
| Per discussion during DISCOVERY KICKOFF LINK an initial scope was determined: |
|---|
| Observability dashboard. Real-time telemetry driven by integrated event-based OpenTelemetry will surface business events, DORA metrics and operational status. |
| Itemize key features / specific business capabilities agreed during onboarding here. |
| If “stretch goals” were discussed, go ahead and mention them here being sure to call out each as a “stretch” or identify any potential limitations. |
Engagement roadmap
Product vision, strategy & capabilities
Product Vision
| The product vision and strategy establishes our aspirational targets with the vision, specific achievable strategic initiatives, and actionable outcomes that can be measured. |
|---|
| Write a description of the product vision. It should define the future and inspire the team to work toward that vision and future state. It describes a product on the 3-5 year horizon, and needs to have complete buy-in from all participants. The statement is intended to provide clear direction and inspiration to the team, and encompasses project goals at a very high level. |
| See: Product vision, 1.3. |
Product Strategy
| Question | Response |
|---|---|
| Who are the customers? |
|
| How does the product address their needs? |
|
| What are our business objectives? | Examples:
|
Team organization & rituals
Our combined team is led by the product trio — product manager, product designer and tech lead — plus domain experts, architects, engineers and quality. The team’s composition, working cadence and decision authority each have a dedicated template:
- Team roster — who’s on the team, their responsibilities, and other key stakeholders
- Team activity matrix — team rituals, communication cadence and who attends what
- Decision rights — who decides what (one decision, one owner), plus the supporting RACI matrix
- Exception log — deviations from the team’s own rules, on the record