In the IT world, many agile practitioners believe that PRINCE2 is not flexible enough for the demands of the contemporary workplace. However, for those that have gone through PRINCE2 training, most will be aware how wrong this mentality truly is.
In fact, many terms are inherently agile and can add a level of flexibility to the delivery of any project. To reinforce this claim, here are four terms that are more agile than many believe.
IT project management training starts with PRINCE2 training.
Agile term one – Initiation
When PRINCE2 projects are implemented, they rely on the business case to ensure they are justifiable. There are also the plans that outline what will happen, the budget constraints and the delivery strategies. All of these are identified and decided during the initiation stage.
The business case is the perfect space to articulate an agile perspective and structure the projects requirements and planning to incorporate agile feature sets and product releases. Take for instance the project management and delivery approach, PRINCE2 practitioners can quite easily utilise agile approaches such as Scrum and Kanban.
Additionally, plans could be also be time-boxed rather than flow based, while funding could be based on the releases rather than the traditional technical stages of delivery effort.
By implementing these approaches in the initiation stage, the project can focus on value delivery, decreasing the time-to-market timeframe and allowing end users to utilise valuable components as soon as possible.
Agile term two – Work package
One of the foundational ideas of agile approaches is self-organising teams. For this to be a reality, teams need to be aware of their responsibilities and it must be organised according to understood and communicable boundaries.
PRINCE2’s work package does not preclude these agile fundamentals but can facilitate this form of organisation. For instance, work packages can allow agile practitioners to communicate to stakeholders their roles, responsibilities and authority. This will allow teams to be sure of what they need to do to build and deliver products of value.
Agile term three – Tolerance
PRINCE2 lumps tolerance control under the Project Manager. Tolerance refers to any variation from the agreed estimates set out by the business case in relation to time, cost, risk, benefit and scope. If these tolerances look like they will be breached, it is the responsibility of the project manager to escalate this to the Project Board to attain formal change control and decision-making ability.
Agile methodologies have the same approaches, although under the guise of prioritisation. For instance, many practitioners will use MoSCoW to re-scope their project if it looks like it is heading off course to ensure the project remains within the set time and budget allocated.
Quality follows a similar vein. Take for example the manufacturing of a car. An agile approach would focus on the minimal viable product – being the engine, chassis and other central concerns, while features such as an air conditioning system and sunroofs included only if time and cost will allow.
PRINCE2 can follow suit. It decided on the tasks required and the budget allocated, which is followed by the scope. This allows projects to be changed on the fly depending on any contingencies in the market or in the scope of the project.
For many, PRINCE2 is still one of the most, if not the most, important project management methodologies available. Attending a PRINCE2 training course is a great way to learn about the inherent agility of this method. It is also a great way to expand your job prospects and enhance your ability to deliver cost-effective and customer-centric projects on time and to a high standard,
If you would like to learn more about PRINCE2 or other project management methods, talk to the experts today – contact ALC Training.