Iteration 0
Iteration 0 starts with our internal EM>PS Transition meeting and goes through the Planning and Design Sessions with the Customer. Please reference Iteration 0 Fundamentals as we prepare for the following stages.
A reminder to think big in discovery and consider team alignment for production readiness. A well-rounded Iteration 0, helps us (and the Customer team) head into the Initial Planning and Design meetings with our customers confidently.
For Transformational planning throughout iterations, please reference here..
Guidelines for PSDM management
EM>PS Transition
We use the Scheduling Intake issue as a guide for the meeting, as it will help us map the next steps with our Customers. The Scheduling Intake issue is created and attached to the Customer Epic.
The Delivery team can use this template to facilitate the meeting to ensure all points are considered from the Scheduling Intake issue. For larger/Transformation Migrations, please be sure to reference the above.
The output of this meeting is to ensure the Delivery team is prepared, and we have a plan heading into the Customer Kickoff & Discovery & Planning sessions with our customers
Stakeholder Planning Meeting
During this meeting, the PM between the Gitlab & Customer side meet to review the high level scope, and gather any onboarding material that is still missing. This is an opportunity to meet each other and begin to build trust. Additionally, this is an opportunity to review how we plan to manage the project our of Gitlab, along with a quick overview of our methodology. (review suggested cadences, iteration planning & review, preferred updated for status, etc.) We will take this information to our Customer kickoff and review it with the broader project teams.
The PM will take information from this discussion & the EM>PS transition process and continue to build out the following for our Customer Kickoff:
- Project Roadmap (workstream overview, use EM timeline as a reference point)
- Definitions of success
- Review the project within Gitlab (provide collateral as needed) & other tools (Zoom, Slack, etc.)
- Review & agree on Communication plan (iterations, cadence scheduling)
- Project Burndown (google sheets)
- RAID tracking
- Risks for discussion
- Next steps
Customer Kickoff
Before we enter Project Kickoff, the goal is to confidently be on the same understanding of Project expectations as the Customer. This is why we have spent so much effort gathering the initial information from both the account team & the Customer.
- The template for our Kickoff deck can be found here.
- Our SteerCO template can be found here.
- It is recommended to use Gitlab for Iteration status reporting, but if the customer prefers a deck, please reference this template.
output: prepared & scheduled Discovery & Planning sessions, and Iteration Cadences are confirmed by the Customer
ffdab3bc)
