2.1 Projects, Operations, and Organizational Progress
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
hello and welcome back to Enterprise Project Management
for this lesson. We're going to cover the difference between projects, operations and what organizational progresses.
So one of the things that I like to use a swimming analogy,
which makes a lot of sense to me because I'm a retired military diver
operations day to day activities, the things that the organization does
would be the equivalent of treading water if you were, say, in the middle of the ocean or middle of a pool, something along those lines and the reason why I use that term treading water is because
operational activities are vitally important to the welfare of the organization. If you stop treading water, you'll drown.
If the organization is unable to conduct operations day to day activities, the normal functioning of the business,
they will not have the revenue with which to invest in enterprise projects. So
what we want to look at as we get into enterprise project management, especially with dependency that constrains, is you have to realize that you can't shut down an organization, spend a bunch of money to do some sort of enterprise level project
because there will be no money so we have to dovetail operations and day to day activities into the strategy. Execution of an enterprise project.
The Enterprise Project Strategy. Execution Peace is what helps organization swim to shore. So you have to tread water first, and you have to remain afloat during the entire project, obviously,
but if you don't do enterprise project management, then you'll never be able to change your direction and move to shore or move to the side of the pool to accomplish your strategic objective
of the organization.
So there are operational considerations
on enterprise projects and the really operational considerations on all projects, but they're especially important enterprise projects. You cannot
affect the operations too heavily
during the execution of an enterprise project.
Conversely, you can't let the day to day activities get in the way of your ability to swim to shore, because if you tread water,
you get tired. Eventually, you won't have the ability to swim to shore. So there's there's quite a balance that you need to strike
between strategy, execution or enterprise project management. They're kind of the same thing
your operational and day to day activities.
Let's talk a little bit about the Project Life cycle.
What we call project originations or ideation, that the terms are kind of interchangeable is really the idea that
we can on Lee do so much right Iron Triangle strikes again.
We have all these great ideas, all these possibilities, all these business challenges, all these opportunities in front of us.
But we don't have infinite resource is we don't have the abilities to pursue too many different strategies. At the same time, not even a major conglomerate like G E can pursue too many different strategy at the same time. That simply isn't the resource capacity within the organization.
So part of the project origination process is what I call the idea. Finally see a little picture on your right there way have these ideas, thieves, thieves, things that we wanna potentially research and try to execute and turn into the next
Tesla or, you know, whatever the next great organizational world changing project.
we have to look at what's the business case with the initial scope
and the really getting to, from an executive level standpoint, sort of the two questions of Can we do it?
And should we do it right, So Enterprise project management is not necessarily about doing things correctly, although there is definitely that component in execution. But it's really about
at the origination level anyway. It's really about doing the right things. So the Project Life cycle begins
in origination or ideation, and it's trying to select what are the right things that we should be doing. And part of that has to do with a project investment mindset, and we'll get into some more detail on it later on in the course. But think of it as if you were investing your own money
into an organization.
That portfolio you might have some money in stocks might have some money in bonds. You might have some money in gold or silver whatever,
but the portfolio is what you care about. You don't necessarily care whether one company is doing better than another company, or whether your idea for what would be a good
new widget is right you care about is my portfolio
generating income and my getting a return on my investment? Because ultimately what you're doing is lending money to a company. If you're talking about the public stock market
in exchange for a future profit, and that profit should exceed what I currently put to that
at the origination phase, this is where those financial skills become so vital because
everybody, not everybody, but most people are married to their ideas. If they're the one that put that idea into the idea of funnel, it's because they believe in it
and they want to see it come to execution.
But part of that origination phase is looking at it from a investment mindset and saying, Well, yes, this is a good idea is a good idea, but idea B is equally good idea, and it has a greater return on our investment. So where we would be better off as an organization
putting our money in tow idea be
regardless of how cool I d a idea A is.
So then you get into was called Project Initiation. So you've got your idea. You've done a business case very high level, looked at r. A. Y very high level, and now you've decided that at a minimum it's worth doing the research to see whether this is a viable project.
So from this point forward, you're gonna hear a lot of terms like progressively
elaborate or, uh,
interpretive development thing, that nature. And basically what it's saying is, you know, at this point in the project, we don't know who's gonna be programming widget, eh?
Or who's what Color button B is gonna be.
That's way too early on. But what we're looking at is let's start looking at
the risk, the complexity of the project. Let's develop that project charm that we talked about in the previous video.
Get that toe where everybody's in agreement so that that, very importantly, they will sign the project charter again, going back to the Iron Triangle, going back to the driver week and strength.
It's the most challenging thing that I've ever personally had to face in. Project Management is getting a sponsor to sign a project charter and agree in writing
that this is the least flexible.
This is the most flexible I have. The as the PM I have the ability to extend the schedule or spend more money or or
bring in less of the performance requirements,
and it's agreed to buy the sponsor. They want it to their to their defense. I mean, everybody wants they want all everything under the sun as much as they can get. They want their money destruct as far as it can.
Part of the PM's job is to sort of be the brain on someone's parade a little bit and make sure that you get that information in the charter and everybody agrees to it ahead of time.
So a project charter is the project's constitution, and at the enterprise level,
we're talking about
a Constitution in the sense of the U. S. Constitution, meaning
that we have a formal requirement to change it. And what
is part of that change process? We won't get into details about it right now, but what part of that process has to also be agreed upon
during the Project charter creation phase so that nobody is surprised later on down the road, it governs the overall project objectives,
So the project are does necessarily care how the sausage is made. But the Project charter cares what the sausages is gonna look like and what it has to be able to do at the tail end. And it really is used as a metric
to determine whether the project was successful or not.
When you hear terms like project failures go creeping that nature. What they're really saying is when compared to the Project Charter we did not achieve our objectives were solve our business case.
So in summary,
we talked about
projects versus operations and different organizational
requirements around both of those fields. And we talked about the beginning of the Project Life cycle. In the subsequent video, we will go in more detail about each of the phases of the project life cycle.
3.1 Project Charter Part 1
3.2 Project Charter Part 2
4.1 Project Planning Part 1
4.2 Project Planning Part 2
4.3 Project Planning Part 3