1 / 23

Work Breakdown StructureS

Work Breakdown StructureS. Elisati Hulu . Definition. “ a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.

patsy
Download Presentation

Work Breakdown StructureS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Work Breakdown StructureS Elisati Hulu

  2. Definition • “a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. • It organizes and defines the total scope of the project. • Each descending level represents an increasingly detailed definition of the project work. • The WBS is decomposed into work packages.’’

  3. Characteristics (1) • Is deliverable-oriented • Is hierarchical and constructed in such manner that • each level of decomposition includes 100% of the work of its parent element, and • each parent element has at least two child elements • Defines the full scope of the project and includes all project related work elements including all internal,external and interim deliverable • Includes only those elements to be delivered by the project • Uses nouns and adjectives to describe the deliverables, not verbs • Employs a coding scheme that clearly depicts the hierarchical nature of the project • Contains at least two levels of decomposition • Is created by those performing the work with technical input from knowledgeable subject matter experts and other project stakeholderss

  4. Characteristics (2) • Includes Project or Program Management at level 2 of the hierarchy • Includes WBS Dictionary that describes and defines the boundaries of the WBS elements • Contains work packages that clearly support the identification of the tasks, activities and milestones that must be performed in order to deliver the work package • Communicates the project scope to all stakeholders • Is updated in accordance with project change management procedures

  5. Examples:

  6. Examples: Simple WBS

  7. Examples: Larger WBS

  8. WBS Decomposition • The logic of WBS decomposition is also something that varies from project to project. • The most common forms of WBS decomposition are breakdowns by the following: • Function • Role • Method • Deliverables (components)

  9. WBS representation

  10. tabular

  11. The steps in creating a typical WBS are: • Define the project’s end product. • This is usually no more than a title: “House at Avenue Drive” for example.  • It forms the root of the Work Breakdown Structure document. • Define the main deliverables. • These are the main components of the project’s end product, for example, for a house, External construction, Internal construction, and so on. • These become sections or ‘main branches’ under the root, defined in the previous step.

  12. The steps in creating a typical WBS are (2) • Break down the main deliverables into their sub-components using as many sub-branches as needed until you have manageable ‘units of work’ which do not need to be subdivided further. • These units of work should be of a size that the project manager can easily handle. • For example, something that a worker or a team of workers can accomplish in a week might represent a unit of work. • Too much subdivision is counter productive as the project manager will then have to get too involved in the project details. Finally you should have a structure with the root at one end and, furthest from the root, units of work. Taken together, the units of work make up the total work in the project, and there should be no overlap between them. 

  13. Division of work in the WBS: the 100% rule

  14. Entering costs to the WBS

  15. ADV for ATM Software

  16. Essential requirements • E1 Financial transactions shall be authorized by an ATM card and a password • E2 Financial transactions shall be terminated if a customer fails to enter the correct password « settable » times • E3 Financial transaction shall allow quick cash withdrawals • E4 Financial transaction shall provide a printed receipt for each transaction • E5 The ATM shall retain the information listed in the requirements specifi cation, section 3.2.1, for each customer transaction • E6 Financial transaction shall process Terminate requests from customers

  17. Desirable requirements • D1 Financial transaction should accommodate balance inquiry transactions • D2 Financial transaction should accommodate standard withdrawal transactions • D3 Financial transaction should accommodate deposit transactions • D4 Customers should be allowed to conduct multiple transactions per session

  18. Optional requirements • O1 Financial transaction could support debit card transactions • O2 Financial transaction could support payment of utility bills • O3 Financial transaction could allow customers to purchase postage stamps which will be disbursed by the ATM hardware

More Related