GoConqr has a new look! Let us know what you think.

Flashcards

SCOPE MANAGMENT

kat atkins Project Management PMP English 38 cards

Cards in this deck (38)

  1. 1WHAT IS SCOPE MANAGEMENT*PROCESSES CONCERNED WITH THE WORK NEEDED TO MEET THE PROJECTS OBJECTIVES
  2. 2WHEN DOES SCOPE MANAGEMENT START?*IMMEDIATELY AFTER PROJECT IS INITIATED
    *CONTINUES UNTIL THE PROJECT IS CLOSED
  3. 3HOW MANY TIMES IS PROJECT SCOPE CONDUCTED?*PROCESS IS ITERATIVE- REVISED THOUGHT OUT LIFE OF PROJECT
    *PERFORMED SEVERAL TIMES IN MULTI-PHASED PROJECTS
  4. 4WHAT ARE THE PHASES OF SCOPE MANAGEMENT (6 EA)1. PLAN SCOPE MANAGEMENT (PLANNING)
    2. COLLECT REQUIREMENTS (PLANNING)
    3. DEFINE SCOPE (PLANNING)
    4. CREATE WBS (PLANNING)
    5. VALIDATE SCOPE (M&C)
    6. CONTROL SCOPE (M&C)
  5. 5WHAT IS PRODUCT SCOPE?*CHARACTERISTIC OF THE PROJECT'S FINAL PRODUCT, SERVICE OR RESULT
    *REQUIREMENT THAT RELATE TO THE PROUDCTION OF THE PROJECT
    *THE DESIRED END RESULTS
  6. 6WHAT DOES PRODUCT SCOPE DESCRIBE (6 EA)?*WHAT WILL IT DO
    *HOW IT WILL BE USED
    *HOW IT WILL FUNCTION
    *WHAT PRODUCT WILL LOOK LIKE, WHAT THE SERVICE IS, RESULT WILL BE
    *WHAT'S THE IMPACT TO STAKEHOLDERS/ORG/CUSTOMERS
    *DESCRIBE CONSTRAINTS, RESTRICTIONS, STANDARDS, REGULATION,ETC
  7. 7WHY SHOULD PRODUCT SCOPE BE "SHARED"?*WHEN EVERYONE UNDERSTAND IT, THE TEAM CAN GET BEHIND IT
    *MORE LIKELY TO COME UP WITH MORE EFFICIENT, INNOVATIVE AND RESILIENT PROJECT DECISIONS
  8. 8WHAT IS PROJECT SCOPE?*THE WORK THE PROJECT TEAM WILL PERFORM TO ACHIEVE ALL THE PROJECT'S OBJECTIVES
    *ENCOMPASSES PRODUCT SCOPE
    *INCLUDES PLANNING, COORDINATION, MANAGEMENT ACTIVITES
  9. 9WHY SHOULD THE PROJECT SCOPE BE DESCRIBED IN GREAT DETAIL?*IT WILL DRIVE THE ACTIVITIES THAT WILL OCCUR
    *REDUCES MISINTERPRETATIONS OF HOW AND IN WHAT STEPS THE DELIVERABLE WILL BE PRODUCED
    *REDUCES SCOPE CREEP
  10. 10HOW DOES PMBOK DESCRIBE SCOPE MANAGEMENT (6 EA)*PLAN: HOW YOU WILL PLAN, MANAGE, CONTROL SCOPE & REQUIREMENTS
    *DETERMINE REQUIREMENTS
    * STAKEHOLDERS NEEDS-SORT & BALANCE
    *CREATE WBS
    *OBTAIN CUSTOMER VALIDATION
    *MEASURE SCOPE PERFORMANCE & ADJUST AS NEEDED
  11. 11WHAT IS A REQUIREMENT?*CONSTITUENT NEEDS, OBJECTIVES, SPECIFICATION OF PROJECT DELIVERABLES
  12. 12WHAT IS THE PURPOSE OF PROJECT SCOPE PRE-PLANNING?*DETERMINE HOW REQUIREMENTS WILL BE COLLECTED, ORGANIZED, PRIORITIZED, TRACKED AND MEASURED
  13. 13WHERE ARE THE REQUIREMENTS COLLECTED?*REQUIREMENTS MANAGEMENT PLAN
  14. 14WHAT IS THE MAIN PURPOSED OF THE REQUIREMENTS MANAGEMENT PLAN?*ENSURE THAT NOTHING IS MISSED WHILE REQUIREMENTS ARE COLLECTED
    * REQUIREMENTS PROPERLY LINKED TO DELIVERABLE AND SCOPE
  15. 15WHAT SHOULD BE INCLUDED IN THE REQUIREMENTS MANAGEMENT PLAN (4 EA)?*KINDS OF INTERACTIONS W/ CUSTOMER AND STAKEHOLDERS TO COLLECT REQUIREMENT
    *CATEGORIZATION METHODS
    *DESCRIBE PRIORITIZATION, SCORING, APPROVAL METHODS
    *CONFIGURATION MANAGEMENT ACTIVITIES (CHANGE)
  16. 165.1 WHAT HAPPENS DURING "PLAN SCOPE MANAGEMENT"?* DETERMINES HOW SCOPE WILL BE PLANNED, EXECUTED & CONTROLLED
    *RESULTS IN CREATION OF SCOPE MANAGEMENT PLAN & REQUIREMENTS MANAGEMENT PLAN
  17. 17WHAT DOES THE SCOPE MANAGEMENT PLAN DEFINE (6 EA)?*HOW TO ACHIEVE SCOPE
    *WHAT TOOLS TO USE TO PLAN
    *HOW TO CREATE THE WBS
    *WHAT ENTERPRISE ENVIRONMENT FACTORS & ORGANIZATIONAL PROCESS ASSETS WILL COME INTO PLAY
    *HOW SCOPE WILL BE MANAGED & CONTROLLED
    *OBTAIN ACCEPTANCE FOR DELIVERABLES
  18. 185.1 INPUTS/TOOLS/OUTPUTS OF "PLAN SCOPE MANAGEMENT"?*INPUTS:
    PROJECT MANAGMENT PLAN
    PROJECT CHARTER
    EEF & OPA
    *TOOLS: EXPERT JUDGEMENT/MEETINGS
    *OUTPUTS: SCOPE MANAGEMENT PLAN & REQUIREMENTS MANAGEMENT PLAN
  19. 195.2 INPUTS/TOOLS/OUTPUTS OF "COLLECT REQUIREMENTS"*INPUTS:
    PROJECT CHARTER
    STAKEHOLDER REGISTER
    *TOOLS: LOTS
    *OUTPUTS: REQUIREMENTS MANAGEMENT PLAN, REQUIREMENTS DOCUMENTS, REQUIREMENTS TRACEABILITY MATRIX
  20. 205.2 WHAT ARE THE TOOLS FOR "COLLECT REQUIREMENTS"?*Reviewing Historical Records
    *INTERVIEWS
    *FOCUS GROUPS
    *FACILITATED WORKSHOPS
    *BRAINSTORMING
    *NOMINAL GROUP TECHNIQUES
    *MULTI-CRITERIA DECISION ANALYSIS
    *MIND MAPS
    *AFFINITY DIAGRAMS
    *QUESTIONNAIRES & SURVEYS
    *OBSERVATIONS
    *PROTOTYPES
    *BENCHMARKING
    *CONTEXT DIAGRAMS
    *GROUPD DECISION_MAKING TECHNIQUES
  21. 215.2 WHAT'S THE PURPOSE OF THE REQUIREMENT DOCUMATION?Make sure the requirements are clear and unambiguous
  22. 225.2 Collect Requirements, Balance Stakeholders’ Requirements?*Make sure the requirements can be met within the project
    objectives
    *Prioritize requirements and resolve any conflicts between them
  23. 235.2 HOW DO YOU RESOLVE COMPETING REQUIRMENTS?*Use conflict resolution, team building, and problem-solving skills
    *Look for options including schedule compression, re-estimating, and brainstorming
    *Hold meetings, interviews, and discussions to facilitate the resolution
  24. 245.2 WHICH COMPETING REQUIRMENT DO YOU ACCEPT?Resolve competing requirements by accepting those that best comply with the following:
    *Business case stating the reason the project was initiated
    *Project charter
    *Project scope statement *Project constraints
  25. 255.2 WHAT'S THE PURPOSE OF THE REQUIREMENTS TRACEABILITY MATRIX?*Help link the requirements to the objectives and/or other
    requirements
    *Track the requirements over the life of the project to
    ensure they are accomplished
  26. 265.3 DEFINE SCOPE PROCESS...WHAT'S THE PURPOSE* The process of developing a detailed description of the project and product
  27. 275.3 DEFINE SCOPE: INPUTS/OUTPUTSInputs:
    *Project Charter
    *Scope Management Plan
    *Requirements documentation
    *Organizational process assets
    Outputs
    *Project Scope Statement
    *Requirements Documentation
    *Project Document Updates
  28. 285.3 DEFINE SCOPE*Use the scope management plan, requirements documentation, project charter, and information about project risks, assumptions, and constraints to help define scope
    *Primarily concerned with what is and is not included in the
    project and its deliverables
  29. 295.3 DEFINE SCOPE: PRODUCT ANALYSIS WHAT HAPPENS HERE?*Analyze the objectives and description of the product stated
    by the customer or sponsor and turn them into tangible
    deliverables
  30. 305.3 DEFINE SCOPE: WHAT IS CONTAINED IN THE PROJECT SCOPE STATEMENT?*Product scope
    *Project scope
    *Deliverables
    * Acceptance criteria
    *WHAT IS NOT PART O FTHE PROJECT
    *ASSUMPTIONS AND CONTRAINTS
  31. 315.4 CREATE WBS: WHAT'S THE PURPOSE OF THE WBS?*Process of subdividing project deliverables and project work into smaller, more manageable components
  32. 325.4 WBS: INPUTS & OUTPUTSInputs:
    *Project scope statement
    *Requirements documentation
    *Organizational process assets
    Outputs
    *Scope Baseline
    *WBS
    *WBS Dictionary
    *Project Document Updates
  33. 335.3 WHY IS THE WBS SO IMPORTANT?*Graphical picture of the hierarchy of the project
    *Identifies all the deliverables to be completed; deliverables not included are not part of the project
    *Foundation which the project is built
    *Is VERY important
    *Should exist for every project
    *Forces you to think through all aspects of the project
    *Can be reused for other projects
    *Does NOT show dependencies
  34. 345.3 WHAT IS THE WBS DICTIONARY?*Description of the work to be done for each work package in the WBS
    *Helps make sure the resulting work better matches what is needed
    *Used to prevent scope creep
  35. 355.4 CREATE WBD: WHAT DOES THE SCOPE BASELINE INCLUDE?*Project scope statement
    *WBS
    *WBS dictionary
  36. 365.5 VALIDATE SCOPE: WHAT IS THE PROCESS?*Process of formalizing acceptance of the completed project deliverables.
    *Meeting with the customer or sponsor to gain formal acceptance of interim deliverables
  37. 375.5 VALIDATE SCOPE: INPUTS/OUTPUTS (M&C PHASE)?Inputs:
    *Project management plan
    *Requirements documentation
    *Requirements traceability matrix
    *Verified deliverables
    Outputs
    *Accepted Deliverables
    *Change Requests
    *Project Document Updates
  38. 38—

Information

Description
PMP Project Management Flashcards on SCOPE MANAGMENT, created by kat atkins on 02/03/2017.
Created by
kat atkins
Views
5
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?