Hi, guys. Welcome back. I'm Katherine McKeever. And today we're going to go over pert or program evaluation and review technique.
Um, introduction to Pert. I'll give you a little bit of a heads up that pert is my favorite of the project management tools that we're going over in. Greenbelt Almond will go through it a little bit as to why. So what is pert? It's a really cool name.
It is. It stands for program evaluation and review technique. This actually came from the military for us.
Andi. It's a to a planning tool so a little bit different than our Gant chart and are Critical Path method, which was more of a timeframe tool. This is a planning tool that graphically shows both the tasks and the inner relationships.
So if you remember in critical path and in Gand, we said that you need to identify dependencies.
We didn't really talk about the relationships between the tasks other than some things can be done concurrently.
This is most commonly prefer performed in conjunction with the Critical path method. So we're going to do our per analysis, and we're also going to look at our critical path method remember Gant charts tend to be done after critical path because we have our work breakdown structure and we have our durations.
So then what we need to do is plug in riel date.
a perch, er is a little bit different than a critical path because it is now driven by delivery, Bols. So critical path tended was driven by activities where each of the little chunks was a work breakdown structure. Our pert
is we're not done with something until we have finished all of the test to create a delivery ble.
So the way that you want to read these is your little node. Your circles are going to be the actual delivery ble, and the arrows represent tasks and activities. I like this because it also focuses on best case and worst case timing.
So remember we talked about the critical path. This is how fast it can be to get this done,
Pert will show us how fast and how short. I think that this is really important for us toe represent to our project spam sponsors. Given the fact that most frequently your projects will be somewhere in between the best case and the worst case.
So we're jumping from node to node, looking at all of the things that didn't need to happen. You will notice in our color coding, our critical path technique is represented in blue, and our worst case is represented in red.
We know that this is going to be the longest that it's going to be. We can talk a little bit about project crashing
and investing extra resource is to get things done. But this is, um how well, what I would do to draw or to publish one of my books. So the first thing target audience and creating outline that's going to get us to our book proposal
draft copy. This is the longest step it's going to be. I'm actually writing the book. Then we're gonna buy for K a little bit.
So now we're doing things concurrently, recognizing that anything that happened prior to step three must be done in completion before we can move forward. So driven by delivery bols rather than, um rather than the actual tasks themselves.
So with that pop quiz of the project management tools we've discussed and remember, we've gone over critical path. Gant charts and pert. Which one of these is most like agile project management? And why
so in the Gant module, I talked a little bit about waterfall project management. It tends to be very linear. You have step a step B, Step C. Um, and then we're talking about agile project management, which tends to be more iterative. The answer to this is actually going to be pert.
And the reason why is because Critical Path and Gant
are driven by timeframes, whereas Per is driven by delivery bols, much like agile project management, where you have your sprints and you have your stories you are working towards, not a linear completion. Of all of the tasks in the list,
you are looking towards completion of your next sprint
so very much a very similar mindset. If you were to draw agile, agile project management and a graphical way, that's where you would see the inter relationship Agile was born from Pert. Because of that focus on
delivery bols and getting to your next item rather than looking at the time frame
and looking at in a larger picture, and both have their strengths and weaknesses, depending on the project and what you're looking to get out of the project.
So with that today we went over the perp methodology. We looked at a per chart which looks suspiciously like a critical path except
our nodes Air. Now our delivery bols, whereas are critical path are nodes. Were our activities from our work breakdown structure
and in our next module, we're going to go over project risk analysis, so I will see you guys there.