Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
75 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
Assumption Log |
Record of all assumptions & constraints that affect the project. |
Record |
|
|
What is an assumption? |
A factor in the planning process that is true, real, or certain without proof or demonstration. |
|
|
|
What do you use the assumption log for? |
May help identify items that have not been closed or managed. |
|
|
|
Basis of Estimates |
Shows how the duration, cost, & resources estimates were calculated to determine any variances from what was planned. |
|
|
|
Change Log |
A comprehensive list of changes submitted during the project. |
|
|
|
Issue Log |
A log that documents all issues & is critical for this process to ensure that all issues have been addressed in the Close Project or Phase process. |
|
|
|
Lessons Learned Register |
A record of knowledge gained throughout the project that shows how project tasks were addressed or should be addressed in the future to improve performance. |
|
|
|
Milestone List |
Identifies all significant points or events in the project & indicates whether the milestone was mandatory or not. |
|
|
|
Project Communications |
Reference for all communications that have been created throughout the project. |
|
|
|
Quality Control Measurements |
Documents the results of Control Quality activities so you can ensure the project's objectives satisfy stakeholders' expectations. |
|
|
|
Quality Reports |
Provides a summary of findings from the Control Quality process, including quality management issues as well as recommendations for improvements. |
|
|
|
Requirements Documentation |
Used to demonstrate compliance with the project scope. |
|
|
|
Risk Register |
A repository with details of all identified individual project risks. Valuable reference on risks that have occured throughout the project. |
|
|
|
Risk Report |
Provides information on sources of overall project risk & summary information on individual project risks. Valuable to check that there are no open risks at the end of the project. |
|
|
|
Project Documents |
Assumption Log, Basis of Estimates, Change Log, Issue Log, Lessons Learned Register, Milestone List, Project Communications, Quality Control Measurements, Quality Reports, Requirements Documentation, Risk Register, Risk Report |
|
|
|
Organizational Process Assets (OPAs) |
Plans, processes, policies, procedures, & knowledge bases that are specific to and used by a performing organization. |
|
|
|
Stakeholder Register |
Used to identify those people & organizations impacted by the project. This document includes the identification, assessment, & classification or project stakeholders. |
|
|
|
Project Charter |
Document issued by the project initiator or sponsor that formally authorizes the existence of a project & provides the project manager with the authority to apply organizational resources to project activities. |
|
|
|
Project Management Plan |
A document that describes how the project will be executed, monitored & controlled, and closed. |
|
|
|
Close Project or Phase Inputs |
Organizational Process Assets, Agreements, Project Documents, Project Charter, Project Management Plan, Accepted Deliverables, Business Documents, Procurement Documentation |
|
|
|
Close Project or Phase Outputs |
Project Documents Updates, Final Product, Service, or Result Transition, Organizational Process Assets Updates, Final Report |
|
|
|
Close Project or Phase Tools & Techniques |
Expert Judgement, Meetings, Data Analysis |
|
|
|
What is part of the Project Performance Summary in the final report? |
Scope Objectives, Quality Objectives, Cost Objectives & Schedule Objectives |
|
|
|
What type of projects use an approved version of the project scope statement, WBS & associated WBS dictionary as the scope baseline for the project? |
Predictive Projects |
|
|
|
Project Scope |
The work performed to deliver a product, service or result with specified features & functions |
|
|
|
Product Scope |
The features and functions of a product, service or result |
|
|
|
What does the Validate Scope process do? |
Gives formal acceptance of completed project deliverables. |
|
|
|
What are the outputs of Plan Scope Management? |
Scope management plan & requirements management plan |
|
|
|
What are tools & techniques of Plan Scope Management? |
Expert judgement, data analysis (alternatives analysis) & meetings |
|
|
|
What is the scope management plan? |
Documents how the project & product scope will be defined, developed, monitored, validated, & controlled |
|
|
|
What are the inputs of Plan Scope Management? |
Project charter, project management plan (quality management plan, project life cycle description, development approach), EEFs, & OPAs |
|
|
|
What links product requirements from their origin to the deliverables that satisfy them? |
Traceability Matrix |
|
|
|
What requirement describes temporary capabilities needed to move from the current as-is state to the desired future state? |
Transition & readiness requirements |
|
|
|
What is the main purpose of the stakeholder register? |
Identify stakeholders who can provide information on the requirements |
|
|
|
What are the inputs of the Collect Requirements process? |
OPAs, EEFs, Project Documents, Project Management Plan, Agreements, Project Charter, Business Documents |
|
|
|
What are the outputs of the Collect Requirements process? |
Requirements Traceability Matrix & Requirements Documentation |
|
|
|
What are the tools & techniques of the Collect Requirements process? |
Data Gathering, Data Analysis, Data Representation, Context Diagram, Interpersonal & Team Skills, Expert Judgement, Decision Making, Decision Making, Protoype |
|
|
|
What are the inputs of the Define Scope process? |
Project Charter, project management plan, project document, EEFs, OPAs |
|
|
|
What are the outputs of the Define Scope process? |
Project scope statement, project documents updates (assumption log, requirements documentation, requirements traceability matrix, stakeholder register) |
|
|
|
What is the key benefit of creating a Work Breakdown Structure? |
It provides a framework for what has to be delivered |
|
|
|
What is a Work Breakdown Structre (WBS)? |
A hierarchical decomposition of the total scope of work to be carried out to accomplish project objectives & create required deliverables |
|
|
|
What are outputs of the Create WBS process? |
Scope baseline, project documents updates |
|
|
|
What are inputs of the Validate Scope Process? |
Verified Deliverables, Project Documents, Project Management Plan, Work Performance Data |
|
|
|
Define verified deliverables |
Completed project deliverables that have been checked & confirmed for correctness through the Control Quality process |
|
|
|
What are outputs of the Validate Scope process? |
Accepted deliverables, Work performance information, Project documents updates, Change requests |
|
|
|
What are the tools & techniques of the Validate scope process? |
Decision making & Inspection |
|
|
|
What are the outputs of the Control Scope Process? |
Work performance information; change requests; project management plan updates (scope management plan, scope baseline, schedule baseline, cost baseline, performance measurement baseline); project ducoments updates ( lessons learned register, requirements documentation, requirements traceability matrix) |
|
|
|
What is Control Scope? |
The process of monitoring the status of the project & product scope & managing changes to the scope baseline. |
|
|
|
What are the tools & techniques of the Control Scope process? |
Data analysis (variance analysis, trend analysis) |
|
|
|
What are the inputs of the Control Scope Process? |
Project management plan; (scope management plan, requirements management plan, change management plan, configuration management plan, scope baseline, performance measurement baseline); project documents (lessons learned register, requirements documentation, requirements traceability matrix); work performance data; OPAs |
|
|
|
What are some considerations for tailoring for project schedule management? |
Life cycle approach, resource availability, project dimensions & technology support |
|
|
|
Develop Schedule is the process of what? |
Analyzing activity sequences, durations, resource requirements, & schedule constraints to create the project schedule module for project execution & monitoring & controlling |
|
|
|
Plan Schedule Managment is the process of what? |
Establishing policies, procedures & documentation for planning, developing, managing, executing & controlling the project schedule. |
|
|
|
What is the output of Plan Schedule Management? |
Schedule management plan |
|
|
|
Schedule Management Plan establishes what? |
Criteria & activities for developing, monitoring & controlling the schedule |
|
|
|
What are the tools & techniques of Plan Schedule Management? |
Expert judgement, data analysis(alternative analysis) & meetings |
|
|
|
What are the inputs for the Plan Schedule Management Process? |
Project Charter, project management plan(scope management plan, development approach), EEFs, OPAs |
|
|
|
Who should be included in a project schedule development meeting? |
Project manager, project sponsor, selected project team members, selected stakeholders, anyone w/responsibility for schedule planning or execution |
|
|
|
What are the tools & techniques of the Monitor Communications process? |
Expert judgement, project management information system, data representation, interpersonal & team skills, team meetings |
|
|
|
Which of the following is a tailoring consideration for Project Scope Management? |
Stability of Requirements |
|
|
|
All of the following are true about the project scope statement except: |
It is an output of the validate scope process |
|
|
|
What are inputs to the Sequence Activities Process? |
Project management plan (schedule management plan, scope baseline); project documents (activity attributes, activity list, assumption log, milestone list); EEFs, OPAs |
|
|
|
In earned value management, the cost variance is equal to: |
(CV = EV - AC) |
|
|
|
The engagement level of stakeholders can be classified as: |
Unaware, resistant, neutral, supportive, and leading |
|
|
|
What are considerations for tailoring in Project Quality Management? |
policy compliance & auditing, standards & regulatory compliance, continuous improvement, & stakeholder engagement |
|
|
|
What is SWOT analysis? |
Examines the degree to which organizational strengths may offset threats & determines if weaknesses might hinder opportunities |
|
|
|
What are 5 alternative strategies for dealing with threats? |
Escalate, avoid, transfer, mitigate, accept |
|
|
|
How many processes belong to the Planning Process Group? |
24 out of 49 processes |
|
|
|
How many processes belong to the Executing Process Group? |
10 out of 49 project management processes |
|
|
|
How many processes belong to the Monitoring & Controlling Process Group? |
12 out of 49 project management processes |
|
|
|
How many processes belong to the Closing Process group? |
1 out of 49 project management processes |
|
|
|
What is a contingency reserve? |
Time or money allocated in the schedule or cost baseline for known risks w/active response strategies. |
|
|
|
What are the Project Cost Management processes? |
Plan cost management, estimate costs, determine budget, control costs |
|
|
|
What is Earned Value Management (EVM)? |
Methodology that combines scope, schedule, & resource measurements to assess project performance & progress against the project baseline. |
|
|
|
What is Earned Schedule (ES)? |
Replaces the schedule variance measures used in traditional EVM (earned value - planned value) with ES & actual time (AT) |
|
