Project Management Principles and Practices Study Guide
Master Project Management Principles and Best Practices with our comprehensive study guide. Get expert insights on Agile and Waterfall methodologies, risk management, and team leadership. Perfect for PMP Exam Prep and real-world application. Start your journey to certification success and project excellence today. Downloadable PDF included!
Short-Answer Quiz
Instructions: Please answer the following ten questions in two to three sentences each, based on the provided source materials.
- What is the fundamental shift in the PMBOK® Guide – Seventh Edition compared to previous editions?
- According to the Kissflow article, what are the five phases of the project management life cycle?
- Define "scope creep" and explain why a well-defined project scope is essential for preventing it.
- What does the S.M.A.R.T. acronym stand for, and what is its purpose in project planning?
- Explain the project management principle of "Stewardship" and list its four key components.
- What is a Project Performance Domain, and can you name at least three of the eight domains identified in the PMBOK® Guide?
- Differentiate between a predictive development approach and an adaptive development approach.
- According to the PMBOK® Guide, what is the difference between a "model," a "method," and an "artifact"?
- Describe the purpose of a risk register and a probability and impact matrix in the risk management process.
- What is "tailoring" in the context of project management, and why is it considered a crucial principle?
Answer Key
- The fundamental shift in the PMBOK® Guide – Seventh Edition is the move from a process-based standard to a principles-based standard. This was done because process-based standards are prescriptive by nature, and the rapidly evolving field of project management required a more flexible approach. The new edition focuses on intended outcomes rather than just deliverables.
- The five phases of the project management life cycle are Project Initiation, Project Planning, Project Execution, Project Monitoring and Controlling, and Project Closing. This structure divides a project into manageable stages, each with its own goals and deliverables, to turn an idea into a working product.
- Scope creep is the gradual and insidious addition of project deliverables, features, or out-of-scope activities beyond what was initially agreed upon. A well-defined project scope is essential for preventing this because it creates a clear boundary, documented in a project scope statement, that defines exactly what the project will deliver and what is considered out-of-scope, thus managing stakeholder expectations and protecting the project from unapproved changes.
- The S.M.A.R.T. acronym stands for Specific, Measurable, Achievable, Relevant, and Time-Bound. It is an established method used in the project planning phase to ensure that goals set for a project are critically analyzed, clearly defined, and attainable within a certain timeframe, which helps reduce risk.
- Stewardship is a project management principle where individuals act responsibly to carry out activities with integrity, care, and trustworthiness while maintaining compliance with internal and external guidelines. Its four key components are Integrity (behaving honestly and ethically), Care (diligently overseeing matters), Trustworthiness (accurately representing roles and authority), and Compliance (adhering to laws, rules, and regulations).
- A Project Performance Domain is a group of related, interactive, and interdependent activities that are critical for the effective delivery of project outcomes. The eight domains are Stakeholders, Team, Development Approach and Life Cycle, Planning, Project Work, Delivery, Measurement, and Uncertainty.
- A predictive approach is useful when project requirements can be well-defined at the start, allowing for upfront planning of scope, schedule, and cost. In contrast, an adaptive approach is used when requirements are subject to a high level of uncertainty and are expected to change; it establishes a clear vision initially, but the specific requirements are refined or replaced based on ongoing user feedback.
- A "model" is a thinking strategy to explain a process, framework, or phenomenon. A "method" is the means for achieving an outcome, output, result, or project deliverable. An "artifact" is a template, document, output, or project deliverable used in managing a project.
- A risk register is a repository used to record the outputs of risk management processes, including identified risks and their characteristics. A probability and impact matrix is a grid used to map the probability of each risk's occurrence against the impact it would have on project objectives, which helps in prioritizing risks for further analysis and response planning.
- Tailoring is the deliberate adaptation of a project's approach, governance, and processes to make them more suitable for the given environment and the work at hand. It is a crucial principle because every project is unique; adapting the approach maximizes value, manages constraints, and improves performance by using "just enough" process to achieve the desired outcome.
Essay Questions
Instructions: The following questions are designed to test a deeper, more synthesized understanding of the source materials. Plan and construct a detailed essay for each prompt.
- The PMBOK® Guide – Seventh Edition marks a significant shift from a process-based standard to a principles-based one. Discuss the implications of this change for a project manager. How do the 12 principles guide behavior across the 8 project performance domains? Use specific examples from the provided texts to support your arguments.
- Compare and contrast the 5-phase project management life cycle described in the Kissflow article with the spectrum of development approaches (Predictive, Hybrid, Adaptive) detailed in the PMBOK® Guide. How would the activities and focus within each of the five phases differ depending on which development approach is selected for a project?
- Define and discuss the concept of "tailoring" in project management. Explain why it is important, what specific aspects of a project can be tailored, and describe the four key steps in the tailoring process as outlined in the PMBOK® Guide.
- A project's success is increasingly defined by the value it delivers, not just by meeting scope, schedule, and cost constraints. Explain how a focus on "Value," as a core principle, influences project activities from initiation through closure. How do concepts like the business case, stakeholder engagement, and adaptability contribute to maximizing this value?
- Analyze the role of uncertainty in project management, incorporating the concepts of ambiguity, complexity, volatility, and risk (both threats and opportunities). Describe the key activities and considerations within the Uncertainty Performance Domain and explain how a project team can proactively navigate these challenges to improve project outcomes.
Glossary of Key Terms
Term | Definition |
Accountability | The condition of being answerable for an outcome. Accountability is not shared. |
Accuracy | Within the quality management system, accuracy is an assessment of correctness. |
Activity List | A documented tabulation of schedule activities that shows the activity description, activity identifier, and a sufficiently detailed scope of work description so project team members understand what work is to be performed. |
Actual Cost (AC) | The realized cost incurred for the work performed on an activity during a specific time period. |
Adaptability | The ability to respond to changing conditions. |
Adaptive Approach | A development approach in which the requirements are subject to a high level of uncertainty and volatility and are likely to change throughout the project. |
Agile | A term used to describe a mindset of values and principles as set forth in the Agile Manifesto. |
Ambiguity | A state of being unclear, having difficulty in identifying the cause of events, or having multiple options from which to choose. |
Analogous Estimating | A method for estimating the duration or cost of an activity or a project using historical data from a similar activity or project. |
Artifact | A template, document, output, or project deliverable. |
Assumption | A factor in the planning process that is considered to be true, real, or certain, without proof or demonstration. |
Assumption Log | A project document used to record all assumptions and constraints throughout the project. |
Authority | The right to apply project resources, expend funds, make decisions, or give approvals. |
Backlog | An ordered list of work to be done. |
Backlog Refinement | Progressive elaboration of the content in the backlog and (re)prioritization of it to identify the work that can be accomplished in an upcoming iteration. |
Baseline | The approved version of a work product, used as a basis for comparison to actual results. |
Budget | The approved estimate for the project or any work breakdown structure (WBS) component or any schedule activity. |
Budget at Completion (BAC) | The sum of all budgets established for the work to be performed. |
Burn Chart | A graphical representation of the work remaining in a timebox or the work completed toward the release of a product or project deliverable. |
Business Case | A value proposition for a proposed project that may include financial and nonfinancial benefits. |
C.L.E.A.R. Goals | A method for setting goals designed for the dynamic nature of a modern workplace, standing for Collaborative, Limited, Emotional, Appreciable, and Refinable. |
Cadence | A rhythm of activities conducted throughout the project. |
Change | A modification to any formally controlled deliverable, project management plan component, or project document. |
Change Control | A process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected. |
Change Management | A comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organizations from a current state to a future state with intended business benefits. |
Complexity | A characteristic of a project or its environment that is difficult to manage due to human behavior, system behavior, and ambiguity. |
Constraint | A limiting factor that affects the execution of a project, program, portfolio, or process. |
Contingency Reserve | Time or money allocated in the schedule or cost baseline for known risks with active response strategies. |
Continuous Delivery | The practice of delivering feature increments immediately to customers, often through the use of small batches of work and automation technology. |
Cost of Quality (COQ) | All costs incurred over the life of the product by investment in preventing nonconformance to requirements, appraisal of the product or service for conformance to requirements, and failure to meet requirements. |
Cost-Reimbursable Contract | A type of contract involving payment to the seller for the seller’s actual costs, plus a fee typically representing the seller’s profit. |
Crashing | A method used to shorten the schedule duration for the least incremental cost by adding resources. |
Critical Path | The sequence of activities that represents the longest path through a project, which determines the shortest possible duration. |
Daily Standup | A brief, daily collaboration meeting in which the team reviews progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated. |
Definition of Done (DoD) | A checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use. |
Deliverable | Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. |
Development Approach | A method used to create and evolve the product, service, or result during the project life cycle, such as a predictive, iterative, incremental, agile, or hybrid method. |
Duration | The total number of work periods required to complete an activity or work breakdown structure component, expressed in hours, days, or weeks. |
Earned Value (EV) | The measure of work performed expressed in terms of the budget authorized for that work. |
Effort | The number of labor units required to complete a schedule activity or work breakdown structure component, often expressed in hours, days, or weeks. |
Emotional Intelligence | The ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people. |
Enterprise Environmental Factors (EEF) | Conditions, not under the immediate control of the team, that influence, constrain, or direct the project, program, or portfolio. |
Estimate | A quantitative assessment of the likely amount or outcome of a variable, such as project costs, resources, effort, or durations. |
Estimate at Completion (EAC) | The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete. |
Estimate to Complete (ETC) | The expected cost to finish all the remaining project work. |
Executing Process Group | Those processes performed to complete the work defined in the project management plan to satisfy the project requirements. |
Fast Tracking | A schedule compression method in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. |
Fixed-Price Contract | An agreement that sets the fee that will be paid for a defined scope of work regardless of the cost or effort to deliver it. |
Forecast | An estimate or prediction of conditions and events in the project’s future based on information and knowledge available at the time of the forecast. |
Gantt Chart | A bar chart of schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates. |
Governance | The framework for directing and enabling an organization through its established policies, practices, and other relevant documentation. |
Hybrid Approach | A combination of two or more agile and nonagile elements, having a nonagile end result. |
Impediment | An obstacle that prevents the team from achieving its objectives. Also known as a blocker. |
In-scope | Project deliverables, tasks, or objectives that the team is committed to completing as part of the agreed scope - within the agreed project budget and schedule. |
Incremental Approach | An adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete. |
Initiating Process Group | Those processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase. |
Issue | A current condition or situation that may have an impact on the project objectives. |
Issue Log | A project document where information about issues is recorded and monitored. |
Iteration | A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is performed. |
Iterative Approach | A development approach that focuses on an initial, simplified implementation then progressively elaborates adding to the feature set until the final deliverable is complete. |
Kanban Board | A visualization tool that shows work in progress to help identify bottlenecks and overcommitments, thereby allowing the team to optimize the workflow. |
Kickoff Meeting | A gathering of team members and other key stakeholders at the outset of a project to formally set expectations, gain a common understanding, and commence work. |
Lagging Indicators | Measures of project deliverables or events that provide information after the fact, reflecting past performance or conditions. |
Leading Indicators | Measures that predict changes or trends in the project, which can be used to reduce performance risk by identifying potential variances before they cross a tolerance threshold. |
Lessons Learned Register | A project document used to record knowledge gained during a project, phase, or iteration so that it can be used to improve future performance for the team and the organization. |
Log | A document used to record and describe or denote selected items identified during execution of a process or activity. |
Management Reserve | Time or money allocated for unknown events such as unplanned, in-scope work. |
Method | The means for achieving an outcome, output, result, or project deliverable. |
Metric | A description of a project or product attribute and how to measure it. |
Milestone | A significant point or event in a project, program, or portfolio. |
Model | A thinking strategy to explain a process, framework, or phenomenon. |
Monitoring and Controlling Process Group | Those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate corresponding changes. |
Opportunity | A risk that would have a positive effect on one or more project objectives. |
Out-of-scope | Anything that is not in the agreed scope of the project. Tasks that are not part of the project's defined boundaries and will not be addressed within the current scope of work. |
Outcome | The end result or consequence of a process or a project. |
Phase Gate | A review at the end of a phase in which a decision is made to continue to the next phase, to continue with modification, or to end a project or program. Also known as a stage gate. |
Plan | A proposed means of accomplishing something. |
Planning | The neurological processes involved in the formulation, evaluation and selection of a sequence of thoughts and actions to achieve a desired goal; one of the executive functions of the brain. |
Planning Process Group | Those processes required to establish the scope of the project, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve. |
Portfolio | Projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. |
Power Skills | Skills such as communication, problem-solving, collaborative leadership, and strategic thinking that contribute to better project performance. |
Precision | Within the quality management system, precision is an assessment of exactness. |
Predictive Approach | A development approach in which the project scope, time, and cost are determined in the early phases of the life cycle. |
Probability and Impact Matrix | A grid for mapping the probability of occurrence of each risk and its impact on project objectives if that risk occurs. |
Product | An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item. |
Product Life Cycle | A series of phases that represents the evolution of a product, from concept through delivery, growth, maturity, and to retirement. |
Product Scope | The features and functions that characterize a product, service, or result. |
Program | Related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually. |
Progressive Elaboration | The iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available. |
Project | A temporary endeavor undertaken to create a unique product, service, or result. |
Project Charter | A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. |
Project Life Cycle | The series of phases that a project passes through from its start to its completion. |
Project Management | The application of knowledge, skills, tools, and techniques to project activities to meet project requirements. |
Project Management Body of Knowledge (PMBOK) | A term that describes the knowledge within the profession of project management. |
Project Management Institute (PMI) | The professional organization that publishes the Project Management Body of Knowledge (PMBOK® Guide). |
Project Management Office (PMO) | A management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques. |
Project Manager | The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives. |
Project Performance Domain | A group of related activities that are critical for the effective delivery of project outcomes. |
Project Scope | The work performed to deliver a product, service, or result with the specified features and functions. |
Project Scope Statement | A document detailing exactly what a project will deliver, including objectives, deliverables, costs, constraints, and assumptions. |
Project Team | A set of individuals performing the work of the project to achieve its objectives. |
Quality | The degree to which a set of inherent characteristics of a product, service, or result fulfills the requirements. |
Register | A written record of regular entries for evolving aspects of a project, such as risks, stakeholders, or defects. |
Requirement | A condition or capability that is necessary to be present in a product, service, or result to satisfy a business need. |
Reserve | A provision in the project management plan to mitigate cost and/or schedule risk. |
Resiliency | The ability to absorb impacts and to recover quickly from a setback or failure. |
Responsibility | The condition of being obligated to do or fulfill something. Responsibility can be shared. |
Retrospective | A regularly occurring workshop in which participants explore their work and results in order to improve both the process and product. |
Risk | An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. |
Risk Appetite | The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward. |
Risk Breakdown Structure (RBS) | A hierarchical representation of potential sources of risks. |
Risk Register | A repository in which outputs of risk management processes are recorded. |
Risk Threshold | A predetermined value of a measurable project variable that represents a limit that requires action to be taken if it is reached. |
Rolling Wave Planning | An iterative planning method in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. |
S.M.A.R.T. Goals | A method for setting goals that are Specific, Measurable, Achievable, Relevant, and Time-bound. |
Scope | The sum of the products, services, and results to be provided as a project. |
Scope Creep | The gradual addition of project deliverables or features, beyond what was initially agreed. |
Servant Leadership | The practice of leading the team by focusing on understanding and addressing the needs and development of team members in order to enable the highest possible team performance. |
Sponsor | The person who provides resources and support for the project, program, or portfolio, and is accountable for enabling success. |
Stakeholder | An individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a portfolio, program, or project. |
Stakeholder Register | A project document that includes information about project stakeholders including an assessment and classification of project stakeholders. |
Stewardship | A principle of project management that entails acting responsibly to carry out activities with integrity, care, trustworthiness, and compliance. |
System for Value Delivery | A collection of strategic business activities aimed at building, sustaining, and/or advancing an organization. |
Systems Thinking | A way of seeing the project as a holistic system with its own working parts that interact with each other and with external systems. |
Tailoring | The deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand. |
Threat | A risk that would have a negative effect on one or more project objectives. |
Uncertainty | A lack of understanding and awareness of issues, events, paths to follow, or solutions to pursue. |
User Story | A brief description of an outcome for a specific user, which is a promise of a conversation to clarify details. |
Value | The worth, importance, or usefulness of something. |
Volatility | The possibility for rapid and unpredictable change. |
Work Breakdown Structure (WBS) | 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. |