Work to keep an overview of the project.Work

Work break down structure is hierarchical and incremental decomposition of project into phase, deliverable and work package. But the team to be accomplish the project objectives and create the require deliverables.(Work Breakdown Structure (WBS) is a process of dividing complex projects to simpler and manageable)The WBS is an important tool which helps to keep an overview of the project.Work break down structure –Defines tasks and assign resources to those tasks.It forms the basis of organization and coordination in a project.WBS element is nothing but a bucket where all the activities belonging to that particular part of the project are captured.Benefit of work break down structurei) Simplifying the project execution.ii) Define the total scope of the projectiii) Accurate and readable project organizationiv) Help to estimate the cost, time, and risk.WBS in projects is to help with resource allocation, assigning responsibilities, monitoring the project, and controlling the project. It allows you double check all the deliverables specifics with the stakeholders and make sure there is nothing missing or overlappingRule or tips to create WBS are as belowRule1: Create WBS with your team not alone as you want their complete involvement and understanding. Involve your team at the planning stage of the project. Build the WBS interactively by first defining what deliverables need to be created. You will have a more complete WBS and a team that understand what they need to do.Rule 2: WBS should have at least 3 levels-highest level is the project itself.For medium to large projects you might have several levels more depending upon both the complexity and size of the components.Rule3: Don’t confuse WBS work package to a task.WBS is a work component that will be decomposed into task .this is also a pitfall that awaits many project managers. For example the “registration page” is a WBS item-but not “writes bad password lockout logic”. The latter is a task and should not look at tasks while creating WBS.Rule 4: Naming convention: Name a WBS item as a noun (not a verb).This makes it very easy to identify WBS items and tasks on the project schedule in the future.Rule5: The WBS lists your work breakdown, and the task list is the breakdown of the WBS work package into actions. Task belong to the project schedule- don’t do task breakdown while doing WBS. Schedule comes AFTER the wbs.Rule 6: The 100% Rule.Each lower level of decomposition must represent all of the work the higher-level element; conversely, all higher-level scope must be reflected in one of the lower-level elements. This is call the 100% rule, which ensures that all of the scope has been captured and that nothing unnecessary is included.Rule7: Your WBS is almost never complete or right in the first iteration. The more you learn about your project-the more will alter your WBS. This is absolutely great-and you should be prepared for this.Rule 8: Tasks have to be small enough to be assigned to individual resources-NOT the WBS. You should decompose WBS items only enough that they make logical sense as a component and not more than that.Rule 9: The lowest level of WBS-the work package will be represented by summary task on your project plan. Each of your WBS work packages should become a summary task. Summary task are collections of logically grouped tasks.Rule10: The 8/80 Rule.When should project stop? Answer of this question given by thumb rule: the 8/80 rule says that ‘all work packages should be greater than 8 hours and lesser than 80 hours’. This should give you a fair indication of when you can stop working on the WBS.On the basis of above rule I made WBS for the project Wedding party is below.