Professional Documents
Culture Documents
Comsats Institute of Information Technology Lahore
Comsats Institute of Information Technology Lahore
Comsats Institute of Information Technology Lahore
Sub!itted to:
Sir S M # $id
Sub!itted b%:
6work breakdown structure6 was not used, this first implementation of -.,# did organize the tasks into product+oriented categories !y 7une 2389, 0o0, 1A"A and the aerospace industry published a document for the -.,#:;<"# system which described the !" approach. #his guide was endorsed by the "ecretary of 0efense for adoption by all services. 'n 238=, the 0o0 issued 6 ork !reakdown "tructures for 0efense >ateriel 'tems6 (>'?+"#0+==2), a military standard re$uiring the use of work breakdown structures across the 0o0.#his standard established top+level templates for common defense material items along with associated descriptions ( !" dictionary) for their elements. W$en to u4e it: A work breakdown structure is an essential element in project planning and project management. 'n the $uality planning process, !" begins with a generalized goal and then identifies progressively finer levels of actions needed to accomplish the goal. 'n the $uality improvement process, the tool is especially useful for creating an implementation plan to remedy identified process problems. *or !" to accurately reflect the project, however, it is essential that the team using it have detailed understanding of the tasks re$uired. 'o1 to u4e it: Identi&% t$e pri! r% re2uire!ent or objecti9e. #his should be a clear item, based on customer re$uirements, to which the entire team agrees. rite this re$uirement at the top of the chart. Subdi9ide t$e re2uire!ent 4t te!ent into ! jor 4econd r% c te"orie4. #hese branches should represent re$uirements, products, or activities that directly lead to the primary objective or that are directly re$uired to fulfill the overall re$uirement. #he team should continually ask, ( hat is re$uired to meet this condition@), ( hat happens ne&t@), and ( hat needs to be addressed@) rite the secondary categories below the primary re$uirement statement. /sing sticky notes at this stage makes later changes easier to accomplish. Bre 8 e c$ ! jor $e din" into "re ter det i3. As you move from top to bottom in the !", products and activities should become more and more specific. "top the breakdown when each task is tiny enough to be easily completed and evaluated for accuracy. 'f the team does not have enough knowledge to continue at some point, identify the individuals who can supply the information and continue the breakdown later with those individuals present. Re9ie1 t$e WBS &or 3o"ic nd co!p3etene44. >ake sure that each subheading and path has a direct cause+and+effect relationship with the one before. .&amine the paths to ensure that no obvious products or actions have been left out. Also ensure that the development of listed products or completion of listed actions will indeed lead to the anticipated results.
'n )i"ure
?arge, comple& projects are organized and comprehended by breaking them into progressively smaller pieces until they are a collection of defined 6work packages6 that may include a number of tasks. #otal e&penses ," 39A,AAA project is simply a lot of projects joined together. #he ork !reakdown "tructure ( !") is used to provide the framework for organizing and managing the work. 'n planning a project, it is normal to find oneself momentarily overwhelmed and confused, when one begins to grasp the details and scope of even a modest size project. #his results from one person trying to understand the details of work that will be performed by a number of people over a period of time. #he way to get beyond being overwhelmed and confused is to to break the project into pieces, organize the pieces in a logical way using a !", and then get help from the rest of your project team. #he psychologists say our brains can normally comprehend around 5+3 items simultaneously. A project with thousands or even dozens of tasks goes way over our ability to grasp all at once. #he solution is to divide and con$uer. #he !" helps break thousands of tasks into chunks that we can understand and assimilate. -reparing and understanding a !" for your project is a big step towards managing and mastering its inherent comple&ity. #he !" is commonly used at the beginning of a project for defining project scope, organizing Bantt schedules and estimating costs. 't lives on, throughout the project, in the project schedule and often is the main path for reporting project costs. <n larger projects, the !" may be used throughout the project to identify and track work packages, to organize data for .arned Calue >anagement (.C>) reporting, for tracking deliverables, etc. 'n planning and supervision phase we do planning .budgeting and coordinating. *or this estimated cost is -D, 4AAAA.and time re$uire for this is 9 days.
'n guest listing phase of project estimated cost is for printing card and making phone call for honorable guests will be -D, 4AAAA and re$uired time is 2 day. 'n speaker invitation phase of project we needed contact with speaker and speaker invitation cost will be -D, 9AAAA and will complete in one day ,oom and e$uipment that re$uire booking of room and decorating of rooms .#he estimated cost is -D, 4AA,AAA and will complete in threedays. <ur menu cost will be -D, 9AA,AAA and it takes one day for preparation the menu list for honorable speakers. *or staffing it takes -D, 2AAAAA and it takes one day for planning.