Pre-mobilization: Internal information gathering & briefing

An internal pre-mobilization template for gathering information, identifying your team, and aligning around engagement objectives.

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.

Team organization & rituals

Our combined team is identified below, starting with the product trio — product manager, product designer and tech lead — plus domain experts, architects, engineers and quality. Regularly scheduled team rituals are also called out.

Team

Role	Person	Responsibility
Product Manager	Name	Owns value and viability: product strategy, roadmap, prioritization and the evidence behind every build decision Provides expert business knowledge; leads discovery with the product designer (e.g., event storming activities)
Product Designer	Name	Owns usability: user research, prototyping and usability testing — continuous discovery, run with the product manager Designs the product’s customer-facing experience
Tech Lead	Name	Owns feasibility: technical direction, engineering standards and the technical health of the product — the team’s accountable technical owner.
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
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

Rituals

Topic	Cadence	Agenda
Increment Planning	Before iteration	Select iteration 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
Demo	TBD	Demo of previous iteration’s deliverable
Retrospective	TBD	Internal team discussion about iteration 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

Discussion & actions

Action / Followup	Topic
Name DATE	External dependencies discovered: Connect with security regarding compliance requirements. Confirm UX designs ready for review.
Name DATE	Discussion topic: Action to follow up on.

Action / Followup

Topic

Name
DATE

External dependencies discovered:

Connect with security regarding compliance requirements.
Confirm UX designs ready for review.

Name
DATE

Discussion topic:

Action to follow up on.