O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
you need to gather all relevant information. First This includes a statement of work, task analysis, schedule of deliverables,milestones, project scope statement, problem analysis,design documentation or other relevantdocumentation.
Welcome to Practicum UniversityWe will take you through the process ofdeveloping a Work Breakdown Structure for anew program in Dog Whispering that we arecreating this year.
The team at PU has gathered all of theirdocumentation and the leadership team isnow ready to start working on a plan todevelop the program.
There are many tools you can use to create the WBS likemind-mapping tools, Powerpoint or Word. We will use theindustry standard diagramming software, Microsoft Visiowith the WBS Modeler Add-in.
Start with the first level that represents the whole project. This should be numbered 1.0.
The second level will vary depending on whether the WBS isProduct-based or Process-based.
A Product-based WBS is broken down into a series of deliverablesin the second level. These deliverables should capture 100% ofthe project scope.
A Process-based WBS is broken down into a series of phases inthe second level. Each phase may or may not have a deliverable,but all major project phases should be included.
An example of a process-based WBS might be to use the stagesof ADDIE as the 5 major phases of the second level.
For the purposes of our example we will use a product-basedWBS. Development of the new program can be broken down intothese stages: Needs Analysis, Curriculum Proposal, CourseDevelopment Plan, Accreditation Package, Implementation, andEvaluation Plan.
At this point we enter a stage of the processcalled decomposition to further break the workdown in to smaller and more manageablechunks of work, called Work Packages.
A general rule that you might want to use iscalled the 8/80 rule. No work package shouldbe less than 8 hours of work, or more than 80hours of work.
The process of decomposition can be done by an individual, or bythe whole team. It all depends on what makes sense for yourproject. Still, two minds are usually better than one!
But you dont necessarily need to reinvent the wheel!
If youve already completed a similar project, you may alreadyhave a template you can follow for decomposition. Perhaps PUhas already followed this process for other programs.
It is critical that you and your team try to account for every taskthat is necessary to complete the project. Mistakes here will onlycost the project more time and perhaps more money later.
Once the WBS has been completed it might be necessary to build a WBS Dic:onary. The WBS Dic:onary is a document that describes each work package in detail.
Here is the completed WBS for PUs Dog Whispering program.
Now that youve broken the project down into manageablechunks of work, you can more easily estimate time, cost andstaffing for the project. By estimating the amount of time eachwork package "should" take, as well as the role assigned to thattask, you can estimate the cost of that task.
You can develop a table that shows each of these fields insequence, but theres another way to visualize this information.The Gantt Chart.
The power of the Gantt Chart is that it is a simple and clear wayto not only show the length of time of each task, but alsovisualize task dependencies.
A Task Dependency is the rela:onship in which a task relies on Task #1 the comple:on (or par:al comple:on) of another task or tasks before it can begin. Task #2 Task #3
Task dependenciesdetermine the totallength of time for eachstage in the project, Task #1 and thus the overalltimeline of the project. Therefore, the GanttChart is a tool thatcan help us determine Task #2 the overall timeline fora project. Task #3
There are manydifferent programs thatcan help you create aGantt Chart includingone of the most widelyused tools for projectplanning andmanagement,Microsoft Project.
Here is a Gantt Chart produced in Microsoft Project for the DogWhisperer program at PU.
To build a project you must start with the founda:on.
1 1.1 1.2 1.3 1.1.1 1.2.1 1.3.1 188.8.131.52 1.1.2 1.3.2 1.2.2The foundation of a project is the Work Breakdown Structure.
The Work Breakdown Structure will help you to define theprojects scope, estimate time, cost and staffing, makedelegation of tasks simpler and identify risks.
The process starts by gathering all the necessary informa:on and your key team members. The more heads, the beHer!
The first two levels of a WBS must encompass 100% of theproject process.
Use the process of decomposition to break the project down tomanageable chunks using the 8/80 rule.
Clarify each work package by creating a WBS Dictionary.
Organize the tasks into a GanH Chart to highlight dependencies and determine the overall :meline.