Go back

APM ChPP - Competencies 3a. Governance and 3b. Reviews

from Project Management Training Podcasts

18m 14s

APM ChPP - Competencies 3a. Governance and 3b. Reviews

The podcast explores the updated governance arrangements and reviews in project management, emphasizing clarity and practicality over bureaucratic jargon. Governance is defined not as managing individual projects, but as overseeing multiple projects through structured frameworks involving decision-making hierarchies, accountability, and reporting. The revised framework includes seven key criteria, forming a logical funnel from broad organizational structures to specific project-level practices, providing flexibility based on complexity and context. Key elements include defining authority levels, establishing clear reporting lines, and using responsibility assignment matrices to document roles. Crucially, governance must be adaptive—tailored to project type, size, and risk, such as applying rigid processes in infrastructure projects versus agile methods in IT ventures. The discussion highlights that successful governance depends on alignment with organizational policies, consistent decision-making mechanisms, and responsiveness to project-specific needs. While some criteria like PB1.7 appear vague, the overall shift reflects a more realistic and practical approach to governance, empowering project managers to demonstrate competence without overcompliance. The framework acknowledges that governance is not static, and its effectiveness is judged by its application, adaptability, and contribution to project success.

Transcription

2101 Words, 12606 Characters

English
[Music] Hello, welcome to another power party training podcast, I'm Paul neighbour and I'm being Matt going to alternate this between us. So calm as to where me Hello, Carmen. Hello. Are you John? Hello. You're still there? Yeah, yeah, I'm Celia. Brilliant. So awake. We've got a really exciting topic of governance arrangements and reviews. These look really hard to me. Yeah. I mean, let's have a look at them. It's a bit buzzword bingo, isn't it? Yeah. These look quite typically. So let's do, so you've got a choice. You can have a governance arrangement or reviews. Yes. Yeah. And you have to do four of these in each one. A minimum of four. A minimum of four. You can do more. Right, so let's just go through them in order. So PP1.1. Can I just step back a bit? I know it's important to the details, but a lot of people get bent out of shape back governance. They don't understand what it is. Yeah. Right. So if you don't understand what it is, good advice do reviews. But if you do want to do governance, make sure you focus on the fact that it's the governance of projects. It's not the governance of a project. Governance of a project is all about integrated planning, which is another competence altogether. Governance is about how you govern one or many projects from an organizational perspective. It's about the framework you use. So this may appeal more to more senior roles, because it's about the levels of accountability. It's about the frameworks and the different layers of reporting you may use. So it's a bit wider competence. It encompasses a lot of things. So is it more likely to apply to a smaller, less complex organization? No, I don't think so. One of the questions is about complexity, but the question you've got to ask yourself is, if you had a project manager and you wanted to get a job done, a project done, would you give them a million quid and say go and get on with it? Or would you want some influence over how they did it and when they told you what they were doing and so on? And that's governance. So sometimes on a smaller organization, they might have to invent that, which is why you got it defined and established. Because in some instances, you might well do that. In other circumstances, you're going to just be following the rules. So a big organization like a big rail company or a big aircraft company, they're all going to have governance arrangements well established. So you're just then following that governance, which is why it made it very difficult for project managers to demonstrate governance because they never did it. Yeah. So you may look at the organizational rules and policies and try to apply those contingent consistency across a number of projects that you may be managing. So everyone uses the same approach, everyone uses the same reporting mechanisms and also there is a clear hierarchies as well because again, different organizations are arranging different ways. So it's a bit of a, yeah. So it's going to be something that appeals to some people and some situations, but not everybody in every organization. As you look down this, think of this, these seven as a funnel at the top. You're talking about multiple projects and as it works its way down, it becomes more specific to a given project. So there is scope actually in there for project managers to do this more than there was in the earlier version, but there's also a recognition that probably they don't all of it, which is why in the old standard, there was only five criteria in here now this seven. So you actually got a broader spread. More choice. More choice. Yeah. Well, I still into the detail and so PP1.1 define reporting decision-making hierarchies and levels of authority for the project. Well, one doesn't sound too bad. What does that one mean, Carmen? So this is about defining delegated authorities. For example, so it's about the functions, it's about processes, procedures. So a project professional, especially someone quite senior, must have a way to establish that consistently. So for example, if you take some of the functions in projects, you may work with people in procurement. So it's about establishing what delegated authorities they have is about how do we escalate things? What is the decision-making process for all these projects within my program or my portfolio? So it's about high level, how do you establish and define that? Why is there an end then? Decision-making hierarchies and levels of authority? Just because when the assessors reading that, they're going to want to make sure it got all four of those things. Who takes decisions and who approves what? That's right, yeah. That sounds like one. Establish relationships between project governance and organizational governance structures. Can you see how to 1.2, 1.3 quite closely aligned? Yeah. Because you'd establish the relationship bearing in mind the type of project, the more complex a project, the more bureaucracy, more governance you need. And then so you design a process, it was more complex and more complicated and more controlled. So they're all bound into each other. I think it's much easier in a lot of ways to read this as one and write 250 words about governance and how you implement it governance. And you know, as long as you pay attention to the individual criteria, if you try and deal with them independently, you're going to end up with a lot of repetition. And the framework is very important. So for example, you may have a stage height process, you may have a life cycle. And again, without going into detail on life cycles, but you may have simple projects that don't need that level of rigor. You may have other projects that is quite critical for the organization. And you may decide a different framework is more suitable or appropriate. So it's about doing that while still abiding to the rules and the policies of the organization. So my company rules are these and the way I'm going to fit those company rules is this. That's right. What is that in the PMP? That document you write that? Well, if you imagine it, what's going to happen is the bottom half of this. If you imagine this as a funnel, the bottom half of this is going to be the top half of the intergrace planning funnel, because those governance arrangements take what you're doing the project, right? Let's go down next level. Yeah. Well, but if you look at Pp1.1.1.5, for example, I mean, let's do them in order. 1.4 adopt or just the governance structures as required. It may not work. So the governance structure you establish and you design may actually not be effective. So if that is the case, you will have to show how you adjust it as required. This is much more to do with organizations that have a very well established process. And you know, project managers don't get to choose whether they use that process or they use that process. But that process isn't a one-size-fits-all. It depends on the complexity, it depends on the size as to how much or how little of that they use. So this is about how do they choose how much or how little, how do they choose which bits do not do, you know? So the adopts the governance structure. I mean, we weren't, we never were at rail. We've got a thing called grip, which is quite a widely well understood process, you know. And grip is quite, dictates quite carefully what you do. It doesn't apply to everything. Well, within there they've got the level of control. Level of control. More complex projects get more bureaucracy. Well, that's a really good example of 1.3, you see. Yeah. Yeah. If I was in that environment, I'd be talking about level of control and using that as evidence of 1.3. And then you may have another situation of organizations that do different nature of projects. And if you are running infrastructure projects, but also you're doing an IT project, you may want to adjust your governance and have a different type of framework, something more like an agile or iterative life cycle for that project. So you need to demonstrate how you adapt it that depending on the context of that project. 1.5 isn't that too bad? No, that's so cloudy. And that's the one you were saying John goes with 1.1. That's racey charts. Oh, it is. Hey, let's hurry for racing charts. You love racey charts. Yes. So is any form of responsibility assignment matrix is how responsibilities and accountability is where agreed and documented? Okay. And 1.6 ensure effective decision-making through maintained governance structures. That's like a twin of the one above isn't it 1.1? Well, this is about safety. Effective. Effective decision-making. So you've got a governance structure that says you're going to have a stage gap with you. You have a stage gap with you. So you just have to demonstrate that you've been operating it. Issue management change management too. All of that. All the project boards do for whatever you call it. In 250 living groups. And clear decision-making accountability and responsibility. So not everyone could just like make decisions. So it will have to be well structured and effectively apply. Okay. Generally speaking, version to a chart that is I think much better than version one in terms of the language that is except for PB1.7 which is completely pointless. Sure. Effective reporting through maintained governance structures for appropriate staffing and maintenance. I don't understand that one. No, no. That's a tricky one. Effective reporting. So it's about reporting through maintained [BLANK_AUDIO] Mae'r iawn i'w i'r iawn i'w i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r iawn i'r ac mae'n gwneud ac mae'n gwneud ac mae'n gwneud ac mae'n gwneud ac mae'n gwneud ac mae'n gwneud ac mae'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio. Mae'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw i'n gweithio'r unrhyw. Mae'n gwasanaeth y gwasanaeth y gwasanaeth y gwasanaeth y gwasanaeth y gwasanaeth y gwasanaeth y g ac mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny, mae'n gweithio hynny. Thank you very much.

Podcast Summary

Key Points:

  1. Governance arrangements focus on organizational project oversight, including decision-making hierarchies, authority levels, and accountability structures, rather than individual project management.
  2. Effective governance involves aligning project governance with broader organizational policies and structures, especially in complex or high-risk projects that require more control.
  3. The new framework includes seven criteria, forming a funnel from broad organizational governance down to project-specific practices, offering greater flexibility and choice.
  4. Project managers must define and document decision-making processes, escalation paths, and responsibilities through tools like responsibility assignment matrices (RAMs).
  5. Governance structures should be adaptable—adjusted based on project complexity, type (e.g., IT vs. infrastructure), and required level of control.
  6. Effective decision-making and reporting depend on consistent, maintained governance processes that ensure accountability, transparency, and stakeholder communication.
  7. Governance is not one-size-fits-all; its application varies depending on organizational culture, project scale, and lifecycle needs.
  8. The inclusion of adaptive governance reflects a shift toward practical, context-sensitive approaches that support real-world project delivery.

Summary:

The podcast explores the updated governance arrangements and reviews in project management, emphasizing clarity and practicality over bureaucratic jargon. Governance is defined not as managing individual projects, but as overseeing multiple projects through structured frameworks involving decision-making hierarchies, accountability, and reporting. The revised framework includes seven key criteria, forming a logical funnel from broad organizational structures to specific project-level practices, providing flexibility based on complexity and context.

Key elements include defining authority levels, establishing clear reporting lines, and using responsibility assignment matrices to document roles. Crucially, governance must be adaptive—tailored to project type, size, and risk, such as applying rigid processes in infrastructure projects versus agile methods in IT ventures. The discussion highlights that successful governance depends on alignment with organizational policies, consistent decision-making mechanisms, and responsiveness to project-specific needs.

7 appear vague, the overall shift reflects a more realistic and practical approach to governance, empowering project managers to demonstrate competence without overcompliance. The framework acknowledges that governance is not static, and its effectiveness is judged by its application, adaptability, and contribution to project success.

FAQs

Governance refers to the organizational framework and decision-making structures for managing multiple projects, while project management focuses on executing specific projects. Governance addresses accountability, reporting, and authority, not the day-to-day execution of tasks.

Governance arrangements involve complex structures like decision-making hierarchies and reporting levels, which are typically managed at senior organizational levels. Large organizations have established policies and frameworks, making governance more relevant and applicable than in smaller, simpler setups.

It means clearly outlining who makes decisions, who approves actions, and how decisions are escalated within a project or portfolio. This ensures accountability and consistency across projects.

More complex or critical projects require stricter governance, such as more formal processes or controls. Simpler projects may use lighter governance, like agile or iterative frameworks, showing flexibility based on project context.

It allows project managers to tailor governance to fit the specific needs of a project—such as using a rigid framework for high-risk infrastructure work or a flexible approach for IT projects requiring agility.

Governance ensures clear accountability, defined roles, and structured processes for decision-making, including issue and change management, to maintain control and consistency across project activities.

Chat with AI

Loading...

Pro features

Go deeper with this episode

Unlock creator-grade tools that turn any transcript into show notes and subtitle files.