PRINCE2 has some weaknesses:
- A number of organisations suffer from PINO (Prince In Name Only), carelessly picking and choosing from the methodology, thereby failing to abide by its key principles. (As with several of the items below, this problem is, of course, not a weakness of the methodology itself but of its practitioners.)
- PRINCE2 is strongly document centric in order to provide good control. However, in some organisations the documents become ends in themselves, and the actual projects themselves falter.
- PRINCE2 provides no explicit treatment of requirements analysis. It is an implementation methodology, which can lead to projects being adopted on false premises, and thereby inevitably failing.
- If not tailored to the needs of the project properly, PRINCE2 can be far too heavy duty an approach for small projects, because it will generate too much work.
- Not very agile
Related posts:
Discussion
Comments are closed.