GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Mindmap

Project Scope Management

GABRIELA BERMUDO Englisch

Inhalt der Mindmap

Project Scope Management

  1. includes the processes required to ensure that the project includes all the work required, and only the work required.

    • Product scope
      • Are the features and functions that characterize a product, service, or result.
    • Project scope
      • The work performed to deliver a product, service, or result with the specified features and functions
  2. 5.1 Plan Scope management

    • Are documents how the project scope will be defined, validated, and controlled.
    • Inputs
      • Scope Management Plan
        • is a component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and verified
      • Requeriment Management Plan
        • Are based on that relationship
    • Tools and techiques
      • Expert Judgment
        • Include the project manager, the project sponsor, selected project team members, selected stakeholders, anyone with responsibility for any of the scope management processes, and others as needed
      • Meeting
        • refers to input received from knowledgeable and experienced partie
    • Outputs
      • Project Management Plan
        • subsidiary plans of the project management plan are used to create the scope management plan
      • Project Charter
        • It provides the high-level project description and product characteristics from the project statement of work.
      • Enterprise Environmental Factor
        • Include
          • Organization’s culture
          • Infrastructure
          • Personnel administratio
          • Marketplace conditions
      • Organizational Process Assets
        • Historical information and lessons learned knowledge base
        • Policies and procedure
  3. 5.2 Collet Requirements

    • The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
    • Outputs
      • Requirements documentation
      • Requirements traceability matrix
    • Inputs
      • Scope Management Plan
      • Requirements management plan
      • Stakeholder Management Plan
      • Project Charter
      • Stakeholder Register
    • Tools and Techniques
      • Interviews
      • Focus Group
      • Facilitated workshops
      • Group Creative Techniques
      • questionnaires and survey
      • Observations
      • Prototypes
      • Benchmarking
      • Context diagrams
      • Document analysis
  4. 5.3 Define Scope

    • process of developing a detailed description of the project and product
      • Inputs
        • Scope management plan
        • Requirements
        • Organizational process assets
        • Project charter
      • Tools and Techniques
        • Expert Judgment
        • Product analysis
        • Alternatives generation
        • Facilitated workshops
      • Outputs
        • Project scope statement
        • Project documents updates
  5. 5.4 Create WBS

    • process of subdividing project deliverables and project work into smaller, more manageable components.
      • Inputs
        • Scope management plan
        • Project scope statement
        • Requirements documentation
        • Enterprise environmental factors
        • Organizational process assets
      • Tools and Techniques
        • Descomposition
        • Expert judgment
      • Outputs
        • Scope Basseline
          • Project scope statement
            • includes the description of the project scope, major deliverables, assumptions, and constraints.
          • WBS
            • is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables
          • WBS dictionary
            • is a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS
        • Project documents updates
          • Approved change requests result from the Create WBS process, then the requirements documentation may need to be updated to include approved changes.
  6. 5.5 Validate scope

    • process of formalizing acceptance of the completed project deliverables.
    • Inputs
      • Project Management Plan
      • Requirements documentation
      • Requirements traceability matrix
      • Verified deliverables
      • Work performance data
    • Tools and Techniques
      • Group decision-making techniques
        • Are used to reach a conclusion when the validation is performed by the project team and other stakeholders.
      • Inspection
        • includes activities such as measuring, examining, and validating to determine whether work and deliverables meet requirements and product acceptance criteria
    • Outputs
      • Accepted deliverable
      • Change requests
      • Work performance information
      • Project documents updates
  7. 5.6 Control Scope

    • process of monitoring the status of the project and product scope and managing changes to the scope baseline
    • Inputs
      • Project management plan
      • Requirements documentation
      • Requirements traceability matrix
      • Work performance data
      • Organizational process assets
    • Tools and techniques
      • Variance Analysis
    • Outputs
      • Work Performance Information
      • Change Request
      • Project management plan updates
        • Scope Baseline updates
        • other Baseline updates
      • Project documents updates
      • Organizational process assets updates
        • Causes of variances
        • Corrective action chosen and the reason
        • Other types of lessons learned from project scope control.

Informationen

Beschreibung
Mindmap am Project Scope Management, erstellt von GABRIELA BERMUDO am 28/08/2017.
Erstellt von
GABRIELA BERMUDO
Aufrufe
0
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck