8.1 Business Analysis and Complicated Modeling Part 1
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
Hello and welcome back to Enterprise Project Management. This is Cane. And today we're gonna be going through less than eight
business analysis and complicated business modeling.
One of the things that I really want you to remember is in this particular lesson. What we're talking about is complicated business process is not to be confused with complex business processes, which will be in the next lesson.
So what we're looking at here are processes that are, no matter how complicated that they are,
are still still have enough finite variables. They were able to get a good model for how we expect the system
to process the transaction, if you will.
And one thing to keep in mind also is a system is made up of five separate things
and processes processes being either technical or manual. So when we talk about a system, especially in business process modeling,
you want to take those five things into account because if you only focus on the technical side of the house,
then you're going to
underestimate the impact of
the people and the processes that may exist outside that system. So don't think of things necessarily in a vacuum.
Try to think of the system holistically with all five of those elements. And again, they are
software, data, people and processes.
All of those make an enterprise level system.
So let's go ahead and get started
now. Business analysis really got its start,
through the efforts of a gentleman named Frederick Winslow Taylor.
And what he did is he wrote a book called The Principles of Scientific Management and you can do the link on this slide here. That should also be visible below the video that you can use to greet a little bit more about him.
But basically he was a,
you know, a child of wealthy parents in from New Hampshire.
He started off in Harvard, had some eye problems that was given him headaches or something like that. I can't remember the details, but basically he was unable to complete his degree from Harvard. So then he went to work for a machine shop on the factory floor and one of the things that he noticed Waas during the manufacturing process,
he saw a lot of artisans. If you will, that would start on whatever it is they're building and they would
you'll stand around it, work
their own pace, had their own processes. Each artisan did things differently, so they produced the same item. But the head wide and varying tolerances and his analytical mind sort of indicated to him that there would that there should be a better way.
So what? He ended up doing WAAS
taking studious nose and researching
various steps that it would took to build whatever the manufactured. I don't waas and then d compiling that into a series of distinct
movements and processes and individual work packages, if you will.
And then he took that information and looked at the layout of the factory floor. How close the tools were in what order the tools were for the artisan and so on and so on. And ultimately, what he created was that business process model that was
the maximum level of efficiency that the human being was capable of wind producing this particular item. And then again, like I said, he wrote a book called Principles of Scientific Management,
and what he really was trying to do is quantify
the human horsepower like what is the maximum level of output
of a person
reduced the number of variables to a finite set and control for them and create this utopian vision of what maximum efficiency. But look like
now the mist of all this. He had Cem
rather controversial human resource believes he believed that all workers were really lazy and some other stuff, So I don't want to give him necessarily a ton of credit for
business management in general. But I think that if you just keep focused on the complicated problem solving process, So he used sort of that deductive reasoning, um, type of process, whereby he said, How do I make a car?
I've gotta get the frame with wheels on it, Put the brakes on before the wheels and so on. It's on.
So therefore, you know, this is the most efficient way that I can scientifically determine
to build this car, and I want to put
all my tools in a certain order. I don't wanna have my big, heavy wrench be the farthest tool from me. I don't want to have to walk across the shop floor when I could just turn around and get a tool things of that nature. So he was very interested in that efficiency and really maximizing that human capacity so
fast forward, top 100 years or 150 years.
what he really established
was this idea that if you have a finite set of steps, regardless of what that is, it could be
Whatever the case might be. If you have a finite number of steps,
you can model that,
and when you model that you can then go back and look at that process model in order to determine if there are any levels of efficiency
in order to increase the productivity of that model.
why does this matter for enterprise projects? Well,
one of the things that we find when we study enterprise project failures is that
the business modeling process,
especially in government but even in private sector, is usually short changed. And what I mean by short changed is you either invite the vendors into early. So therefore, what you're really doing is looking at the vendors determination of what the business process model is
and not really looking at the adaptability of that model to your organization
or you just don't take the time to really drill down into the well they sometimes call, as is to be specifications,
to really understand what this model is going to entail for your your organization or you
model be existing process. And this goes back Thio. I mentioned it early on in the course, the thinking for implementation,
where you're so hung up on how you currently do business, that you basically build a new system that models all the inefficiencies of the existing system, in which case that bears the argument of why I have a new system. So
as an enterprise project manager to the best of your ability, especially when you're in that stakeholder engagement. Working with your sponsor Working with your Project governance team, you really want to
be forceful advocate for
the time it takes to really do a proper business model.
Understand what your processes get your arms around and get the team all on the same page. So you're looking at the same set of data and then take the next step
of looking at where efficiencies can be gained in that model. Before you start developing whatever your new system is going to be
and again and system is those five things. So I'm not necessarily just talking about i t I'm talking about all five elements
oven enterprise system. So
take time. This is an important step. This could really make a break your project. So do not be afraid to spend quality time on your business process analysis.