12.2 Enterprise Project Execution and Governance Part 2
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
6 hours 23 minutes
having a PSC
is one of the key elements to getting
gaining the ability within the organization to prevent project failure. So if you look at some of these top 12 reasons
like a top management support Well, hey, you know what? Having a PSC kind of eliminates that issue because your top management is now a part of your PSC
stakeholder involvement. Same thing, right? If your stakeholders are on the PSC, they're involved.
so some of these things failure of change, control process, your P S C is the folks that are supposed to be controlling the change within your project. So having a good PSC eliminates a number of these variables that have been quantitatively proven
to cause the majority of project failures. So just kind of know in your head think about it, let it marinate a little bit that, you know, you've got a risky profession.
The bigger the project gets, the more risky that it becomes
and the proper selection and utilization of a PSC. It's really going to help you mitigate a lot of that risk and allow you to be successful.
giving you the guidance and the political cover and the decision making power and the political power
that you need
possible. And it does vary from project to project.
Like I said before, you want to bring the PSC on as early as practicable.
part of the problem that happens with some projects is
kind of They do the ready fire aim So they somebody usually high up in the organization, wants Excuse project is the enterprise project. It's big, it's massive. It's complicated, but we got to do it. It's a great opportunity for the organization. We have huge r A y. This is the right thing for us to be doing.
Let's go. And by the time people start thinking of standing up the PSC and developing norms, you're already
almost complete with planning and the execution phase. So,
if possible during the discovery phase or the planning phase of the project, once you've gone,
maybe to the project charter drafting phase of a project,
if possible, it's not always possible. Start to build up your initial PSC so that they have a role in hand in that project. Charter development,
um, definitely include your main stakeholder, if possible, and then you also want to include members from other divisions or business units, not
packed the PSC with people that are not involved in the project. But just try to have
a good sampling of middle of senior management within the different areas of your organization.
One of the things that I found is a common weakness is that the PSC
is formed. Everything's going great, but they don't have the ability to make a decision. So have some sort of process in place and make sure the PSC understands that they're in this these meetings. They're in this role
to make a decision to not
kick everything upstairs because they're too afraid to act on information and make a decision. So usually the E S C will give
some kind of guidance 10% of the budget, 10% of the schedule. Whatever the case might be in, the PSC needs to feel confident that they can make decisions with in that room.
Uh, the PSC needs to be responsible for scope, schedule, budget, the old iron triangle. Remember the PSC loyalty at this point, and we'll talk about this in the next couple of videos, but think of but their loyalty
when they're in this PSC meeting as to the project, so they can almost put blinders on for a minute about the rest of the organization and their day to day job. Everything else. And they just need to think about
what's best for the project, and I'll explain why that is later on. But that's
the way to think about this responsibility thing.
If you can avoid even numbers, that's great, because then you don't have voting deadlock when they're voting.
Um, and again, voting deadlock is a problem. If it happens a lot, just because you're kicking stuff up to the E S C, that doesn't really need to go to them, you just couldn't make a decision. And so now you're getting the E. S C involved in things that really are not part of their their role.
And then, of course, the SC does all the big stuff, and that's fine. We want them to do the big stuff. But you got to remember that
yes, he is there for the hard decisions that really complicated ones, the really expensive ones,
then that means that the PFC needs to have the skills and ability authority
to do more of the routine decision making within the project. So that's why I use the rule of thumb at 10% just because it's something everybody kind of easily understands. So small stuff PSC is gonna handle it. They're gonna tell the project manager what to do once it gets, you know, above there
their purview or their decision making authority,
then they're gonna escalate that to the exit
or the U. S. C. I'm sorry.
So that's sort of how the structure of the PSC and he s e needs to be set up. And we will continue mawr in the next video. Thank you.