1 / 14

Work Breakdown Structure (WBS) Extended Table of contents

Work Breakdown Structure (WBS) Extended Table of contents. Introduction The project triangle. Product (result, features, quality). Resources. Time. Introduction The project triangle. Product (result, features, quality)  What: . Resources  Who. Time  When.

kimball
Télécharger la présentation

Work Breakdown Structure (WBS) Extended Table of contents

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 Structure (WBS) Extended Table of contents

  2. IntroductionThe project triangle Product (result, features, quality) Resources Time

  3. IntroductionThe project triangle Product (result, features, quality)What: Resources Who Time When

  4. The project triangleThe relation between product, time and resources Product Change in one part – will have consequences for other parts Time Resources

  5. Works Breakdown Structure is: • A method for organizing tasks for a project • Focuses on tasks and what needs to be done in a hierarchical way – top down (headlines not importance) • Most of the time - says nothing about time (sequence and time needed) • From distance the elephant doesn’t look that big – but when it comes closer • But bite the elephant into smaller pieces

  6. WBSWhy breaking the project into tasks? • Clear plan of the work-sequence towards completion of promised deliverables • Easier to manage -> plan, execute and control • Easier to decide what kind of skills/resources are needed + estimate resource (time, manpower and machinery) • Easier to communicate and understand Project planning and control

  7. WBS: Ground rules for WBS • Define the work as independent tasks that can be sequenced, assigned, scheduled and monitored • Define the tasks at a level of detail appropriate for the length and complexity of the project • Think parallel tasks, but be aware of dependencies, joint decision and completion points • Present the hierarchy of tasks in a easy understood format • Verify that the tasks cover the attainment of project goals and objectives Project planning and control

  8. IntroductionFrom structure into a plan • From distance the elephant doesn’t look that big – but when it comes closer !!! - ??? • ... bite the elephant into smaller pieces Project planning and control

  9. Work Breakdown Structure I • Stepwise or gradually planning process. • Structuring according to: • Physical/geographical location • Type of work • Functions • Systems • Organisational belonging

  10. Work Breakdown Structure II Use e.g. your function tree or mind –map to split your project tasks into even smaller tasks. Determine in which order you will solve the different tasks.

  11. Example of a WBS

  12. ExtendedTable of Contents • An Extended Table of contents is an Extended Table of contents • Table of contents known from reports and word! • ETOC is used for helping you discuss and structure your project – before you start writing on your project (probably not now) • Consist typically of: • Content • Arguments • Literature/method based upon • Number of pages / extent • Responsible

  13. ExtendedTable of Contents

  14. To the next time • Hand in preliminary project description – October 1rst (to your supervisor and upload to fronter) – • ALL 7 sections must be included (Planning tools next time) • Approximately 10 pages • Everyone from the group must “deliver” and participate in the work

More Related