6 hours 23 minutes
then we'll go to the game core team
and we'll sort of repeat the same
basic process here. So you can start timers build.
Then we have to do
the recast build,
and then I have to do the read mouse build. These are just different again functionalities that were specified during the business process analysis
same same scenario here. I got to go to and say, OK, I can't do any of this until the Windows piece is complete
and this is gonna take me four days.
I couldn't do the ray cast at the same time,
but I can't do the read mouse until after the raid. CASS is done, and that's gonna take me three days.
Okay, so I can go connect that one to that one. I can connect this one to the end of this one
and this one to the end of this one and so on. So on and again in systems like Microsoft Project,
type of lot of dysfunctionalities for moving things around is done automatically.
So then I meet with the graphics team and I look at what their tasks are and they've got to
looks like they're just building the u I.
And okay, so really, they just gotta build a maze. You I
and then build the control. You I
or I should say, design, build,
dying to control you. And that's the gonna be the text and what colors they're gonna use and all that kind of stuff.
so they tell me
that's all they need to do.
When can you start? And they say, Well, actually, I don't really need anything from programmers to
start this build, but it's gonna take me 10 days. So I go to
take 10 days to do that, and I can design the control. You I as soon as I have the basic structure of the maze
so I can start that in the 19
and that's gonna take me approximately 10 days, too.
And then we can either set
a dependency here which will yell at us, but we could ignore it or just leave it overlapping. And you'll just know that this dependence this is not necessary dependent on this start, but is dependent upon it to finish.
And this particular software won't let you do those types of dependencies in some of the more advanced software, you actually have the ability to
do a start to start dependency or finished finished dependency so on. So you can sort of make all this magic happen.
And then if you go into the list for you, So let's say we've done all our dependencies, got everything figured out.
Then we need to look at what the duration is. So the create window functionality.
We started it yesterday. We're gonna have it do on win Tuesday. That's fine.
So I can't load graphics until Wednesday,
which will put that being done by the 26 thing with the build tables.
Play games. Take me till the second
start timers is gonna run till the third. And let's say that I actually won't get it done till the 12 of April,
and this will be done on the ninth and so on. And so on and again. We're doing this in a collaborative environment,
with the developers
asking them for their assumptions and where they develop those assumptions from
because sometimes experience. Sometimes
it's just a
what they call a swag, a scientific guests that has no real basis in reality. But you got to give him an estimate.
So then going back to the gang chart, I'm gonna look through as I've developed more, more. I'll have
dozens, if not more, of these individual tasks. And I look and see that Make sure that there's no red connectors, which there's one here, but we know why that's there.
And then I'll actually go in and assign Resource is of some of these. Oh, and then under project management, of course, you've got your status reporting.
Um, you might have,
uh, getting sign off
and so on. And you want to schedule those in the tasks in the schedule as well. But those are just product management tasks. Those aren't necessarily huge deal.
So then I go ahead and I'm gonna sign this task to me. Of course, there's only one person on my team. So what'll end up happening here is if I assigned myself to this task as well,
you should start to see, and this may not be advanced enough to do it,
but basically I've been assigned to two tasks.
The design may, as you I as well as the create window
and they're both on the same
are occurring around the same time. So what that means is that you'll either have to
build additional resources
delay one, because you're now what they call resource constrained, which means that you can't
have one person working 16 hours a day. It doesn't work out in the long run. That's what's called resource leveling, and this particular software doesn't have it really good
automatic way to do it. Which is fine because it's free can complain about price.
But what you would look too on a resource leveling standpoint is see where certain resource is our assigned to various tasks and say, OK,
you can't build the maze you I while you're also building or creating the window module,
unless you're telling me that you only need to do half and half reach.
So that's sort of part of the give and take
in the schedule development process and again kind of going back to the science and art of
building a project schedule, and this again is a water fallen based schedule. So we're doing very deliberative. We know what the order of things needs to be. We're really just trying to maximize our resource is utilization. So, for example, let's say that under this Ray cast,
I had a very busy resource.
But he had some free time.
Uh, during a certain window, I might go ahead and just slide this to the right
even though it creates that that slack that we talked about in the last lesson.
But because I'm resource constrained, that's just gonna have to happen. And that might affect my critical path. And it might affect when I can bring the project in for completion. It really does does depend. But
the couple of main things take away from this. This video is
you have to build your business process, know what you're gonna do. You know who you have on your team, what their skill set is.
Put together your tasks in your sub task. Start high level. Don't be afraid to start high level and continually refine because you may have another layer of sub task below this and so on. Continually refine those tax and processes until you've got a pretty good idea of a workable schedule.
Now, from that workable schedule standpoint, you know, then you have to write it for approval and and actually the course, monitor the schedule and things of that nature.
this is all a very quote unquote scientific guess
of what we think is actually going to happen. So you need to be prepared during project execution, which is the next video to adjust accordingly when things aren't working the way that you plan. And you also need to make sure that your sponsors are aware that we did our very, very best
to guess what we think needs to happen. But we won't really know until we actually start the project and start developing.
So in summary, we did a practical exercise on project planning and scheduling. And we're going to begin project execution on the next video.
Thank you very much.