The document discusses Work Breakdown Structure (WBS), which involves dividing large projects into smaller, more manageable tasks. A WBS breaks down a project's deliverables and work into hierarchical levels to facilitate planning, execution, and monitoring. It helps managers accurately assign responsibilities, allocate resources, monitor progress, and control projects. A good WBS defines work at a level of detail that is neither too small nor too large, with identifiable start and end dates.
The document discusses Work Breakdown Structure (WBS), which involves dividing large projects into smaller, more manageable tasks. A WBS breaks down a project's deliverables and work into hierarchical levels to facilitate planning, execution, and monitoring. It helps managers accurately assign responsibilities, allocate resources, monitor progress, and control projects. A good WBS defines work at a level of detail that is neither too small nor too large, with identifiable start and end dates.
The document discusses Work Breakdown Structure (WBS), which involves dividing large projects into smaller, more manageable tasks. A WBS breaks down a project's deliverables and work into hierarchical levels to facilitate planning, execution, and monitoring. It helps managers accurately assign responsibilities, allocate resources, monitor progress, and control projects. A good WBS defines work at a level of detail that is neither too small nor too large, with identifiable start and end dates.
BMEF15M019 Introduction Dividing complex projects to simpler and manageable tasks is the process identified as Work Breakdown Structure (WBS).
In WBS, much larger tasks are
broken-down to manageable chunks of work. These chunks can be easily supervised and estimated. example of outlined WBS. WBS helps manager ◦ Facilitates evaluation of cost, time, and technical performance of the organization on a project. ◦ Provides management with information appropriate to each organizational level. ◦ Helps in assiging project responsibilities to organizational units and individuals ◦ Helps manager plan, schedule, and budget. Purpose of WBS There are three reasons to use a WBS in your projects: It helps more accurately and specifically define and organize the scope of the total project. The second reason for using a WBS in your projects is to help with assigning responsibilities, resource allocation, monitoring the project, and controlling the project Finally, it allows you double check all the deliverables' specifics with the stakeholders and make sure there is nothing missing or overlapping. How to build a WBS Begin with the Charter, focusing on Objectives and Deliverables Break the main project down into sub- tasks. Set the structure to match how you’ll manage the project. Lowest level not too detailed, not too large Identify support activities Following are a few reasons for creating a WBS in a project Accurate assignment of responsibilities to the project team. Indicates the project milestones. Helps to estimate the cost, time, and risk. Illustrate the project scope, so the stakeholders can have a better understanding about the project. Goals For WBS Giving visibility to important work efforts.
Giving visibility to risky work efforts.
Illustrate the correlation between the
activities and deliverables(Product result deliverables). Elements of WBS Definable—can be described and easily understood by project participants. Manageable—a meaningful unit of work where specific responsibility and authority can be assigned to a responsible individual. Estimateable-- duration can be estimated in time required to complete, and cost can be estimated in resources required to complete. Measurable—can be used to measure progress; has start and completion dates and measurable interim milestones.
Integratable—integrates with other
project work elements and with higher level cost estimates and schedules to include the entire project. Thank you