When looking at project management methodology, PRINCE2 is one of the well-known methods. So well-known that it is preferred by the government, enough for them to really push it as a course with many incentives after completion. How do I know this? Well I remember when I was looking at the GOV site in search of an apprenticeship I came across many Project management apprenticeships, and going through the description 9/10 of them really spoke passionately about PRINCE2. At the time I had no idea what a PRINCE2 was so I just closed the application and looked for something I did.
Now that I do know a little bit about it, I realise that it is a great methodology, what make it good is that it can be tailored to work for many kinds of projects, whether big or small. Techie or non-techie.
Learning about methodology and software development life cycles are key to becoming a master at software development. It is important to know what the ideal approach would be to use during a project. Is it a small relevant simple project that will work with the waterfall approach? or is it a complex huge project that can be better handled with an Agile approach?
PRINCE2 in general just like any software development life cycle starts with an idea/improvement, waits approval, goes through development and produces a product/result. The real difference is the process in-between. When I first looked into PRINCE2 I thought it seemed like a basic waterfall. You have the Project Board, Customers, Suppliers, Project manager… etc. however I realised unlike waterfall it is flexible enough to adapt to change.
There are four main roles which create the foundation of the PRINCE2 methodology, these are:
- Corporate or programme management, these are outside of the project management team, and are responsible for the Project Mandate, naming the Executive, and defining the project-level tolerances.
- The Project Board is responsible for providing the overall direction and are accountable for the success of the project
- The Project Manager is responsible for the day-to-day management of the project within the constraints laid down by the Project Board.
- Team members are responsible for delivering the project products within quality, time and cost
Under each of those roles there are deeper and more complex roles, but that’ll be on another blog post in the future maybe…
PRINCE2 is not perfect. Just like all other SDLC’s, PRINCE2 has its ups and downs.
- Very popular internationally, hence many qualified people trained within the methodology of PRINCE2
- Free to use and also supported by the APM Group ltd.
- Can be used in any kind of organization, doesn’t have to be software or tech related.
- It is often seen as administrative if not understood and applied appropriately.
- it can take time and effort to roll it out across an entire organisation.
- The language can be off putting for those unfamiliar with project management methods.