Book Notes Flashcards
Intiating, Planning, Executing, Monitoring and Controlling, and Closing
Predictive Process Life Cycle
5 Stages of Predictive Process Life Cycle
Intiating, Planning, Executing, Monitoring and Controlling, and Closing
Records of what the PM has planned, scheduled, and budgeted for in terms of scope, schedule, and cost performance.
Baselines
Baselines
Records of what the PM has planned, scheduled, and budgeted for in terms of scope, schedule, and cost performance. Used to compare project’s actual performance against what was planned.
When the earliest parts of a project are planned in detail and the later phases are planned at a higher level.
Rolling Wave Planning
The process of continually refining estimates and scope definition.
Progressive Elaboration
Feasibility, Initiation, Release Planning, Iterations, Close Out
Adaptive Process
Five stages of the adaptative process?
Feasibility, Initiation, Release Planning, Iterations, Close Out
Determines the potential profitability of an investment by calculating the benefits received in relation to the cost
Return on Investment
The value today of future cash flows - the project with the greatest PV is typically selected
Present Value
The present value of the total benefits (income or revenue) minus the costs over many time periods
Net Present Value
Analysis and research work that is completed to make sure a requested change or new product is feasible and will bring benefits or value to the organization and its customers.
Needs Assessment
Captures the business need - why the project was selected and how it fits into the organization’s strategic goals
Business Case
Captures the org’s desired benefits from the project and explains who the benefits will be maximized/sustained
Benefits Realization Plan
Document that authorizes the start of a project and provides the project manager with the authority to apply organizational resources to project activities.
Project Charter
Various records and files that are used throughout the project lifecycle to support project planning, execution, monitoring, and control. They provide detailed information and data that help manage the project effectively.
Project Documents
Used in agile project management - profile of a particular stakeholder who will use the product
Persona
Document the strategy and approach for managing the project and processes related to topics of scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement. “How-to” guides
Management Plans
Defines how the scope will be achieved, what tools will be used to plan how the project will accomplish scope, how the scope will be managed and controlled, and how acceptance of deliverables will be obtained.
Scope Management Plan
Describes techniques the PM intends to use in identifying requirements and how the requirements will be analyzed, prioritized, managed, and changes tracked.
Requirements Management Plan
Documents how a PM will plan, manage, and control the project to the schedule baseline, and how they’ll manage schedule variances.
Schedule Management Plan
Documents how to estimate, budget, manage, and monitor and control project costs for the project.
Cost Management Plan
Identifies all relevant organizational or industry practices, standards, and requirements for the quality of the project, the product of the project, and the project management efforts. Helps to ensure that the project and its outcomes meet the expected quality levels and satisfy stakeholder expectations.
Quality Management Plan
Plan for how and when resources will be added, managed, and released from project.
Resource Management Plan
Documents how a PM will manage and monitor communications.
Communications Management Plan
Defines how risk will be structured and performed for the project.
Risk Management Plan
Documents an overall procurement process and how procurements will be executed and controlled. EEFs and OPAs will significantly influence this plan.
Procurement Management Plan
Documents the existing and desired levels of engagement for all stakeholders, including plans to achieve the desired levels. Details the way stakeholders will be involved in the project and includes guidelines and metrics for monitoring and evaluating how well the plan is meeting the needs of stakeholders and project.
Stakeholder Engagement Plan
Plan that integrates all the individual management plans into a cohesive whole.
Project Management Plan
A set of plans and baselines.
Project Management Plan
Describes the phases of work on a project required to produce the deliverables.
Project Life Cycle
The approach used to produce the project deliverables: predictive, adaptive, or hybrid
Development Approach
Milestones are built into project management plans, so managers and stakeholders can compare project progress to what was planned, and then identify any changes needed to the management plans
Management Reviews
Scope, Schedule, and Cost Baselines combined
Performance Measurement Baseline
Project scope statement, work breakdown structure, and WBS dictionary
Scope Baseline
Agreed-upon schedule, including start and stop dates for each activity, and scheduled milestones
Schedule Baseline
Spending plan indicating how much money is approved for the project and when the funds are required and will be available
Cost Baseline
Defines how requirements will be gathered, analyzed, prioritized, evaluated and documented, and how the requirements will be managed and controlled throughout the project
Requirements Management Plan
Defines and plans for stakeholders’ needs, wants, expectations, and assumptions
Requirements Management Plan
Describes how changes will be managed and controlled
Change Management Plan
Defines naming conventions, the version control system, and the document storage and retrieval system, and entails how changes to the documentation will be managed
Configuration Management Plan
System that includes standardized forms, reports, processes, procedures, and software to track and control changes
Change Control System
Contains the org’s standardized configuration management tools, processes, and procedures that are used to track and control the evolution of the project documentation
Configuration Management System
Due to the iterative nature of planning, project documents must be updated frequently. This means that _____ _____ _____ are an output of many of the project management processes.
Project Document Updates
Business Analysis work ____ business needs
clarifies
A condition or capability needed to satisfy a business need
Requirement
Requirements that come from a person or group; often thought of as requests
Stakeholder Requirements
Describes the product or solution to be built
Solution Requirements
Helps the project team prepare the users for the change to the new product or service
Transition Requirements
Defines how the project team will know when their work has met the requirements
Acceptance Criteria
Project management plans - answers how many, how much, how long, etc.
Project requirements
Describes how the project manager and/or the business analysis engages with SMEs to gather and analyze business needs
Collect Requirements process
Brainstorming, interviews, focus groups, questionnaires/surveys, benchmarking, reuqirements workshops, and user stories are examples of what?
Data Gathering
Grouping ideas by similarity
Affinity Diagrams
Consensus approach
Facilitation
Follows 4 steps resulting in ranked ideas
Nominal Group Technique
Particiapnts build on each other’s ideas
Brainstorming
Measuirng performance against other organizations
Benchmarking
Diagram of ideas or notes
Mindmapping
Step-by-step instructions describing the user experience
Use Cases
Model of proposed product
Prototype
Used to make decisions in group setting
Voting
Short descriptions used with agile approaches
User stories
Linking requirements to each other to ensure nothing has been missed and that the original business need will be fulfilled
Requirements Traceability
Identifies the characteristics and functions of a product or service
Product Scope
The work the team will do to deliver the the product of the project
Project Scope
The key Input to Define Scope is?
Requirement Documentation that is created in Collect Requirements
Used to analyze the objectives and descriptions of the product, as stated by customer or sponsor
Product Analysis
Allows the PM to make sure the product and project are understood and accurate
Product Analysis
A document that effectively says what the team will do on the project
Project Scope Statement
