Cracking the Microsoft project 2010 WBS code
Probably the most important aspects of planning to get right at the very beginning is to understand precisely what the project scope is. Scope has been defined as ‘what is included within the project and what is not to be included – with the focus on the boundaries’.
There are two aspects of project scope: the scope of the project plan and the scope of the project deliverables or products. I want to focus on the latter in this short Microsoft project 2010 article.
Work breakdown structure (WBS)
Codes can be generated automatically with Microsoft project 2010 to create what it calls a ‘project outline’.
Much the same way that the book is split into chapters, with each chapter consisting of several major topics, and each topic being split in two and a set of paragraphs and sentences, then a project will also needs to be broken down into sub-tasks.
As an example, a project may be split into management stages or phases, and each of these split into possibly work packages or products/tasks. Within these, projects may be outlined by of resources, or by a group, or by organization, or by types of products.
There were no right or wrong answers here, but one is important is that during planning, and agreement is made of the best way to outline the project.
There are various ways to represent a WBS structure and code. During the planning workshop for example, Post-It notes may be used to create an outline much like this:
Using Microsoft project 2010, the best way to produce a the work breakdown structure ready for entry, is to first consider the benefits/objectives/outcome of the project, and from there determine the end project deliverable or product.
Thinking through the acceptance criteria for the end project product will help identify the products and hence tasks that will form part of the project.
The vital question to ask that will help ensure that a realistic and complete work breakdown structure (WBS) is generated is:
‘What is the project SCOPE in terms of time, cost, resources, deliverables,
quality expectations, outcomes, operational areas/customers, and benefits?’
Outdent and indent.
This is a Microsoft project 2010 function that allows you to move tasks to either a higher or lower level within your outline. Outdenting moves a task up a level in the outline, and Indenting moves the task down a level in the outline.
To outdent or indent a task in Microsoft project 2010, perform these steps:
- Click on a task that you wish to represent a summary bar. If such a task is not yet exist, then use the command ‘summary task’ within the task tab of the ribbon.
- Select those tasks that you wish to be indented below the summary bar, and use the green indent task button within the schedule group of the task tab.
- Note that the summary task bar has now changed to the black summary bar shape.
Follow the above three steps for each work breakdown structure (WBS) level.
The outlined detail can be shown/hidden by using the + or – button to the left of the task name.
[thrive_link color=’orange’ link=’https://www.projex.com/courses/microsoft-project/’ target=’_self’ size=’medium’ align=’aligncenter’]Microsoft Project Masterclass[/thrive_link]
