As a trainer I am often asked what the difference is or the similarities between Agile (PM) and PRINCE2®. Lay people say a lot about it in the corridors, but what about exactly? Let me begin by saying that both have their value in that they are used by many organizations and individuals and are bearing fruit. When used properly, they increase the chance (!) Of a successful project: - Less costs - Better quality - Reduced throughput time - Less risks - More benefits - More clarity (scope) PRINCE2® Tried and tested for years, a reasonably complete project management method (or best practice), which encompasses almost all aspects of project management and provides checklists throughout the life cycle of the project of processes / activities that should be performed in order to lead and deliver a successful project, taking into account indisputable principles and using adaptable themes such as a Business Case for the project, design of the project organization (with clear roles), defining Quality, Risk, etc. In a Project Brief (mainly with a High Level Business Case), the project answers the question: Do we have to start the project ??? In the (following) Initiation Phase, the Project Initiation Documentation (or ?? PID ?? with ao a project plan, a detailed Business Case, ??) answer to the question: what does the project and the output of the project look like? In the Phase plans, a (sub) plan is presented at a detailed level shortly before the next phase. made by the most updated state of affairs so that it is iterative and ?? to the point ?? remains, with the PID revised where necessary. Info about PRINCE2 Agile (PM) Agile PM wants a more pragmatic approach than the traditional approach and is opposed to the Waterfall method, which is too static. Through an iterative way of working and always in collaboration with the customer, Agile always ensures minimal deviations from the wishes of the customer. Agile chooses to allow the functionality desired by the customer to fluctuate for the benefit of costs and (lead) time, whereby the latter 2 must be fixed and functionality based on the MoSCoW (Must -, Should -, Could -, Won? ? t have) principle to fluctuate in order to stay within time and costs. Info about Agile Differences A difference between the two techniques is of course in terminology, where I tell customers and students that a lot is in the ?? language ?? which one prefers to speak. For example, Dutch is not necessarily better ?? than French, but more convenient ?? if you eg want to ask for directions in the Netherlands, but more awkward if you ask for directions in Paris. Another difference is how the various activities are grouped: for example, PRINCE2 knows the ?? Pre Project ?? looking at the desirability of continuing, which in Agile is again cut into 2 pieces ??: ?? Pre-project ?? and ?? Feasability ?? (..). Also in the amount of roles Agile has more (split) roles than PRINCE2 which groups these roles more together, etc. Another perhaps important difference is the different choices that are made: eg where PRINCE2 works with tolerances with regard to all aspects (time, money, quality of the (end) products, ??.) that must be properly agreed, Agile states in advance that costs and lead time may not be tinkered with and that functionality is the MoSCoW principle (see above) must vary, assuming that not all features ?? are equally important. PRINCE2® also uses MoSCoW, but states that any choice on any of the aspects is a joint decision by both the project supplier and the client / business (or customer). Last but not least, Agile believes there is an essential difference between building software and all other projects. Similarities It is clear to me that the similarities are much greater than the differences and there is no other way and I mean this in an almost "physical way". OF COURSE you have to think carefully about what you are going to do before you start, then continue to fine-tune (with the customer and key stakeholders) whether what you are doing is still intended and worthwhile, evaluate afterwards etc: this basic philosophy also has every decent method. / best practice / ??. on earth! The iterative character is also a vision that has grown stronger over the years and is reflected in Agile, PRINCE2® and any other modern technology. Obviously, it is much more convenient for the supplier of products to have static specifications (specs) (Waterfall method), because the supplier can then work comfortably and unhindered without always taking changed specs into account, but THE WORLD IS UNFORTUNATELY NOT STILL WHEN YOU DO YOUR PROJECT! All PM methods have removed most of the static elements from each technique and replaced them with dynamic / iterative components. Both techniques are NOT NORM, which means that you can / must adjust them so that they work best for your organization and you get the best results from them. Combining Agile / PRINCE2 It is argued by colleagues in the business that ?? partial use ?? The solution of both techniques would be: I am very much against this for several reasons. 1) You ask an organization to know 2 methods where it is already very difficult to know 1 method well. 2) You introduce different terminology, which greatly increases the confusion both internally and externally. You get islands within your organization, each with their own jargon / interpretation of the different methods, while it is difficult enough to make good agreements with 1 method. External parties: suppliers, new employees, ?? will find it extra difficult to integrate. The strength of 1 (!) Method is precisely that everything must be clear to everyone and you prevent discussions about ?? what do you mean ??. ?? 3) You actually develop a new method, while dedicated specialists worldwide sometimes spend decades trying to get a method (or technique) so complete / consistent / (almost) flawless. We're going to mix that up for a while? must there be a good answer to that? Apart from the fact that these ?? colleagues ?? often having too little knowledge / skills for this, this would take years. The result for organizations is therefore often disastrous. PLEASE NOTE: a PRINCE2 Agile method has been developed that could be very interesting for those who would like to do the above. There, too, it must be realized that this is neither PRINCE2® nor Agile PM and so in fact a choice for a new method with the same advantages and the same risks above. Conclusion My conclusion is that there is no ?? best technique / method ?? is. PRINCE2® is by far the most widely used method and this should definitely be a consideration. As the Dutch language is by far the most used language in the Netherlands, this should certainly be a very important argument for using Dutch as the working language in your organization. The same applies to PRINCE2, although Agile is gaining more and more popularity, the proportions are still very strong in favor of PRINCE2®. In addition, organizations must of course look at the situation they find themselves in and ask themselves and stakeholders questions such as: - What technology do we currently use (possibly partly) and how does it work for us and our environment? - In which areas do we have difficulties and does our way of working not give the expected results? - What expectations do our (most important) stakeholders (or stakeholders) have and what technology do they work with? Finally Choosing a well-suited Project Management method is essential for large and small organizations that are going through more and more changes and want to make these changes in an effective (achieving the objectives) and efficient way (without using too much time / costs / resources). implement. In addition to choosing a method, training / certification and guidance of employees is also crucial. You can contact D-ICT Solutions for certified training courses or a free consultation.