The Money Files

It’s time for part 4 of our journey through the Scope Management Knowledge Area from the PMBOK Guide®-- Sixth Edition. Today, we’re looking at the Create WBS process.

You can find the previous parts here:

• Plan Scope Management
• Collect Requirements
• Define Scope

The point of this process is to move from having the scope statement (from the Define Scope process) to a scope baseline. The Work Breakdown Structure (the WBS of the process name) gives you the baseline for what the project is going to create. It’s scope, but in a lot more detail than a scope statement.

Personally, I don’t often use the full WBS process. If you are on a small project, or leading a project where you have done similar work in the past and are working with an experienced team, or you have a scope that isn’t easy to button down, then approach the WBS process with an open mind. I have lost too much time in the past creating a full WBS and WBS dictionary, with lovely descriptions of everything, only to find that the next week the scope changes due to the whim of senior management, and all my work is rendered pointless. So this is definitely a process where tailoring comes into play, especially if your ‘predictive’ environment isn’t really that predictive!

You need a scope baseline in order to exercise change control, but you might not need to follow this process to the letter to get it. Just sayin’.

Create WBS Process

This is the fourth process in the Knowledge Area. We are still in the Planning process group.

While I might not use the full WBS process and terminology, the overall objective of this process is to break down the work into smaller components that are more manageable to deliver. You take your scope statement and basically turn it into chunks of work that people can actually do.

This is a process you can do at various points in the project so you might not be able to decompose everything at the beginning and that’s fine. Repeat the decomposition effort as you move through the project and more scope is known, or you find out you have to break it down further to get where you want to be.

Inputs

There isn’t much that has changed from the Fifth Edition with this process, and in fact the only small changes are here with the inputs. The inputs to this process are:

• Project management plan – instead of the scope management plan (the same change as we saw in the Define Scope process).
• Project documents – these were also added to the Define Scope process, and here replace the project scope statement and requirements documentation, which are now out. We’ve seen this trend towards more generic terminology across the whole Fifth-to-Sixth rewrite, and it is to be welcomed. While the scope statement, for example, is no longer specifically mentioned, you would want to refer to it (obviously). However, there’s now the explicit understanding that there might be other documents beyond the requirements documentation and scope statement that could be useful to you at this point.
• Enterprise environmental factors – no change here, it was on the list before.
• Organisational process assets – again, this was previously on the list so isn’t a change.

Tools & Techniques

Nothing has changed with the Tools and Techniques. The list still remains:

• Expert judgment
• Decomposition.

Although if you want to get picky I think they were listed in the other order in the Fifth Edition. Frankly, I don’t think the order of techniques matters much. I have never thought they were listed in priority order.

Outputs

Once again, there are no new or changed outputs to this process.

You still end up with the scope baseline, which was the ultimate goal of doing the WBS and ‘project documents updates’, which is so broad it could include anything. However, it’s really talking about updating any documents that need a reference to the final scope.

People often think of the WBS as a diagram, but it’s much more than that. The graphic is useful, but on larger projects they can get so complicated they are difficult to interpret. Also, I’m not a visual thinker – I expect that’s another reason why me and the WBS have never really got on.

The scope baseline includes:

The scope statement – you probably won’t need to amend this much from previously, but you might want to check it over as you work through the detail of the scope, to make sure it remains consistent.

• The WBS
• The work packages
• The planning packages, if you need to describe work without schedules (because the work package should have schedule information in)
• The WBS dictionary – a summary of all the work packages so you can easily reference them.

I do like the idea of work packages, and I do use this concept on my projects. If the language of work package isn’t understood, I create a terms of reference which covers the same main elements as a work package, and this can go to workstream leaders.

Next time I’ll be looking at the fourth process in this Knowledge Area: Validate Scope.

Pin for later reading:

I’ve worked on projects where all the resources are in house, but it’s more common (at least in my experience, to have some external supplies needed on a project. Whether that’s external legal advice or buying a software product, many project managers have to work with suppliers.

But what should you ask them before you start work?

This video gives you 3 key questions you should talk to your vendors about before the project starts. They give you a way to have a conversation about working practices and expectations before you start really building one of the most important relationships you’ll have on this project.

Watch the video below and then share what you typically ask suppliers in the comments below.

For more information about working with suppliers, and a bonus 2 extra questions to ask, check out this article.

Pin for later reading:

Every so often I do a roundup of questions that I’ve been asked, relating to the topic of this blog – project budgeting. Let’s dive in to some more of your questions about project budgeting!

What’s the best tool for managing your project budget?

It depends!

Unfortunately, there’s no simple answer to this. The answer depends on how your company expects budgeting to happen.

Many companies rely on Excel to track and report project budgeting. I have an Excel spreadsheet myself that tracks invoices and purchase orders, as well as current budget and forecast. We have a corporate template so all projects track the same thing, although because it’s Excel it is possible for project managers to amend the spreadsheet and personalise it. There is some latitude to track what’s important to this particular project. For example, sometimes I need to track spending in different currencies or with different tax rates, and not all projects at my company require that.

So – while I can’t give you a one-size-fits-all answer to this question, the answer lies in your PMO or Finance department. Talk to them about their requirements. Do they want you to enter data in your project management software (that’s the main alternative to spreadsheets) or do they have another way they want you to track your budget?

If there is no corporate standard, you have the latitude to work it out yourself. Spreadsheets are the easiest to get started with. Ask another project manager what they do, or search projectmanagement.com for templates.

How much contingency should I add?

This question comes up a lot!

And unfortunately, again there isn’t a simple answer. You might have organisational standards about how much contingency gets added to a budget. But in my experience, that isn’t the case. Project managers are largely left to their own devices and are expected to work out contingency themselves.

You should ask yourself:

• How risky is this project?
• Have we done something like this before that gives us confidence in the estimates?
• How certain are we that we’ve got all the tasks on the plan?
• Have we got the full requirements or might something else come up later that absolutely needs to be done?
• Do we have confidence in our supply chain?

The answers to these questions will help you work out whether you need to be generous with contingency or whether you can cut it back a bit.

The riskier the project, the more different it is from things your company has delivered in the past, and the level of confidence you have in the whole thing determine the contingency.

A reasonable starting point is 10% on the whole project budget. Cut it down for areas where you have confidence – like project initiation and close down, where the tasks are relatively standard and you can estimate the work more accurately. You might need to boost up contingency on project areas where you are doing unique work that hasn’t been done before and where your estimates are basically guesses.

Always make your contingency explicit in the budget and explain to your sponsor why it’s in there.

What’s a project budget summary?

It’s just the headlines of the budget. For example:

• The overall budget number – how much money your whole budget is
• How much you’ve spent so far
• Some text to provide narrative about whether you are on track or not.

That’s it.

You use the budget summary in your project status reporting. It goes in the box about project budget update (or whatever your similar section on your report template is called). All it’s for is to give the project sponsor and the wider stakeholder group the short version of where the project is with its spending. They don’t care if you’ve spent £3.50 this month on stationery suppliers for team members on the road. They only want to see the big picture, and the summary statement gives them that.

If you feel that the total + current spend + narrative doesn’t give them enough information (or they are constantly asking you for more detail) then provide what’s necessary. They may want estimate to complete or some other type of information. Ultimately your project reporting should deliver what they want to know about the project, so ask them if your summary is hitting the right points and if not, switch it up.

I’ve done other Q&A articles before. If you enjoyed this one, check out the other instalments in this series.

See Part 1 here

See Part 2 here

See Part 3 here

See Part 4 here

See Part 5 here

See Part 6 here

See Part 7 here

See Part 8 here

And if you have questions for me, please drop me a message! I’d love to feature your question in an upcoming article.

Pin for later reading:

We need to measure project performance to see if the project is on track.

The graphic below shares some ideas on the different ways you can measure work performance. None of these suggestions is better than any other – they are all appropriate for different projects, environments and levels of project management maturity.

Do you use any of these approaches to measure progress on your projects? Why (or why not)? Let us know in the comments section below!

If infographics aren’t you thing, you can get almost the same information (with perhaps a teeny bit more detail) over at this article:

7 Contract Terms You Should Know

It’s time for part 3 of our journey through the Scope Management Knowledge Area from the PMBOK Guide®-- Sixth Edition. Today, we’re looking at the Define Scope process.

Check out the previous parts:

• Plan Scope Management
• Collect Requirements

The Define Scope process happens early in the project so that everyone has clarity on what the project is supposed to deliver. Unclear scope means unclear expectations. And that nearly always leads to confusion, dissatisfaction and conflict on the team.

So take the time to actually define what is in and out of scope – that’s what this process is all about.

Define Scope Process

This is the third process in the Knowledge Area. We are still in the Planning process group.

Inputs

The inputs have changed slightly from the Fifth Edition, but it doesn’t feel major. The inputs to this process are:

• Project management plan – instead of the scope management plan.
• Project charter – which was there before.
• Project documents – again we see the generic terminology that can basically include anything about the project. In this case, we’re talking really about the assumptions log, requirements documentation and the risk registers, as there can be useful things included in there that need to be transferred to the project scope.
• Enterprise environmental factors – this wasn’t there before and covers things like infrastructure that might affect what systems you can install, marketplace conditions, staffing and culture.
• Organisational process assets – this was previously on the list so is not a change. It refers to items like historical information and lessons learned that could shape the scope, along with any internal relevant policies and procedures.

The objective of this process is to create the scope statement. You are trying to take the requirements from the previous process, prioritise and review them and make a final list of what you will actually be delivering as part of this process.

It is different from the Collect Requirements process because you may have collected requirements that you cannot deliver (or choose not to deliver) in this phase. The work that you are currently doing may not extend to all the requirements that were discussed and documented. You may have to prioritise what you can deliver.

It’s the final list of requirements, plus anything else that needs to be considered and included, that ends up as your scope statement.

Tools & Techniques

Not much has changed with tools and techniques. We have:

• Expert judgment
• Data analysis
• Decision making
• Interpersonal and team skills
• Product analysis.

Alternatives generation and facilitated workshops have dropped off the list. However, interpersonal and team skills is pretty broad and would cover running a workshop, or any kind of meeting.

Data analysis is also a broader technique than what was there before. Alternatives generation is one way of analysing data, but not the only the option. We’re seeing throughout this refresh that the terminology, tools and techniques have got broader to allow for more tailoring and personalising. I’m of the opinion that’s a good thing.

Outputs

There are no new or changed outputs to this process.

We still have the project scope statement and the project document updates.

The objective at the end of the process is to have a statement of scope. It should include what’s in scope, what’s specifically excluded from scope, and anything else you feel the need to document to ensure everyone is on the same page about what is going to be delivered.

Scope statements come in various formats, and while you’ll be able to find templates, and may even have one from your PMO, feel free to tweak and amend the document so it suits the needs of your project.

Aim for your scope statement to be really detailed, so that people can’t misinterpret what is going to be delivered. Think about what users, processes, tools, technologies, policies and so on are going to be impacted or changed as a result – and which ones won’t.

You can also include items for the scope of future phases (useful so they don’t get forgotten). However, these should be reviewed and revised at the point that the future phase is initiated, just in case the business has moved on and the scope items are no longer relevant.

Next time I’ll be looking at the fourth process in this Knowledge Area: Create WBS.

Pin for later reading: