in this post, we’re talking about bad p6 progressing. that’s right. bad p6 progressing. i’m about to launch a brand-new course called “advanced p6 progressing“. in this new course, i show you how to progress all sorts of different ways, earn value, financial periods, and much more. but one of the things that we really dive deep into is bad p6 progressing – what you should not do when you progress schedules.
in this video, i talk about bad progressing and i do it with one of my favorite new tools: deltek acumen fuse. that’s right. so, we’re looking at p6 schedules, but we’re looking at them through deltek acumen fuse. let’s dive into it…
import schedule into deltek acumen fuse
okay. what you see here is deltek acumen fuse. and what i have done is i’ve imported up at the top my baseline project called build project. and then i’ve imported all 11 of the update schedules. every month, we produce an update schedule. it refers back to the baseline. in deltek, you can import all of these projects at the same time and then start to do some comparisons and some deep diving on what’s looking good and what’s not looking so good.
the part of deltek that is the most helpful for the kind of bad progressing i talk about in this video is the forensics area. so, we’re gonna go over here to forensics. te forensic screen actually does a whole bunch of comparison between the baseline and all of the other projects. you can see them listed here down on the left-hand side and also in the table.
bad p6 progressing in this schedule
right from this screen, we can start to get into bad progressing that’s going on. so, we have our start date, our finish date, our baseline start, our baseline finish, the number of activities, durations, etc.
let’s start with start date. all of these projects started on the same date. that’s great. let’s look at the finish date. okay. the baseline lists 2020-08-20. you see not even the first update schedule matches the baseline finish. and in fact, you can see there’s a growing trend that every update every month, the finish date changes. now, we know in construction project management, it’s not unheard of to have changes and to be off-course. that’s cool. but we definitely see a growing trend that concerns me quite a bit.
so, between one month – let’s say update 6 and update 7 – the finish dates went out by five months. so, in one month, we somehow extended the project five months out. and you can see that trend continue. in fact, here in update 8, somehow, we pulled it back a couple of months from november 8th to july, and then we went back to october. this is disconcerting.
let’s go even a little further. let’s look at activities. the original baseline schedule had 472 activities. month one update schedule had 514, next month, 573, 580 in month three. and then we went from a whopping 582 three times the number of activities in month four (1525 activities). what is going on here, right?
as we continue down, you can see we max out at 2,300 activities. so, we started with 472 activities and we grew it to be 2,300 activities. so, what does that suggest? well, to me that suggests that number one, the baseline wasn’t very well done, and that this contractor or whoever’s putting this project together is elaborating the schedule as they go. so, they didn’t think about all of the stuff they were gonna do from the start. and they are elaborating and elaborating and elaborating as they update and make work and update and complete work. this is not what you want to be doing. this is what i call bad progressing.
bad progressing change management
so, i’m not talking about bad progressing from the perspective of, “oh, i fudged this one activity.” i’m talking about the growing trend that we see here. if you do it wrong in the first month, you’re gonna keep doing it wrong and keep doing it wrong, and there’s gonna be this snowball effect. when we progress, it’s really important that we don’t add scope. we can’t be adding scope every month. we can’t be doing that without going through a change management process.
obviously here, there is no change management process. the contractor is just adding scope and adding more activities and finding more work that they need to accomplish. and they’re adding it into their schedule. as such, you can see that there are so many more activities that there is no way we can match to the baseline. we don’t have activities in the baseline that are gonna match the extra, looks like 1,000 activities, in update 4.
tracking activity changes
so, now we can’t accurately track things. we need to have the same activity that’s in the baseline match in the updates schedule. we can’t have more activities in the update schedule that aren’t in the baseline – this is bad updating. now, i’m gonna take it one step further. what we’re gonna do is we’re gonna have a look at some of the activities and how they have changed over the course of these schedules. and for that, i can go to the activities view here in acumen fuse. on this screen, i have the activities here on the left-hand side. i don’t have enough space to actually put the names of the activities. and that’s okay. we can still understand what’s going on here by looking at the columns. so these are the columns for each of the update projects in the baseline project. and you can see how activities come and go by looking at these xs and checkboxes.
so, this activity didn’t exist in the baseline, but it exists from update 6 onward. and here’s an activity that didn’t exist in the baseline, it existed in update 5 and then it vanished. and we see that throughout this list where an activity comes and goes. so, for example, again, another activity here exists in update 6 and 7, and then it is gone again. it vanished. so, to me, i’m not 100% sure what’s going on, but i suspect that there may also be a changing of activity ids. that may be one of the issues that’s going on here as well.
when we change activity ids from one update project to the next, tools like acumen or even p6 will not be able to track that id, and again, properly link it to its baseline activity. and so that is another no-no. we don’t wanna be changing activity ids as we go through our updates. we want our activity ids to stay consistent throughout.
more we can do with acumen fuse
so, a couple of more things we can do with acumen. you can see that we can do some analysis around calendars, some analysis around status of activities, and even lags or leads. now, we don’t have time in this post to dig into all of these things, but you can see here more results of bad updating and bad scheduling to begin with. we have so many lags and leads in here. we have number of different calendars. there’s a lot of stuff that was not well thought and well developed in this project. this is a great example of bad updating and how that bad updating can snowball.
i’ve got more posts like this coming to you, especially around updating. if you’re interested, check out our brand new advanced p6 progressing course here.
comment below with your questions.
