Concept and mechanism
A migration has a defined outcome and closure even when its engineers also operate the daily service. Operations continue after delivery and need usable products. PRINCE2 7 connects principles, people, practices, processes, and project context. Principles guide method application: continued justification, learning from experience, clear roles and relationships, stage management, exception management, product focus, and tailoring. A principle is not a mandatory form. Useful evidence is how it guides investment, authority, quality, and transition decisions.
Guided application
Consider a migration whose savings depended on a service another initiative will close. The business case needs review before further resources are consumed. Money already spent does not demonstrate future benefit. Also learn from earlier migrations: if workload accounts were missing from handover, include that check in current preparation. For a small project, simplify record format and the frequency of some meetings while retaining proportionate decisions, responsibilities, and control. Tailoring should be understood and documented; removing necessary controls merely to reduce documents leaves a real gap.
A decommissioning project can use a short record of products, criteria, owners, and decisions. It still needs to demonstrate that costs, benefits, and risks justify the action.
Common pitfalls
Treating ongoing support and projects as one commitment; justifying through sunk cost; copying templates without tailoring; dropping a principle in the name of simplicity.
Related topics: People, communication, and adoption · Justification, organization, and sustainability
Structure should support decisions and delivery with clear authority and justification.
Reference: PRINCE2 7 Foundation syllabus · PRINCE2 Project Management Version 7