How can you use project management frameworks?

In my experience, I have had the opportunity to use different frameworks (in some cases I had to combine) to deliver simple and complex projects. What I have found really useful before choosing a framework is to first have a good understanding of the project requirement, assess the organisation culture (this is very important for communication and team dynamics- different organisation have different level of tolerance for change and adaptability) and lastly a good understanding of the range of stakeholders and reporting needed. When combining framework, try PRINCE2Agile. I have found this combination to be effective for both medium and complex project, especially with project that involves difficult stakeholders with vested interests.

In my experience as a project leader, it is not just important to follow the steps or phases of the adopted framework, it is also helpful to ensure the framework guidelines are followed. For example, the PRINCE2 usually have a sequential steps but adhering to underpinning principles and methodology can keep you away from unnecessary stress. As a project leader, keep this at the forefront of every conversation with your team.

I once led a complex software integration project involving two stakeholders. One of the stakeholder companies is quite mature in it use of PRINCE2 framework, while the other stakeholder company has recently adopted Agile (Scrum). The stakeholder who has recently adopted Agile was not initially open to accepting the combination of both methodologies. This particular stakeholder owns 75% stake in the project. I had to put together a presentation to demonstrate to senior management the benefits of using PRINCE2 Agile and why it is the best approach for this specific project. After the presentation, the decision was in favour. Subsequently, I conducted a workshop for teams from both stakeholders to ensure alignment and a unified direction.

In my experience, the change process within the PRINCE2 framework can sometimes be more bureaucratic compared to Agile. Nevertheless, when leading a high-stakes and complex project, PRINCE2 can be valuable due to its ability to ensure proper control, especially when the team working on the project lacks seasoned technical experts. The need for both effective control and quick adaptability to change was one of the reasons for the creation of PRINCE2 Agile. Using PRINCE2 Agile allows the change process to be agile while maintaining proper control. It's essential that the scope document clearly defines the change tolerance if you want to fully benefit from PRINCE2 Agile.

As a project leader, a successful project is not solely determined by achieving the project outcomes, but ensuring these are achieved in a way that leaves stakeholders satisfied with their experience of being part of the project. Feedback is useful for reflection on practices to improve. This is why Agile framework is useful as it encourages review and feedback for every output before a complete handover of the project. Personally, I always try to connect with team members beyond the scope of the project. Building trust is key and it also allows team members to share and comment. I usually allocate time slot in every meeting to focus on leadership and team by focusing on what is working and what can we improve.

In today's customer centric world, we shall not focus on the delivery solely. Are we delivering the best customer experience or not? That's the question which I always have in my head. Having knowledge of all the PM frameworks is essential but the most important part is to use the right framework on the right project. Not just that, how can you modify or update it along the way to suit your customer needs. I personally feel that to provide the best customer experience, be flexible and customise or tailor the framework as per the needs. It might need an extra effort but it's worth it for building the long term partnerships with the customer.