D365Forge

Templates › Delivery plan and milestones

Delivery plan and milestones

Format
Excel (xlsx)
Owning skill
programme-management:delivery-plan
Tailored from
organisation, goals, modules, estate, constraints, edition, modules_in_scope, roles, generated_on
Status
draft

How to use this template

The project manager ({{roles.project-manager}}) builds this plan in Initiate with the partner ({{constraints.partner}}) and the solution architect, working back from the target go-live of {{goals.target_go_live}}. Baseline it when the solution blueprint is approved and report progress against that baseline at every steering meeting. Re-baseline only through change control, and keep the earlier baseline in the file so slippage stays visible.

The plan is organised by Success by Design stage. Workstreams are listed per module in scope ({{modules_in_scope}}) plus the cross-cutting streams every Dynamics 365 project needs.

Guidance: Plan backwards from go-live as well as forwards from mobilisation. Fix the dates that are outside your control first (release waves, organisation change freezes, ERP releases, peak trading), then place UAT, training and cutover so none of them collides with those dates.

SMB: Use one combined workstream for the apps in scope, two-week sprints and a short Prepare stage. Keep the stage gates; a small project still needs a documented go/no-go.

Enterprise only: Give each module its own workstream lead and sprint backlog, add an integrated plan for SIT and UAT across modules, and decide early whether go-live is phased by module, region or business unit.

Sheet: Read me

ItemDetail
Organisation{{organisation.name}}
Edition{{edition}}
Modules in scope{{modules_in_scope}}
Target go-live{{goals.target_go_live}}
Known change freezes{{constraints.change_freezes}}
Generated on{{generated_on}}
Status valuesNot started, On track, At risk, Late, Complete

Sheet: Phases

StagePhaseObjectiveExit criteria (stage gate)StartEndOwnerStatus
StrategizeVision and business caseAgree outcomes, scope, budget and partnerCharter drafted, statement of work signed{{roles.executive-sponsor}}
InitiateMobiliseTeam, governance and environments in placeRACI agreed, sandboxes provisioned, backlog tool ready{{roles.project-manager}}
InitiateFit-to-standard and designTest processes against standard apps, close gaps by designSolution blueprint approved by design authority{{roles.solution-architect}}
ImplementBuild sprintsConfigure, extend and integrate in short iterationsAll MVP backlog items accepted at sprint review{{roles.project-manager}}
ImplementSystem integration testingProve end-to-end processes across modules and integrationsSIT exit criteria met, final mock migration passed{{roles.test-manager}}
PrepareUAT, performance and trainingBusiness proves the solution and users are readyUAT signed off, training delivered, performance accepted{{roles.process-owner}}
PrepareCutover readinessRehearse cutover and decide go/no-goRehearsal completed in agreed window, go decision recorded{{roles.project-manager}}
OperateGo-live and hypercareStabilise and hand over to supportHypercare exit criteria met{{goals.target_go_live}} plus hypercare{{roles.support-lead}}

Sheet: Workstreams

WorkstreamModuleLeadKey deliverablesDepends onPeak stageInclude?
SalesSales ({{modules.sales.users}} users){{roles.sales-consultant}}Lead to opportunity, products and price lists, quotes, forecastingProduct and customer data from {{estate.erp}}Implement{{modules.sales.in_scope}}
MarketingCustomer Insights - Journeys{{roles.journeys-consultant}}Journeys, segments, consent and preference centre, sending domain set-upDNS changes, consent history from current systemsImplement{{modules.marketing.in_scope}}
Customer ServiceCustomer Service ({{modules.customer_service.users}} users){{roles.customer-service-consultant}}Case lifecycle, queues and unified routing, SLAs, knowledge, channels{{estate.telephony}}Implement{{modules.customer_service.in_scope}}
Field ServiceField Service ({{modules.field_service.technicians}} technicians){{roles.field-service-consultant}}Work orders, incident types, schedule board, Field Service Mobile, inventoryInventory and invoicing in {{estate.erp}}Implement{{modules.field_service.in_scope}}
Integration and dataAll{{roles.integration-lead}}Integrations, migration mapping, mock migrations, reconciliationSource system ownersImplement to PrepareYes
Platform and ALMAll{{roles.platform-administrator}}Environments, pipelines, security roles, monitoringTenant and identity teamsInitiate onwardsYes
TestingAll{{roles.test-manager}}Test strategy, SIT, UAT, regression packStable test environmentsImplement to PrepareYes
Change and trainingAll{{roles.change-lead}}Stakeholder plan, communications, role-based training, super usersProcess sign-offPrepareYes

Guidance: Delete workstream rows for modules marked out of scope.

Sheet: Milestones

IDMilestoneStageBaseline dateForecast dateOwnerEvidence of completionStatus
M01Charter and business case approvedInitiate{{roles.executive-sponsor}}Signed approval page
M02Solution blueprint approvedInitiate{{roles.design-authority-lead}}Design authority minutes, no open blocking findings
M03Build completeImplement{{roles.solution-architect}}Final sprint review accepted
M04SIT exitImplement{{roles.test-manager}}SIT exit report
M05UAT signed offPrepare{{roles.process-owner}}UAT sign-off form per process
M06Go/no-go decisionPrepare{{roles.executive-sponsor}}Signed go/no-go record
M07Go-liveOperate{{goals.target_go_live}}{{roles.project-manager}}Production smoke test passed
M08Hypercare exitOperate{{roles.support-lead}}Exit criteria met, handover signed

Sheet: Sprint plan

SprintStartEndSprint goalWorkstreamsReview dateStatus
1Core data model, accounts and contacts, base security rolesPlatform, all modules
2Lead to opportunity and first integration stubSales, Integration
3Case creation, queues and routing rulesCustomer Service

Sheet: Release waves and freezes

ItemWhy it mattersDateWhere to checkActionOwner
Release plans for the next wave publishedShows new and changed features for in-scope modulesCheck current release plansMicrosoft Learn release planning pagesReview features and deprecations for in-scope modules{{roles.solution-architect}}
Early access window for the next waveAllows regression testing in a sandbox before updates are appliedCheck current datesPower Platform admin center and Microsoft LearnEnable on a sandbox copy and run the regression pack{{roles.platform-administrator}}
Wave updates applied to productionPlatform changes arrive in productionCheck current datesMicrosoft 365 admin center Message centerAvoid go-live and cutover in the same window{{roles.platform-administrator}}
Deprecation announcementsFeatures in the design may be withdrawnCheck before blueprint approvalMicrosoft Learn deprecation noticesLog affected items in the RAID log{{roles.solution-architect}}
Organisation change freezes{{constraints.change_freezes}}Internal calendarKeep cutover and training outside freeze periods{{roles.project-manager}}
ERP and telephony vendor releasesInterfaces may change{{estate.erp}} and {{estate.telephony}} ownersAgree interface freeze from SIT to hypercare exit{{roles.integration-lead}}

Guidance: Never type release dates from memory. Check the current Microsoft Learn release planning pages and the Power Platform admin center each time the plan is re-baselined.

Credit: Template from D365Forge by Simon Foote and Robert Peledie (https://github.com/SimonFoote-greensparx/D365Forge), licensed under CC BY 4.0. Keep this credit when you share or adapt the template; in your own completed document you may keep it as a footer or remove it.