Heh, well, yes, of course in the real world we'd both spend our days in front of industrial tribunals if either of us acted in such a peremptory manner. :-)So yes, you've rumbled me; I would no more *really* sack a member of my team than I would *really* cheerfully strangle my client.Here is maybe a more thoughtful rationale:1. The various controls in PRINCE2 each help to mitigate a particular kind of project risk - e.g. Product Description helps to clarify the individual outputs, Project Board helps avoid key decisions being made without appropriate input form each of the user, supplier and project team.2. Most big projects find themselves more or less under-resourced in some area, so they can't do everything they would like. And a fair number of them come up against several systemic problems. 3. However, most big projects aren't going wrong in every aspect of their organisation and delivery at the same time.4. In a project that is experiencing problems and is resource constrained, it would be sensible to prioritise the specific weaknesses that could help get the project back on track. It would probably not be affordable or appropriate to invest in every PRINCE2 control in the book. Also there are huge gaps in PRINCE2 - estimating, resource management, budget and cost control, planning and procurement are just some of the most obvious areas where PRINCE can't help much.5. I would therefore question the wisdom of a team member who thought implementing all of PRINCE2 out of the book was a sufficiently targeted response to a project going wrong or a realistic way of ensuring a project will go right.6. If the project is going well and has every PRINCE2 control in place, that is great. Not something I have ever seen or expect to see, though.Now to go back to the OP's question. In my opinion, more of MSP than of PRINCE2 is usable and value-adding in a real programme.