0100,0100,0100Afternoon All, The work breakdown structure is a method of structuring work scope. It is the first activity that is undertaken when dealing with projects and breaks the project into manageable sections. For this assignment you are required to examine the whole project and provide a WBS to three levels for the whole project and selecting one area only provide a 4th level. The way you break the project down is up to you and it must make sense. Attached are the notes on WBS and they are repoduced here I can not get onto eeserver so this information is also in the U drive of the NT's under EPM444 leftHIERARCHICAL METHODS leftThese methods attempt to successively refine the definition of scope. They are the most common method of scope organisation. leftThese methods are useful in providing scope checklists and allow for detail to grow with the project. leftOther requirements for these systems include: outManageable where specific authority and responsibility can be assigned outIndependent or with minimal interfacing with other elements outcan be integrated to give an overall picture outMeasurable in terms of progress. leftThey however can create divisions in organisations as to the split of work responsibilities. Care should be used in designing these systems to ensure interface points are defined and agreed. leftThese structures can also grow in size at a rapid rate leading the generation of "clerical monsters". leftTYPICAL STRUCTURES leftStructures vary from one organisation to another and one project to another. A hierarchical structure may comprise: Level Description  1 Total Program  2 Project  3 Task  4 Subtask  5 Work Package  6 Level of Effort  leftThe upper three levels are usually specified by the client. Level 1 is usually used for authorisation and release of all work, budgets are prepared at level 2, schedules at level 3. leftThe top 3 levels represent integrated efforts and should not be applied to a department. leftThe summation of all elements in one level must be the sum of all work on the next lowest level. Each element of work should only be assigned to one and only one level of effort. leftIn setting up a system, the following should be considered: outThe technical and complexity requirements of the program outThe program cost. outThe time span of the program. outThe executor's resource requirements. outCustomer and contractor internal management control and reporting structures. outNumber of organisations involved in the project. Chris Croft email: ccroft@ee.uwa.edu.au phone: +61 8 9380 3097 fax: +61 8 9380 1065 Dept. of Electrical & Electronic Engineering The University of Western Australia NEDLANDS WA 6907 Western Australia