WBS:Â Deliverables or a â€śTo Doâ€ť List?
The work breakdown structureÂ WBS Â provides the foundation on which a project manager works.Â The PM uses the WBS to control the project and the team. The WBS also provides the checkpoints against which the PM and the organization measure progress (What is the WBS).Â In the project management world, there are two ways to do the work breakdown structure. The first way is to think of the WBS and develop the WBS as if it were a â€śTo Doâ€ť list.Â Just like the kind of list youâ€™d make up before going to the grocery store or running your errands. Now, there is nothing wrong with to do lists. I make them up for myself all the time. The problem with to do lists comes when we give one to somebody else.Â Hereâ€™s an example. If my to do list for workday includes an entry like â€śFix XYZâ€™s program scheduleâ€ť thatâ€™s a fine reminder for me because Iâ€™ve been thinking about what that client wants to do and the political ramifications of changing the program scope and what executives have different positions about that scope. The short little reminder â€śfix XYZâ€™s program scheduleâ€ť is fine for me because Iâ€™ve been thinking about it for days, talked to the client and thought about it some more. If I were to give that to do assignment to another of our consultants they would have absolutely no idea what that meant. They might have to spend days acquainting themselves with that client company and the new strategic program they are starting. That to do would be a terrible assignment for me to give someone. Iâ€™m creating no performance expectation nor telling them what a good job is or how I will evaluate their work.Â Clearly, project managers ought to limit their use of to do lists to personal reminders. For something like a project, which may affect your professional career and the success of your organization, we need a better tool. (WBS Clear Performance Expectations)
Letâ€™s fashion a good WBS entry
Now letâ€™s take that same assignment and make it work as part of a professionally done work breakdown structure. It has to meet a number of criteria to be included in our work breakdown structure.
- It has to tell he person doing the work what a good job is before they start, creating a clear performance expectation.
- It has to be unambiguously measurable. We donâ€™t want to have to have a meeting to decide whether we are done. Executives need hard-edged measures of project progress, which are not open to interpretation or word games.
Those two criteria sound simple. Nevertheless, it is not easy to produce them.Â In fact, itâ€™s one of the most difficult parts of the project management art. We need to decide exactly what we want is an end result from the assignment and then convert that end result into a metric. Letâ€™s try it with the assignment for the XYZ program schedule we discussed earlier. (What Size WBS)
First, I would go through the process of identifying what I want our consultant to give me when he or she completed this assignment to â€śfix the XYZ schedule.â€ť Going back over my conversations with the client, I could identify a number of characteristics that they want to see in the schedule. They want the project to be finished in less than 250 days. They want to avoid using outside contractors. They want to spend less than $325,000 on the project.
Therefore, I might use those metrics to tell our consultant I will that I want to schedule that completes and 250 days or less, doesnâ€™t use outside contractors and has a budget of less than $325,000. Those of the success criteria for the assignment and thatâ€™s the deliverable I would define for the team member. Obviously, I had to make up my mind about exactly what I wanted. A really awful assignment would have been to tell the team member I want to schedule revised to be shorter, cheaper and not use any outside consultants. What are my odds of getting what I want? They are very poor because the consultant he has to guess what I mean by faster, cheaper and no outside consultants.Â I donâ€™t know whether this result is actually achievable. I would need to sit down with the staff member who I was giving the assignment, look at the current schedule, and give that team member a chance to think about whether the result is achievable. Then they need to think about how long it will take them to achieve the result. We would discuss the approach and the budget for doing the work and then I have a good entry for my work breakdown structure. (WBS Best Practices)
Is this too much work breakdown structure?
You may be saying to yourself, â€śit is going to take me a lot of time to decide exactly what I want and how Iâ€™m going to measure it for every task in the work breakdown structure.â€ť You are right, it does take more time than a to do list. However, remember how important the work breakdown structure is to your project success. The WBS or work breakdown structure is the centerpiece of every project. You use the tasks in the WBS as the foundation for estimating work, cost and duration. The WBS gives team members clear project assignments, allows everyone to track progress on their tasks and it allows you to identify problems. As the project team executes the plan, we compare their actual results to the estimates for each WBS task. That lets us quickly identify variances and design corrective action.
Unfortunately, too many project managers donâ€™t recognize the importance of the WBS. They think they can just make a list of all the tasks in the project and then start work. That approach yields projects that take longer than they should. It also produces project that are late because we have not identified all deliverables in the initial planning. To develop a strong WBS, you begin by defining the scope and major deliverables. Then you break them down in to tasks to create your WBS.
How big should the WBS Be?
Project managers often ask, â€śHow many tasks should this project have?â€ť or, â€śHow much detail should I have in the WBS?â€ť The mistake PMs often make is to list â€śto doâ€™s,â€ť often hundreds of them. They start by listing the first thing they can think of to do and stop when they canâ€™t think of anything else.Â They may list tasks that will take as little as an hour to complete.Â The driving force behind this minutia is the fear of forgetting something. (How many tasks in WBS)
Itâ€™s easy for a PM to think that a projectâ€™s WBS should detail everything; everyone should do on the project. PMs mistakenly think that will protect them from people forgetting or skipping an item because they are lazy, stupid or sloppy. It also frees the PM from relying on the thinking or creativity of the team members. They can just put their heads down and follow the â€śto doâ€ť list. The PM has â€śthought of everythingâ€ť and done all the thinking for them.
The WBS â€śTo Doâ€ť List
This â€śto doâ€ť list approach may work for projects with one or two people, but it falls apart when the project gets any bigger. The flaws come from a misunderstanding of:
- How to exercise tight control on a project
- How to spot and solve problems early
- The pros and cons of micro-management.
What is Tight Control of a Project?
Is tight control having no problems?Â Hardly. That happens only in project fantasyland. Tight control requires that you:
- Can identify problems early and fix them quickly and inexpensively
- That every project team member knows what he or she is accountable for delivering.
Acceptance criteria tell team members what they are accountable for delivering. This is quite different from what they have to do. As an example, a â€śto doâ€ť list might tell a team member to â€śclean up the file room.â€ť That task is open to many different interpretations. It doesnâ€™t define your performance expectation for the team member.Â Itâ€™s a very ineffective checkpoint against which to measure their progress.
The deliverable of â€śâ€ś98% of the files are on the shelves in alphabetical orderâ€ť creates a crystal clear expectation for the team member. It also provides the acceptance criteria and an objectively measurable checkpoint for progress. When you assign that deliverable, you have better control because the team member knows what is â€śgood enoughâ€ť and doesnâ€™t have to guess.Â Then you combine deliverable-based WBS with work estimates to create a superior tool for control and tracking. When you canâ€™t exercise tight control, you must check everyoneâ€™s work frequently and make all the decisions. Thatâ€™s micromanagement.
Pros & Cons of WBS Micromanagement
Micromanagement is right for brand new employees who need to learn their jobs. Itâ€™s also necessary for known slackers or nincompoops on the team. Nevertheless, few project teams are composed entirely of people who need all the decisions made for them.Â This management style discourages problem solving or ownership of results.Â It makes team members dependent on you when you donâ€™t allow them independent decision-making. Worst of all, it creates team members who have no accountability for their results. All they have to do is follow the â€śto doâ€ť list of activities.
Most of your project team members wonâ€™t thrive under micromanagement.Â Micromanagement stifles people who want independence and are willing to be accountable for their work. They are the best performers and you need to encourage their best work.
Micromanagement doesnâ€™t work on projects that need complex judgments and creative thinking.Â On these projects, much of the work is cerebral. Therefore, itâ€™s impossible for you to specify everything they must do.Â More importantly, itâ€™s stupid to try. Letâ€™s say you have an experienced engineer performing a task like â€śdesign the payment input screen (GUI) for the billing system.â€ťÂ That relatively small task will require:
- Meeting with users to gather information about requirements
- Listing all the required information for the GUI
- Thinking about how to arrange the data elements on the screen for data entry efficiency
- Writing a layout document for the screen
- Meeting with users to get approval of the rough design.
You could list all those activities and more in the WBS. But what if the engineer comes up with a great idea?Â Do you want the engineer to ignore it and follow the WBS to doâ€ť list? Of course not. You want the engineer to figure out the best way to do the design. So instead of the activities in the â€śto doâ€ť list,Â you might assign deliverables like:
- User management signs off on the GUI design and acceptance criteria
- User management signs off that the GUI meets the acceptance criteria.
You let the engineer estimate how long those two deliverables will take.Â Youâ€™ll get a status report each week so you know how the work is progressing. Best of all, you designed an assignment that motivates the engineer to do his best work. (Create WBS with Team Members)
Maintaining the â€śTo Doâ€ť List WBS
Remember how small the second WBS was for the engineer compared with the To Do list?Â That is typical. The â€śto doâ€ť list approach to yields large and detailed work breakdowns that require lots of maintenance. Every time one of the micro-tasks changes, you need to update the WBS. That can require entering dozens of changes each week. If each team member is reporting on 5 â€“ 15 tasks per week, youâ€™ll have a lot of data entry (even if you have clerical support to input all the status data).
The inevitable result is that tracking falls behind and so does updating the schedule.Â There are simply not enough hours to complete these tasks.Â Within a few weeks, youâ€™ll stop updating the schedule because it takes too much time. This may sound like a stupid and improbable reaction but we see it frequently, even on large and important projects. The justification for stopping is, â€śNo one is looking at all that detail anyway, so why should I spend the time to update it?â€ť
A Deliverables WBS Works Best
Professionals who manage projects for a living and use the best practices in project management, agree the WBS should be composed of deliverables (end results), not â€śto doâ€™s.â€ť Assigning accountability for deliverables to team members yields a smaller WBS, easier reporting of progress (actuals) and less work to keep the schedule current.Â You also get team membersâ€™ ownership of the results when they are accountable for producing deliverables. Â (Pre-launch Review of a WBS )
Your work breakdown structure (WBS) is your design for making assignments, holding people accountable and monitoring process. Done properly, your schedule will be easy to keep current and your team members will be responsible for their deliverables.
You can learn to do a WBS properly as part of our basic and advanced project management courses. Youâ€™ll learn how to break down the scope into deliverables for which you will hold people accountable.