Integrated planning in the APMCHPB framework refers to the creation of a comprehensive, organizationally aligned project management plan that defines scope, timing, cost, resources, risks, and governance. It goes beyond mere scheduling—encompassing a holistic view of project delivery through structured plans like work breakdown structures, budgets, and risk registers. The plan's size and detail must match the project’s scale and organizational expectations. Formal stakeholder sign-off is required to validate and activate the plan, ensuring shared understanding and accountability. A common misconception is equating integrated planning with Gantt charts, which belong instead to schedule management. Effective planning requires defining tools and techniques, establishing units of measure (like working days or weeks), and clearly defining activity dependencies. Ongoing monitoring and change control are critical to refine the schedule as new information emerges. Configuration management, though complex, is a key discipline that must be understood and applied appropriately, especially in formal assessments. The emphasis is on practical, demonstrable application—choosing criteria that best showcase an individual’s strengths, particularly for program or portfolio roles where hands-on scheduling may be less frequent. Success hinges on clarity, alignment with organizational standards, and strong communication of plans and changes.
(upbeat music)
Welcome back to another parallel project training podcast.
We're continuing through the APMCHPB competency framework
and we're onto 4A and 4B.
4A is integrated planning.
So the definition says here is the ability
to take forward the definition of outputs
into detailed planning, incorporating multiple areas
into the integrated project management plan.
Comment, set some lights on what that means.
- So integrated planning is not only about
when you're gonna do things, it's not your schedule.
It includes your schedule, but is the plan for your project?
Is what you're going to deliver?
Is how much is gonna cost you?
Is who is involved?
What are the roles and responsibilities?
And then how is that project going to be delivered?
So what process is what plans do we need to follow?
So it's a collection of those plans.
So when the APM definition says
is the ability to take forward the outputs
of the detailed plan process is about the group of documents
that answer that sort of questions.
- Okay, so let's go through the criteria.
One at a time, we'll start with 1.3 obviously.
1.3 is demonstrated compliance with organizational practice
when establishing the size, structure,
and contents of an integrated plan, John.
- Yeah, yeah, exactly that.
Well, I mean, the point is if you're building a garden shared,
you're not gonna write a 500 page project management plan.
And if you've got cross-row,
you're not gonna do on the back of the fact packet.
So I think the point is that your organization
is gonna dictate to you the size, scope,
nature of the planning that they are expecting.
I think we need to shoot a fox here.
There's, if you read the introduction here,
it says talks about commonly referred to
as a project management plan.
So integration planning could be analogous
to project management planning.
So you produce a project management plan.
So then the question is why do they talk about
an integrated plan?
Well, because a program manager won't produce
a project management plan,
and a portfolio manager won't produce a project management plan.
So I think what it project management planning,
program managers wouldn't be able to do it,
'cause they'd say, well, I don't know that.
So they call it integrated planning,
which is a lot better than it used to be,
is we call consolidated planning.
But now it's integrated planning,
but that really what you're talking about
is a generation of a project management plan.
And it actually says that in the narrative on page 28
of the guidance notes.
So when you're talking about any of this,
you're what you're really talking about
is producing a project management plan.
And all of this is kind of geared around that, really.
And would you have a huge plan for a little project
or a little plan for a big project?
No, so you have to think about
what the organization will demand of you later on.
And the first two, Pp1.1 and 1.2 are very specific.
So you're looking at dependencies
and governance arrangements and 1.1's looking
at constraints and assumptions, which are different.
I mean, a constraint is only 24 hours in a day
and assumption is we're going to work out of them.
Yeah.
So if you pick, for example, a project management plan,
so assuming that you are a project manager,
you cannot take the liberty to decide the way
you want to plan things.
So if you start with 1.1, there will be some constraints,
things that really are limitations.
And then assumptions, things that you may just,
as the world said, assume, but different projects
will require different level of detail
and different contents and different documents.
So in this Pp, what you need to show,
what you need to demonstrate, is what
were those constraints and assumptions
that you had to face when you decide
what are going to be the contents of your plans?
This also follows a similar theme, really.
The first few of these are all about doing the plan.
The second few, sorry, the last four
or so are all about running the project.
So 1.4 then says, included other relevant components,
plans and documentations.
What other relevant components are they talking about?
Could be plans.
For example, you need to follow a race management plan.
Could be some of the processes, change control process.
For example, so the different type of documentation
they fit different purposes.
Some documents are more like the delivery documents.
Your can charge, your cost plan, your resource plan.
All the documents is more about compliance
with your organization.
So some project management specific processes
and procedures and plans.
Yeah, well, that exactly couldn't agree more.
I mean, it says it at the top, actually, in the headings.
It talks about the intention is it
captures the fundamental components of scope.
So you'd have a work breakdown structure, quality.
You'd have the quality criteria and acceptance criteria.
Time, you'd have a ganchard, or a schedule, cost,
you'd have a budget, resources, you'd
have a resource histogram, resource planning,
risks an issue, a risk an issue plan, communication plan,
and success and benefits management and so on.
So what it's doing is it's pulling all those bits
and pieces together, whether physically or conceptually.
I think it's a bit naive to think a project management plan
always is one document that sits on the shelf.
It's probably a whole multitude of different documents
and references and hyperlinks and all sorts.
But essentially, it's the thing that allows you
to govern the project.
You know, we talked about governance.
So governance will dictate the fact
that you need a project management plan.
And then you go away and write a project management plan.
And this is what's in it.
But the bottom four, completed formal sign-off
and acceptance, continually monitored it.
So how would somebody go about showing
that they completed formal sign-off
without writing the sentence that I completed formal sign-off
and got acceptance of the plan?
So typically, you will expect a meeting
or a review, a forum to get, again, that formal acceptance.
And once the integrated plan is approved or sign-off,
then you could start putting that into action.
But you have to formalize a way to get formal acceptance
and make sure that everyone, all the stakeholders,
agree and abide to that as well.
And so everyone is really clear how this project is going
to be managing, delivering the products.
And in a way, it's almost like a communication aid,
because it ensures that everyone understands
the sort of like terms and conditions on this project.
Which, when you look at scope, quality, cost, and time,
you could also argue that that integrated plan
helps you as well to baseline those parameters.
I think you're right.
I think, in some cases, you can't, you'd say,
I've got formal sign-off by taking it to the board
and presenting it and arguing the case.
But there's very little you can do by written evidence.
It's going to be difficult in 250 words
to outline an entire sign-off process
without just saying the words.
Yes.
It was signed off.
Yes, that's right.
Can I just point out one here that's a bit naughty?
And that's 1.8.
Applied configuration management to a plan?
Yeah.
Because configuration management is not in itself a competence.
And unfortunately, I think I've seen evidence of people
being asked to discuss configuration management at some length.
And it's come as a surprise.
It's because it's been picked up by an assessor 1.8.
And someone's attempted to do integrated planning
or consolidated planning as it was.
And they're not actually able to substantiate that.
Because configuration management is a discipline,
quite complex discipline, or in itself.
And it's sort of lost.
And it appears, again, further on in some of the other competencies.
But I think a word of advice for people
is just make sure that you're familiar
with configuration management.
And I also have a recognition that it's not just document control.
Because I've seen that get unpicked in an interview.
Because even if you don't cover this in your written application,
they might decide to question you on configuration management
of a plan in your interview.
Oh, well, that's an interesting one.
Because I mean, I think the problem they have, this is a general point, really.
And maybe a subject of a podcast, all on its own,
is that you only have to do four of these.
So if I was an assessor, and I chose one that wasn't one of your four,
what are you going to say?
So if I said to you, if I was an assessor, I said,
could you just discuss how you apply configuration management plan to a plan?
And if you had never done it, what are you going to say?
So strictly speaking, yeah, strictly speaking, they could.
Practically speaking, it is more likely they try to explore what you've written.
Saying that, I know this is only about the PPs, don't rule out.
they may not be a technical knowledge question on that. So again choices are quite important,
but if you decided to write something on one point A, you will just have to show that
not only you know configuration management, but you apply that to your integrated plan.
For example, 1.7 is okay because if you have an integrated plan and you have to adjust any
of those parameters, you could demonstrate that you apply your change control process. So
1.7, it's probably easier to demonstrate whereas configuration management, as John said,
is a whole discipline in itself. You could write 250 words just on that or even more.
Good, so integrated planning probably looks like quite an intimidated one until you realise
they're probably just talking about project management plans and in which case it's a story,
Pp 1.1 to 1.8 goes from, you know, all program management plan or program management plan and
you just go through the process. Or indeed a work package plan, if it's a significant
work package, I think it could be a work package plan. So let's look at the alternative then 4B,
which is schedule management. The ability to undertake time-based planning with an emphasis on
activities and resource. I'm going to put a piggy on the ground here. One of the things that people
get confused about is they call a scheduler plan. So a schedule in this context is a schedule
of when things happen. So think Gantt chart. If you talk about Gantt charts under integrated planning
as being the core of the topic, you'll get rejected. So integrated planning is not a Gantt chart.
Schedule management is more of a Gantt chart. So if you love Gantt charts and you want to tell
everybody about Gantt charts. Do schedule management? Yeah, and if you start talking about schedules
or your Gantt charts in integrated planning, you can come unstuck if it becomes too dominant.
Okay, so let's go through the criteria. Then 1.1 defined tools and techniques for creating
and updating a schedule. Yeah, so two things here. So you define the tools or techniques
for creating your schedule. So that could just be a complex Gantt chart in Microsoft project
or primavera or it could be a more simple and effective just table in Excel for your schedule.
So you will have different techniques and you will use different tools and methods for creating
that. Once that has been created, you know, with all the components, your tasks, your durations,
your dependencies, maybe you may want to flag some milestones, you will have to keep an eye and
monitor it and then update it as appropriate. So it's two things and it's very important
to highlight that because you will have to demonstrate both to fully hit that criteria. Can I
just point out this is defined? Defined tools. So you had to show how you define the tools and
techniques, not how you use them. So this is about defining how you are going to create a plan.
How you're going to get a schedule and how you're going to monitor a schedule and update a schedule.
And when they're talking tools, they're not talking Microsoft project or?
Yeah, I think there's a moot point about because technically there's four things to do here.
Give me a tool for creating. Give me a tool for updating. Give me a technique for creating. I tell you. So there's strictly three, there's four things to do. I think you've
got to repast that a little bit or that does say and. So if you want to take the real purest view,
you've got four things to do. But I think what you're going to have to do is you have to show what
tools you were using and why and how they played a part in creating and updating a schedule.
So you can update a schedule. We wouldn't necessarily use Microsoft project to update a schedule.
That's not going to provide the data. That's going to be a way of recording the updates.
So it's quite a difficult one to do, PP1.1 actually. It's a lot in it. You could write 250 words just
on that one. What's the difference with a tool and a technique? Well, a technique is critical
path analysis or critical chain analysis or whatever else you can think of. Tools, probably Microsoft
project, maybe Excel, maybe Primavera. So you've got different tools you use, techniques you use,
and then you've got to show how they created updated. It's quite a big one. I can see people can
come and start with that one. So lots of it with them. PP1.2 established units of measure to
accurately define activities and events to be completed during a project. What do they mean by units
of measure? Well, apparently it's a schedule. We talk about time, not money. So you talk about working
hours, working days, working weeks, months, how you're going to record it, time recording,
schedules, all that stuff. So that plays into the earned value calculations really that
probably have a role to play later on. So then that feeds into 1.3. So they're asking how you go
about measuring it, and then 1.3 is asking how did you come up with those estimates?
Yeah, so this is very similar to the one in budget and control, but the difference is that now
in a schedule, what you need to estimate is your time, it's your duration. So how long activities
will take, what does it mean in terms of effort, you know, dependencies as well of all these tasks,
the sequence, and the real sequence, do we need to wait until that finish to start the next
thing? Or can we do that concurrently? So all of that takes a factor of it.
So quick, critical dates and milestones as well, by the way.
Yeah. And then 1.4, relationships and dependencies. Well, you know, you can think of the logical
dependencies like finished start, start, finish, finish, finish all that stuff. Or you could think
about sort of less firm logic to connect with, connect everything together. So and also from
a program management point of view, I'd be thinking about one project depending on another project.
So, you know, an external dependency is like I'm expecting the clients to do this. I'm
expecting the clients to do that by then, and you know, the equipment's not going to arrive until
then that's a dependency that has to show on the plan or that's what. So all of this is about the
nitty gritty, the detail, nuts and bolts of creating a schedule really.
And then the next one's, I suppose, about documented it. Documented seems to be the way
that stands out. How did you actually, I suppose that's how did you record it and share it?
Yeah. Well, the, the, yeah, the emphasis of this is on project monitoring and progress reporting.
So, you know, what role do those three things have in that?
Which takes you quite nicely onto, I suppose 1.7 talking about then communicating a regular schedule.
So, once you're monitoring it, how are you then communicating it to your stakeholders?
Yeah. Yeah. So, you monitor, you review your progress, then what do you do with that information?
So, you'll have to communicate that, you will have to keep people updated.
Maybe implications as well. Like, you know, we talk about those dependencies.
You may mention resource dependencies as well without going into a lot of detail because there is
another competence for, for resource management and team management. But, but somehow you need
to disseminate some of that information. So, this criteria is about regularly keeping the right
to stakeholders, including internal and external, updated into, and to any updates in, in your schedule.
And then finally, what do they mean by 1.0? Refined a schedule of activities based on effective
monitoring, implementing the change control process when required. So, you have to know change control.
And then what they're asking you, yeah, that's right. They're asking you to talk about how you
get that schedule up to date. And how you monitor it and how you use change control to change it.
Yeah, very mind when you put it in the first plate, you use assumptions, you may get estimates.
So, the more the project progresses, the more information you have, and sometimes you may need to
refine, or you may need to re-baseline your schedule. So, you will have to show that you implement
change control process when that happened. So, there's nothing particularly complex in here.
You've got to explain the tools and techniques you use. You've got to explain how you come up with
estimates for how long things are going to take. You've got to explain how you develop a schedule
and the relationships between activities. You have to explain how you're communicating that to
people and then how you're keeping it up to date. So, there's nothing that's rocket science in there.
For some people, that may be the bread and butter, and this is why it may seem quite an easy one
to pick, but if you are a program manager or a portfolio manager, you may not do that all the time.
So, again, in general, the general advice is play your strengths and go for the choice that you
think you could demonstrate more of the criteria. Thank you very much.
Podcast Summary
Key Points:
Integrated planning involves creating a comprehensive project management plan that covers scope, timeline, cost, resources, risks, and governance, not just a schedule.
The plan’s size and structure must align with organizational requirements, ensuring appropriateness for project scale and complexity.
Key components include work breakdown structures, schedules, budgets, resource plans, risk registers, and communication plans, all integrated into a unified framework.
Formal sign-off and stakeholder acceptance are essential to ensure alignment and enable project execution.
Configuration management is a complex discipline often misapplied in planning; demonstrating its use in plans requires technical understanding.
Schedule management focuses on time-based planning using tools like Gantt charts, but integrated planning should not center on schedules alone.
Tools and techniques (e.g., critical path analysis) must be defined and justified, while updates require monitoring and change control processes.
Clear communication of schedule updates to stakeholders is vital for transparency and alignment throughout project delivery.
Summary:
Integrated planning in the APMCHPB framework refers to the creation of a comprehensive, organizationally aligned project management plan that defines scope, timing, cost, resources, risks, and governance. It goes beyond mere scheduling—encompassing a holistic view of project delivery through structured plans like work breakdown structures, budgets, and risk registers. The plan's size and detail must match the project’s scale and organizational expectations.
Formal stakeholder sign-off is required to validate and activate the plan, ensuring shared understanding and accountability. A common misconception is equating integrated planning with Gantt charts, which belong instead to schedule management. Effective planning requires defining tools and techniques, establishing units of measure (like working days or weeks), and clearly defining activity dependencies.
Ongoing monitoring and change control are critical to refine the schedule as new information emerges. Configuration management, though complex, is a key discipline that must be understood and applied appropriately, especially in formal assessments. The emphasis is on practical, demonstrable application—choosing criteria that best showcase an individual’s strengths, particularly for program or portfolio roles where hands-on scheduling may be less frequent.
Success hinges on clarity, alignment with organizational standards, and strong communication of plans and changes.
FAQs
Integrated planning refers to creating a comprehensive project plan that covers scope, schedule, cost, resources, risks, and governance. It's not just a schedule but a collection of interrelated plans that define how a project will be delivered.
Yes, integrated planning is essentially the creation and implementation of a project management plan. It brings together various components like work breakdown structures, budgets, risk plans, and communication plans into one cohesive framework.
Key components include the work breakdown structure, schedule, budget, resource plans, quality criteria, risk management plan, communication plan, and benefits management plan—all aligned to ensure project success.
Constraints are hard limits (like time or budget), while assumptions are things taken for granted (like market stability). Both are critical when defining the scope and content of the integrated plan.
Formal sign-off means obtaining official approval from stakeholders through a review meeting or forum, confirming that the integrated plan has been reviewed, understood, and accepted as the project’s governing document.
Configuration management is not a core part of integrated planning and is often misapplied. While it's a complex discipline, it's not typically required unless explicitly relevant to the project’s documentation control needs.
Chat with AI
Loading...
Pro features
Go deeper with this episode
Unlock creator-grade tools that turn any transcript into show notes and subtitle files.