Work breakdown structure for project management

From apppm
Revision as of 00:56, 15 February 2021 by S162685 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Summary / abstract: A brief summary of the key points of your article

Big idea: describe the tool, concept or theory and explain its purpose. The section should reflect the current state of the art on the topic

Application: provide guidance on how to use the tool, concept or theory and when it is applicable

Limitations: critically reflect on the tool/concept/theory and its application context. What can it do, what can it not do? Under what circumstances should it be used, and when not? How does it compare to the “status quo” of the standards – is it part of it, or does it extent them? Discuss your article in the context of key readings / resources provided in class. Substantiate your claims with literature

Annotated bibliography: Provide key references (3-10), where a reader can find additional information on the subject. The article MUST make appropriate references to the and reference material provided in class – either incorporating it as a source, or critically discussing aspects that are missing from it but covered by this article. Summarize and outline the relevance of each reference to the topic (around 100 words per reference). The bibliography is not counted in the suggested 3000 word target length of the article.

Abstract:

Work breakdown structure, as the wording suggests, refers to the tool utilised to breaking larger work into smaller tasks. This is a common productivity technique related to project management, seeking to make the work and complexity af the task more manageable and approachable. It is defined by The Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK) as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.”. The work breakdown structure is seen as one of the most vital tools to utilise the work breakdown technique as well as project management document. It integrates both scope, cost and schedule baseline for the project, ensuring that these are in line with the project plan.

In general it is possible to distingue between three types of work breakdown structures: 1) Deliverable-based work break down structure Deliverable-based work breakdown structures is the most common and preferred approach, and mostly the initial phase of defining the how to assess succes in project progress is the key difference between the two.

Deliverable based work breakdown structure is .....


2) phase-based work break down structure

Phase based work break down structure is.... Stage gate model .....

3) Responsibility based structure Resposib


‘’'Creating a Work breakdown structure‘’’

When creating a work break down structure.....

Know your project scope.....

Identify Key Deliverables.....

Determine Work Packages.....

Use the Right Format.....


Use of the Work Breakdown structure: The work breakdown structure serves to cater many project management disciplines. . Initially, it serves as a planning tool to help the project team plan, define and organize scope with deliverables. The Work breakdown own structure is usually also used as the primary source of schedule and cost estimate activities. Moreover, it is used as a description of all the work related to a project and a tool for monitoring and controlling these, which serves as its biggest contribution to project managers.

Work packages .......



Bibliography: https://www.workbreakdownstructure.com https://blog.taskque.com/work-breakdown-structure/ The Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK)

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox