Work Break-down Structure

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
  
 
This article will contain the following contents
 
This article will contain the following contents
#basic content
+
Basic content
  
 
• rule of task decomposition
 
• rule of task decomposition
Line 13: Line 13:
 
• decomposition scheme
 
• decomposition scheme
  
• What should the scope of procedures include?
 
 
• How large should the sample sizes be?
 
 
• Who should execute the procedures?
 
 
• How often should the procedures be performed?
 
 
• What should the reporting of results consist of?
 
 
• How can we work efficiently with the borrower <ref name="four">https://www.protiviti.com/UK-en/risk-and-compliance/portfolio-and-lender-due-diligence</ref>?
 
  
 
#key benefits and potential disadvantage
 
#key benefits and potential disadvantage
 
#Application on a real study case
 
#Application on a real study case

Revision as of 05:30, 14 February 2021

Abstract

Work breakdown structure (WBS) is a principle of project management that arranges project elements based on the deliverables instead of a schedule activity. which summarizes and defines the whole scope of work of the project, and each descending level represents a more detailed definition of the project work. WBS is always at the center of the planning process, and it is also an important basis for making progress plans, resource requirements, cost budgets, risk management plans, and procurement plans. WBS is also an important basis for controlling project changes. The key process for building a WBS is to disintegrate the assignments into an amount of light workload and distribute it to every individual who is considered as a participant.

This article will contain the following contents Basic content

• rule of task decomposition

• building requirements

• decomposition scheme


  1. key benefits and potential disadvantage
  2. Application on a real study case
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox