Project Docs Flashcards
Project Charter
The process of developing a document that formally authorizes the existence of a project and provides the PM with the authority to apply organizational resources
Project Management Plan (PMP)
The document that describes how the project will be executed, monitored, and controlled and closed.
Scope Management Plan
Subsidiary Management Plan - Establishes how the scope will be defined, developed, monitored, controlled and validated
Requirements Management Plan
Subsidiary Management Plan - Establishes how the requirements will be analyzed, documented and managed
Schedule Management Plan
Subsidiary Management Plan - Establishes the criteria and the activities for developing, monitoring, and controlling the schedule
Cost Management Plan
Subsidiary Management Plan - Establishes how the costs will be planned, structured, and controlled. Can include:
- units of measure, level of precision, level of accuracy, organizational procedures links, control thresholds, rules of performance measurement, reporting formats
Quality Management Plan
Subsidiary Management Plan - Establishes how an organizations quality policies, methodologies, and standards will be implemented in the project
Resource Management Plan
Subsidiary Management Plan - Provides guidance on how project resources should be categorized, allocated, managed and released
Communications Management Plan
Subsidiary Management Plan - Establishes how, when, and by whom information about the project information about the project will be administered and disseminated
Risk Management Plan
Subsidiary Management Plan - Establishes how the risk management activities will be structured and performed
Procurement Management Plan
Subsidiary Management Plan - Establishes how the project team will acquire goods and services from outside of the performing organization
Stakeholder Engagement Plan
Establishes how stakeholders will be engaged in project decisions and execution, according to their needs, interests and impact
Scope Baseline
Approved version of a scope statement and work breakdown structure (WBS). Provides project and product definition, WBS, project scope statement, work package and planning package
Schedule Baseline
Approved version of the schedule model that is used as basis for comparison to the actual results
Cost Baseline
Approved version of the time-phased project budget that is used as a basis for comparison to the actual results
Change Management Plan
Describes how the change requests throughout the project will be formally authorized. Documents the roles and responsibilities of the change control board (CCB)
Configuration Management Plan
Describes how the information about the items of the project will be recorded and updated so that the product, service, or result of the project remains consistent
Performance Measurement Baseline
an integrated schedule-scope-cost plan for the project work
Project Life Cycle Description
a series of phases that a project passes through from its initiation to closure
Development Approach
Help define the scheduling approach, estimating techniques, scheduling tools Ex: predictive, iterative, agile or hybrid
Management Reviews
identifies the points in the project when the PM and relevant stakeholders review the project progress
Change Log
Project docs - contains the status of all change requests
Lessons Learned Register
Project docs - used to improve performance of the project and avoid repeating mistakes. Identify where to set rules or guidelines
Milestone List
Project docs - shows the scheduled dates for specific milestones
Project communications
project docs - includes performance reports, deliverable status and other information
Project Schedule
project docs - includes the list of work activities, their durations, resources and start/finish dates
- presents linked activities with planned dates, durations, milestones and resources
- uses bar charts, milestone charts and project schedule network diagrams
Requirements Traceability Matrix
Project docs - links product requirements to the deliverables
Risk Register
Project docs - provides information on threats and opportunities that may impact project execution
Risk Report
Project docs - provides information on sources of overall project risk along with summary information on identified project risks
Activity List
Activities to be performed to complete project work
stakeholder register
additional information on existing or new stakeholders is gathered
Project team assignments
Project docs - provide info on the type of competencies & experiences available in the project
Resource Breakdown Structure
Project docs - includes information on the composition of the team that may help to understand what knowledge is available as a group
Basis of estimates
Project docs - indicates how the various estimates were derived and can be used to make a decision on how to respond to variances
Cost Forecasts
Project docs - used to determine if the project is within defined tolerance ranged
Quality Reports
Project Docs - includes quality management issues, recommendations for process, project and product improvements, corrective action recommendations and a summary of findings
Schedule Forecasts
Project docs - used to determine if the project is within defined tolerance ranges for schedule
quality control measurements
document the results of control quality activities
requirements documentation
used to demonstrate compliance with the project scope - how individual requirements meet the business need
benefits management plan
outlines the targeted benefits of the project
project scope statement
the description of the project scope, major deliverables, assumptions and constraints
verified deliverables
project deliverables that are completed and checked for correctness through the control quality process
activity attributes
extend the description of the activity by identifying multiple components associated with each activity
resource calendars
influence the duration of schedule activities due to the availability of specific resources
duration estimates
contains the quantitative assessment of the likely number of work periods that will be required to complete an activity
project schedule network diagrams
contain logical relationships of predecessors and successors that will be used to calculate the schedule
resource requirements
identify the types and quantities of resources required for each activity used to create the schedule model
schedule data
the collection of information for describing and controlling the schedule
project calendars
identifies working days and shifts that are available for scheduled activities
project funding requirements
total and periodic funding requirements are derived from the cost baseline
quality metrics
describes a product attribute and how the control quality process will verify compliance to it
test and evaluation docs
created based on industry needs and the organizations templates - they are used to evaluate the achievement of quality objectives
physical resource assignments
documentation of the physical resource assignments records the material, equipment, supplies, locations and other resources used
team charter
where the team operating guidelines are documented
team project assignments
identify the team and member roles and responsibilities
risk breakdown structure (RBS)
structure risk categories - EX: technical risk, management risk, commercial risk, external risk
stakeholder risk appetite
measurable risk thresholds around each project objective for the stakeholder
definitions of risk probability and impacts
specific to the project context and reflect the risk appetite and thresholds of the organization and key stakeholders
probability and impact matrix
shows opportunities and threats using positive and negative impact threats (high, medium, low)
reporting formats
define how the outcomes of the project risk management will be documented, analyzed and communicated
tracking
how risk activities will be recorded and audited
procurement documentation
initial procurement documentation should be reviewed as procured goods and services from outside the organization may increase or decrease overall project risk
assessment of overall project risk exposure
changes of project success and degree of inherent variability remaining within the project at the time the analysis was conducted, indicated by the range of possible project outcomes
detail probabilistic analysis of the project
quantitative risk analysis - S-curves, tornado diagrams, critical analysis
prioritized list of individual project risks
individual risks that post the greatest threat or opportunity
recommended risk responses
suggested responses to the level of overall project risk exposure or key individual project risks
Procurement strategy
make or buy analysis, delivery methods, contract payment types, procurement phases
bid documents
used to solicit proposals from perspective sellers - generally used when the seller selection decision is based on price
Request for Information (RFI)
bid documents - used when more information on the good and services to be acquired is needed form the sellers
Request for quotation (RFQ)
bid documents - used when more information is needed on how vendors would satisfy the requirements and how much it would cost
request for proposal (RFP)
bid documents - used where there is a problem in the project and the solution is not easy to determine
procurement statement of work
defines the portion of the project scope that is to be included within the related contract - describes the procurement item in sufficient detail to allow perspective sellers to determine if they are capable of providing the products, services or results
source selection criteria
buyer seeks to ensure that the proposal selected will offer the best quality for the services required
make or buy decisions
decisions as to whether particular work can best be accomplished by the project team or needs to be purchased from outside sources
independent cost estimates
For large procurements, the procuring organization may elect to either prepare its own independent estimate or have a cost estimate prepared by an outside professional estimator to serve as a benchmark on proposed responses
sellers proposals
prepared in response to a procurement document package, form the basic information that will be sued by an evaluation body to select one of more successful bidders
selected sellers
those who have been judged to be in a competitive range based on the outcome of the proposal or bid evaluation
Business Case
documented economic feasibility study used to establish the validity of the benefits of a selected component lacking sufficient definition and that is used for further PM activities
Benefits Management Plan
describes how and when the benefits of the project will be delivered
agreement
a mutually binding document that obligates a seller to provide the specific products, services or results of a contract, memorandum or understanding (MOU), letters of agreement, verbal agreements, email or other tangible forms
