So that's organizational change management. That's its own area of expertise.
So the best advice I can give you is if you have an O. C. M available to you. Um, leverage. Their resource is
ah, bunch of skills that they can bring to the problem of actually getting the organization ready for this change, which is going to be the result of the project.
In addition to that,
you have change management,
remember, dude ization of business like he grows more and more important.
what you didn't have to do when you start getting into enterprise projects
not only have project change control, but you have to have
what I'll call I t universe change control. And that's where a configuration management database or C M. D. B comes in. You have to have the visibility and the 360 degree
vision of what your systems, enterprise applications, whatever that you want to call him. But your I t universe your I t infrastructure.
So if you picture a system, it's five things, right? Hardware, software
and processes that was generally make those five things generally make up a system.
Your configuration management database
means to have all of those things in it. So not only does it need tohave
your hardware and software that's installed on the computers and servers that are in your organization, but also
what do those servers do? What applications do they support?
you're talking about Amazon, they've got some servers with a bunch of stuff on him
to support Amazon's Web store.
But the Web store is also a configuration item is part of the configuration management data maze. So
you would need to make sure you include that those higher level applications as being part of your see MTV.
So you're C. M D. B is
uh, really. And truly getting your arms around
I t management, which, of course, includes project management.
So with the properly configuration configuration, man, been database
right. Two universes out there.
Oh, CME folks were doing their own thing
when a new enterprise project begins,
or any kind of project. Really,
you now have the infrastructure available to tie it to your enterprise project. So
ask yourself the question.
What does this enterprise
right and then a system replacement. Is it something else?
impact. Show the relationships that exist
your your cmd be universe, which also, by the way, has to be maintained and passion and service. And if the server goes down after the reboot, it's all these changes now are happening inside this C M d B.
That's changing virtually real time. While you're trying to do your enterprise project management
and your enterprise project management efforts are affecting those systems as well. So it's a constant. While saying speed and technology, it's a constant
challenge to keep the information up to date. So what you see here is, um,
that same system, the configuration management database.
Um, but this is kind of showing how
the system support themselves, that you have me on this case. You've got a firewall or I S P firewall for your Internet service provider,
your main or pruner firewall
that's outside your organization, your main switch,
second floor switch, and so on, and so on. The idea here and then the computer that's connected to it. So the idea here is as you go through your C, M, D. B and you build your I T universe,
you can start showing relationships. Now let's say all this is still true. And then after that second switch,
there was a server that was running your Web application.
What? Those are the kinds of things that would be visible
in a sea mdb. So, as your C M. D B is being updated, you have
incidents that are affecting your configuration items. You have projects affecting your configuration items you have
I t. Security affecting those those items.
So there's just a constant amount of change
and adding enterprise
projects into that. The only way to effectively do that is really toe have that c M D. B
and enable it to gain that level of visibility of your entire enterprise. So you know
who's getting patched, whose computers were down, who's getting new servers.
Project is gonna impact this enterprise system
by replacing it or whatever. So in summary,
we covered enterprise change management, and we also discussed the difference between i t Change Management, which uses the C M D. B and is very much focused on the systems within the organization.
An organizational change management, which is more focused on the people and preparing the organization for the changes that your enterprise project is going to bring about.
I want to thank everyone, have a great day, and I'll see you the next video.