Project route
Describe the project and get the route from presale to closure: core practices with the reason, what to avoid and what each gate will check. An agent gets the same answer from plan_project.
Events
Core practices
- Estimationneeded for G1: Estimate (range)
Also useful (24)
- recommendedStage gating
- recommendedStakeholder engagement
- recommendedBudget control
- recommendedRisk management
- recommendedBenefits management
- recommendedUncertainty assessment (Cynefin)
- recommendedBusiness Model Canvas
- recommendedFinancial analysis
- recommendedSWOT analysis
- recommendedAnalogous estimation
- recommendedParametric estimation
- recommendedThree-point estimation (PERT)
- recommendedReference class forecasting
- recommendedStakeholder map (power / interest)
- recommendedInterviews
- recommendedFacilitated workshops
- recommendedDocument analysis
- recommendedMoSCoW
- recommendedRisk analysis (probability × impact)
- recommendedPre-mortem
- recommendedAssumptions management
- recommendedContext diagram
- borrowableJobs-to-be-Done interviews
- borrowableAI-generated prototype
Gate evidence
G0 · Bid / no-bid
Should we pursue this opportunity at all?
- criticalOpportunity brief
- criticalInitial requirements
- optionalStakeholder register
G1 · Commit
Can we commit to scope, price and approach?
- criticalSolution outline
- criticalEstimate (range)
- requiredAssumptions and exclusions log · waivable
- criticalProposal
- criticalContract / statement of work
- optionalSuccess metrics with baselines
- optionalRisk register (RAID)
02
Initiation and kickoff
Authorize the project and align team and client on goals, roles, cadence and ways of working.
Events
- coreInternal kickoff
- coreClient kickoff
Core practices
- Risk managementneeded for G2: Risk register (RAID)
- Project initiationneeded for G2: Project charter, Project management plan
Also useful (13)
- recommendedStage gating
- recommendedDecision logging
- recommendedStakeholder engagement
- recommendedCommunication planning
- recommendedProduct Backlog management
- recommendedDefinition of Done
- recommendedVisual management
- recommendedService level management
- recommendedUncertainty assessment (Cynefin)
- recommendedAssigning responsibilities (RACI)
- recommendedStakeholder map (power / interest)
- recommendedPre-mortem
- recommendedAssumptions management
Gate evidence
G2 · Launch
Is everyone ready to start work?
- criticalProject charter
- requiredStakeholder register · waivable
- requiredRACI chart · waivable
- requiredCommunication plan · waivable
- criticalRisk register (RAID)
- optionalWorking agreements
- criticalProject management plan
- requiredProduct Backlog · waivable
- requiredDefinition of Done (agreed text) · waivable
Events
Core practices
- Scope baseliningneeded for G3: Scope statement
- Facilitated workshopsneeded for G3: Confirmed elicitation results
Also useful (33)
- recommendedStage gating
- recommendedStakeholder engagement
- recommendedRequirements life cycle management
- recommendedPrototyping and early visualisation
- recommendedBusiness Model Canvas
- recommendedSWOT analysis
- recommendedWork breakdown
- recommendedStakeholder map (power / interest)
- recommendedInterviews
- recommendedDocument analysis
- recommendedSurvey or questionnaire
- recommendedFocus groups
- recommendedEvent storming
- recommendedBrainstorming
- recommendedData flow modelling
- recommendedScope modelling
- recommendedBuilding a glossary
- recommendedUser story mapping
- recommendedClickable prototype
- recommended5 Whys
- recommendedFishbone diagram
- recommendedBPMN 2.0
- recommendedFlowchart
- recommendedSwimlane diagram
- recommendedData flow diagram (DFD)
- recommendedContext diagram
- borrowableJobs-to-be-Done interviews
- borrowablePaper or whiteboard sketching
- borrowableAI-generated prototype
- borrowableCurrent reality tree
- borrowableSIPOC
- borrowableValue stream map
- borrowableCustomer journey map
Gate evidence
G3 · Scope baseline
Do we understand the needs well enough to specify them?
- criticalConfirmed elicitation results
- criticalScope statement
- optionalGlossary
Events
Core practices
- Product Backlog managementneeded for G4: Product Backlog
- Prototyping and early visualisationneeded for G4: Mockups / wireframes
- Non-functional requirements analysisneeded for G4: Non-functional requirements
Also useful (40)
- recommendedStage gating
- recommendedDecision logging
- recommendedRequirements life cycle management
- recommendedScope baselining
- recommendedChange control
- recommendedDefinition of Ready
- recommendedFacilitated workshops
- recommendedEvent storming
- recommendedData flow modelling
- recommendedData modelling
- recommendedUse cases and scenarios
- recommendedUser stories
- recommendedAcceptance and evaluation criteria
- recommendedSpecification by example (BDD)
- recommendedBusiness rules analysis
- recommendedBuilding a glossary
- recommendedFunctional decomposition
- recommendedState modelling
- recommendedRoles and permissions matrix
- recommendedPrioritisation
- recommendedMoSCoW
- recommendedUser story mapping
- recommendedWireframing
- recommendedClickable prototype
- recommendedReviews and walkthroughs
- recommendedBPMN 2.0
- recommendedFlowchart
- recommendedSwimlane diagram
- recommendedUML activity diagram
- recommendedUML use case diagram
- recommendedUML state machine
- recommendedData flow diagram (DFD)
- recommendedEntity-relationship diagram (ERD)
- recommendedDecision table / DMN
- borrowableWeighted Shortest Job First
- borrowableKano model
- borrowablePaper or whiteboard sketching
- borrowableAI-generated prototype
- borrowableEvaporating cloud
- borrowableUsability testing
Gate evidence
G4 · Requirements ready
Is the next work specified well enough to design and build?
- criticalProduct Backlog · one of
- criticalAcceptance criteria
- criticalMockups / wireframes · one of · waivable
- criticalPrototype · one of
- criticalNon-functional requirements
- optionalUse case specifications
- optionalDefinition of Ready (agreed text)
05
Design and planning
Define architecture, data and integrations; plan delivery, risks, budget and resources.
Events
Core practices
- Delivery plan on a timelineneeded for G5: Delivery plan (timeline)
- Risk managementneeded for G5: Risk register (RAID)
- Quality planning and controlneeded for G5: Test strategy and plan
- Solution architecture and designneeded for G5: Solution design / architecture description
- Work breakdownneeded for G5: Work breakdown structure
- Data modellingneeded for G5: Data model (ERD)
Also useful (49)
- recommendedStage gating
- recommendedManagement by exception
- recommendedStatus reporting from real data
- recommendedDecision logging
- recommendedOrganisational change and adoption
- recommendedChange control
- recommendedPrototyping and early visualisation
- recommendedEstimation
- recommendedSchedule management
- recommendedRolling-wave planning
- recommendedProbabilistic forecasting
- recommendedBudget control
- recommendedTest management
- recommendedTechnical debt management
- recommendedTimeboxing
- recommendedAnalogous estimation
- recommendedParametric estimation
- recommendedThree-point estimation (PERT)
- recommendedReference class forecasting
- recommendedPlanning Poker
- recommendedMonte Carlo simulation
- recommendedCritical path method
- recommendedBrainstorming
- recommendedData flow modelling
- recommendedNon-functional requirements analysis
- recommendedFunctional decomposition
- recommendedState modelling
- recommendedRoles and permissions matrix
- recommendedWireframing
- recommendedClickable prototype
- recommendedRisk analysis (probability × impact)
- recommendedPre-mortem
- recommendedSpike or proof of concept
- recommendedReviews and walkthroughs
- recommendedArchitecture decision records
- recommendedBPMN 2.0
- recommendedSwimlane diagram
- recommendedUML activity diagram
- recommendedUML class diagram
- recommendedUML sequence diagram
- recommendedUML state machine
- recommendedUML component and deployment diagrams
- recommendedData flow diagram (DFD)
- recommendedEntity-relationship diagram (ERD)
- recommendedC4 model
- recommendedGantt chart
- borrowableHigh-fidelity UI design
- borrowableTechnical debt quadrant
- borrowableUsability testing
Gate evidence
G5 · Design and plan approved
Can the team build without guessing, and do we know when it will arrive?
- criticalSolution design / architecture description
- criticalData model (ERD) · waivable
- optionalArchitecture decision records (ADR)
- criticalWork breakdown structure
- criticalDelivery plan (timeline)
- requiredRelease plan · one of · waivable
- requiredProbabilistic forecast · one of · waivable
- criticalTest strategy and plan
- requiredRole and access matrix · waivable
- criticalRisk register (RAID)
Events
Core practices
- Test managementneeded for G6: Test cases
- Solution build and configurationneeded for G6: Increment
- Test automation and TDDcontext rule
- Continuous integrationcontext rule
Also useful (55)
- recommendedStage gating
- recommendedManagement by exception
- recommendedStatus reporting from real data
- recommendedDecision logging
- recommendedStakeholder engagement
- recommendedRequirements life cycle management
- recommendedProduct Backlog management
- recommendedChange control
- recommendedDefinition of Ready
- recommendedEstimation
- recommendedSchedule management
- recommendedRolling-wave planning
- recommendedDelivery plan on a timeline
- recommendedProbabilistic forecasting
- recommendedBudget control
- recommendedRisk management
- recommendedIssue and impediment management
- recommendedQuality planning and control
- recommendedDefinition of Done
- recommendedCode review
- recommendedTechnical debt management
- recommendedVisual management
- recommendedWIP limits
- recommendedFlow metrics
- recommendedTimeboxing
- recommendedContinuous improvement
- recommendedRelease and deployment management
- recommendedContinuous delivery
- recommendedIncident management
- recommendedService level management
- recommendedLessons management
- recommendedPlanning Poker
- recommendedMonte Carlo simulation
- recommendedUser stories
- recommendedAcceptance and evaluation criteria
- recommendedSpecification by example (BDD)
- recommendedPrioritisation
- recommendedRisk analysis (probability × impact)
- recommended5 Whys
- recommendedFishbone diagram
- recommendedBlameless post-incident review
- recommendedA/B testing
- recommendedSpike or proof of concept
- recommendedReviews and walkthroughs
- recommendedArchitecture decision records
- recommendedKanban board
- recommendedCumulative flow diagram
- recommendedGantt chart
- recommendedBurn-up chart
- borrowableSustainable pace
- borrowableWeighted Shortest Job First
- borrowableCurrent reality tree
- borrowableEvaporating cloud
- borrowableTechnical debt quadrant
- borrowableValue stream map
Gate evidence
G6 · Test readiness
Is the solution complete enough to verify end to end?
- criticalIncrement
- criticalTest cases · one of
- criticalAutomated test suite · one of
- optionalDefect log
- requiredTechnical debt register / known restrictions · waivable
- optionalRelease notes
- optionalUser and admin documentation
Core practices
- Test managementneeded for G7: UAT scripts, Defect log
Also useful (6)
- recommendedStage gating
- recommendedStatus reporting from real data
- recommendedChange control
- recommendedIssue and impediment management
- recommendedQuality planning and control
- borrowableUsability testing
Gate evidence
G7 · Acceptance
Does the solution do what the business needs?
- criticalUAT scripts · one of
- criticalAcceptance criteria · one of
- criticalUAT sign-off record
- criticalDefect log
- requiredTraining materials · waivable
Events
Core practices
- Release and deployment managementneeded for G8: Cutover plan / runbook, Rollback plan
- Knowledge transferneeded for G8: Support model and SLA
Also useful (6)
- recommendedStage gating
- recommendedStakeholder engagement
- recommendedOrganisational change and adoption
- recommendedRisk management
- recommendedContinuous delivery
- recommendedService level management
Gate evidence
G8 · Go / no-go
Is it safe to switch to the new solution now?
- criticalCutover plan / runbook
- criticalRollback plan
- requiredTraining materials · waivable
- criticalSupport model and SLA
- requiredRelease notes · waivable
- requiredCommunication plan · waivable
Core practices
- Knowledge transferneeded for G9: Handover package, Support model and SLA
Also useful (11)
- recommendedStage gating
- recommendedOrganisational change and adoption
- recommendedIssue and impediment management
- recommendedTechnical debt management
- recommendedFlow metrics
- recommendedContinuous improvement
- recommendedHypercare / early life support
- recommendedIncident management
- recommendedService level management
- recommended5 Whys
- recommendedBlameless post-incident review
Gate evidence
G9 · Handover
Is the solution stable enough for operations to own it?
- criticalHandover package
- criticalSupport model and SLA
- requiredUser and admin documentation · waivable
- optionalTechnical debt register / known restrictions
- requiredIncident log
Events
Core practices
Nothing core here for this context.
Also useful (8)
- recommendedStage gating
- recommendedBudget control
- recommendedContinuous improvement
- recommendedKnowledge transfer
- recommendedBenefits management
- recommendedLessons management
- recommendedFinancial analysis
- recommendedA/B testing
Gate evidence
G10 · Closure
Is everything closed and was the value delivered?
- criticalClosure report
- requiredLessons learned register · waivable
- optionalBenefits realisation report