Some Additional Remarks Concerning the Subject Scope
- Breakdown Structure is the result of a decomposition concerning a domain. There exist more than one breakdown structures (comp. CROSSWIND7, page 176):
- Organizational Breakdown Structure (Organigram)
- Risk Breakdown Structure (Risk and Subrisk Description)
- Resource Breakdown Structure (Team- and Subteam Analysis)
- Bill of Materials (List of components and subparts)
- Work Breakdown Structure (List of tasks and subtasks)
- Delphi (Opinion) Technique is a method to get the same valid expressions from multiple experts by trying to find a concensus. You may think of it as an iteration of exchange opinions.
- Management by Objectives is a method to integrate and or relate a special project (in)to the sense and target of a set of multiple projects
- Product Scope is the set of features of those deliverables, which have to be generated by the project
- Project Scope is the work that must be done to generate the product scope
- Project Scope Statement is that set of descriptions, which determines the scope of the project. Therefore, it's allowed to use negative expression to exclude some aspects.
- Scope Creep is an uncontrolled change of the scope: the project owners and their related stakeholders often want to expand the scope ("get more for the same money"), the suppliers want to reduce the scope ("get the same money for less work") and the developers want to "over-accomplish" their task, "because it would be a good thing", also known as 'gold plating'
- Work Package is a unit on the lowest level of the WBS. Work packages are decomposed by the process activity definition.
