Project playbook

The parent project wiki home page template for aggregating team information, scope, ceremonies, 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 indiex 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 #WaterCoolor 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 meterics 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?	Describe the customer or specific market segment.
How does the product address their needs?	Itemize specific needs that are met by the product. Additional need this product addresses.
What are our business objectives?	Itemize desired business outcomes that are possible because of the product. Examples: Reduce infrastructure cost by at least 35%. Deliver a fully mobile, self-service financial banking platform. Deliver a user interface optimized for visual accessibility needs, including screen reader and ARIA support. Allow customers to completely self-manage their spending, savings, and loan finance accounts (with minimal to no bank intervention required). Provide seamless, very low-barrier (e.g.: “one-click”) integration with merchants to support purchase financing. Build a scalable platform that is highly responsive at all times.

Question

Response

Who are the customers?

Describe the customer or specific market segment.

How does the product address their needs?

Itemize specific needs that are met by the product.
Additional need this product addresses.

What are our business objectives?

Examples:

Reduce infrastructure cost by at least 35%.
Deliver a fully mobile, self-service financial banking platform.
Deliver a user interface optimized for visual accessibility needs, including screen reader and ARIA support.
Allow customers to completely self-manage their spending, savings, and loan finance accounts (with minimal to no bank intervention required).
Provide seamless, very low-barrier (e.g.: “one-click”) integration with merchants to support purchase financing.
Build a scalable platform that is highly responsive at all times.

Team organization & ceremonies

Our combined team, along with key roles, such as product owners, domain experts, architects and engineers are identified below. Regularly scheduled team ceremonies are also called out, along with schedules and topics.

Team

Role	Person	Responsibility
Product Owner	Name	Provides expert business knowledge and decision making authority regarding the product Owns product discovery and roadmap (e.g., Event Storming activities)
Architect	Name	Overall program direction Application architecture / DSO architecture SME
Product Engineer	Name	Architecture and design of the target state solution Implementation of POA and subsequent milestone deliveries
Team Lead	Name	Technical leadership for the team, acts as the team’s architect, chief engineer, and technical expert.
Engineer	Name	Peer reviews on product development, provides specific technical engineering expertise in…
Quality Engineer	Name	Often a rotating role, ensures quality is engineered in at all stages. Guides the team in test engineering.
Dev/OpsSec Engineer	Name	Deep skills in CICD pipeline implementation and “operationalizing code to the cloud.”
Business Analyst	Name	Go-to support across the team for answering all business related questions, and analyzing business unknowns.
Customer / Value Recipient	Name	End-user or customer directly consuming the value (product, feature). Provides insight into the value of the solution, participates in demos.

Other stakeholders

Role	Person	Responsibility
End user	Name	Provides input and participates in usability testing
Role	Name	Description

Ceremonies & communication

Topic	Cadence	Agenda
Sprint Planning	Before @ Sprint	Select Sprint objectives from available stories Review “DoR” and confirm each commitment
Daily Standup	Daily @ 0900 ET	Team standup to raise obstacles and ask for collaboration; provide 90-second progress update
Sprint Demo	Last Day of Sprint @ 1500 ET	Demo of sprint’s deliverable (working software, fully deployed)
Sprint Retrospective	Day After Sprint @ 0900 ET	Internal team discussion about sprint health and continuous improvement
Executive Sync	1st & 3rd Friday @ 0900 ET	Review overall project health and progress Identify and manage any risks and project needs

Team activity matrix

	Role	Strategic Event Storming	Tactical Event Storming	Target State Design	Business Analysis	Sprint Planning	Demos, Retros, Standup
Facilitator		Product Owner	Product Engineer	Product Engineer	Product Owner	Team Lead	Team Lead
Participant	Product Owner	R	R		R	R	R
	Architect	R	R	R			O
	Product Engineer	R	R	R	R	O	R
	Team Lead	R	R	R	R	R	R
	Engineer	R	R	R	O		R
	UX Design	R	R				O
	Data / Business Analyst	R	R	R	R		O
	DSO Engineer	R		R			O
	Quality Engineer	R	R	R		R	R
	Customer	R					R
R = Required Attendance, O = Optional Attendance

RACI matrix

Outputs	Architect	Product Owner	Product Engineer	Team Lead	UX Design	Data / Business Analytics	DSO Engineer	Engineer / Quality Engineer	Customer
Strategic Event Storming	R	A	R	R	R	C	I	R	R
Tactical Event Storming	R	R	R	A	C	C	I	R	I
Target State Design	A	C	C	R	I	I	I	I	I
Business Analysis	I	A	I	R	I	I	I, C	C	C
Sprint Planning	I	A	R	R	I	I	C	I	I
Demos, Retros, Standup	I	A	R	R	I	I	I	R	I
R = Responsible, A = Accountable, C = Consulted, I = Informed Responsible: A team member who is directly responsible for successfully completing a project task. Accountable: The person with final authority over the successful completion of the specific task or deliverable. Consulted: Who must be consulted for their input on tasks or the overall project Informed: Who should be informed of the ongoing status of the project