Principles | Prince2 7

Look back before you leap. Capture lessons from past projects (good and bad) and apply them continuously, not just at the end. 3. Define Roles and Responsibilities (Who Does What?) The Story: In week two, chaos erupts. A developer, Sarah, changes the database structure without telling anyone. The tester, Mike, is furious because his tests now fail. Sarah says, "I thought I was helping."

The auditor later commends David: "You followed the spirit of PRINCE2, not just the paperwork." prince2 7 principles

However, he keeps the and Product Descriptions formal because those are critical for a high-risk project. Look back before you leap

Maria nods. "Roll this out to all our project managers next quarter." Define Roles and Responsibilities (Who Does What

Maria shows him the data: $500k in lost sales last month due to site crashes. David creates a —a living document showing the project will cost $300k but deliver $2M in benefits over two years.

"How did you avoid all the disasters of our last project?"

"I didn't. We had 17 issues and 8 risks. But the PRINCE2 principles gave us a system. The Business Case kept us honest. Stages gave us checkpoints. Roles stopped blame games. Lessons from the past saved us from repeating mistakes. And we tailored everything so it didn't drown us in bureaucracy."