Free Google Project Management Certificate Exam Flashcards

A formal document that officially authorizes a project and outlines its objectives, scope, stakeholders, and success criteria. It serves as a reference throughout the project lifecycle and helps align stakeholders on the project's purpose. The charter also defines the project manager's authority and responsibility.

The clearly defined boundaries of a project that specify what work is included and excluded. Scope includes deliverables, features, functions, and requirements that must be met. Proper scope definition prevents scope creep and ensures stakeholder alignment on expectations.

A framework for setting objectives that are Specific, Measurable, Achievable, Relevant, and Time-bound. SMART goals provide clarity and accountability for project teams. For example, 'Reduce customer complaints by 20% within 6 months' is a SMART goal.

Any individual, group, or organization that can affect, be affected by, or perceive themselves to be affected by a project. Stakeholders include project sponsors, customers, team members, vendors, and regulatory bodies. Identifying and managing stakeholder expectations is critical to project success.

The process of identifying stakeholders and assessing their interests, influence, and potential impact on the project. This analysis helps prioritize communication and engagement efforts. Tools like power-interest grids help categorize stakeholders by their level of authority and involvement.

A senior executive who champions the project, provides resources and funding, and removes organizational obstacles. The sponsor has the authority to make key decisions and approve major changes. They are accountable for the project's success at the organizational level.

A document that justifies the investment in a project by analyzing costs, benefits, risks, and alternatives. It answers why the project should be undertaken and what value it will deliver. The business case is used to secure funding and stakeholder buy-in.

A financial analysis that compares the total expected costs of a project against its total expected benefits. This helps determine if a project is financially viable and worth pursuing. The analysis considers both tangible (revenue, savings) and intangible (customer satisfaction) factors.

A goal-setting framework that defines clear objectives and measurable key results to track progress. Objectives describe what you want to achieve, while key results are specific metrics that indicate success. OKRs are commonly used at Google to align teams around shared goals.

The fundamental project management model showing the interdependence of scope, time, and cost. Changes to one constraint affect the others, so if scope increases, either time or cost must also increase. The triple constraint helps project managers make trade-off decisions.

A hierarchical decomposition of the total project work into smaller, manageable components called work packages. The WBS organizes deliverables and tasks in a tree structure, making it easier to estimate costs, assign resources, and track progress. It forms the foundation of project planning.

A visual timeline showing project tasks, their durations, dependencies, and milestones as horizontal bars across a calendar. Gantt charts help track progress, identify scheduling conflicts, and communicate timelines to stakeholders. They are one of the most widely used project scheduling tools.

The longest sequence of dependent tasks that determines the minimum project duration. Any delay in critical path tasks directly delays the project completion date. Project managers must closely monitor and manage critical path activities to keep the project on schedule.

A significant point or event in a project timeline that marks the completion of a major deliverable or phase. Milestones have zero duration and serve as checkpoints to measure progress. Examples include project kickoff, design approval, or product launch.

Relationships between tasks that determine the order in which work must be completed. The four types are Finish-to-Start (most common), Start-to-Start, Finish-to-Finish, and Start-to-Finish. Understanding dependencies is essential for creating realistic project schedules.

The process of assigning and managing people, equipment, materials, and budget across project tasks. Effective resource allocation ensures the right resources are available when needed. It requires balancing workload, skills, availability, and cost constraints.

A document that identifies potential risks, assesses their probability and impact, and outlines response strategies. Common risk responses include avoid, mitigate, transfer, and accept. Proactive risk management reduces surprises and prepares the team for challenges.

A responsibility assignment chart that clarifies roles for each task: Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), and Informed (kept updated). RACI matrices prevent confusion and ensure clear accountability across the team.

The amount of time a task can be delayed without affecting the project completion date. Tasks on the critical path have zero float, while non-critical tasks have positive float. Managing float helps project managers prioritize and allocate resources efficiently.

The process of predicting the amount of work required to complete project tasks. Common techniques include analogous estimation (using past projects), parametric estimation (using data), and three-point estimation (optimistic, pessimistic, most likely). Accurate estimation is crucial for realistic planning.

The approved financial plan that estimates all costs required to complete the project. It includes labor, materials, equipment, software, training, and contingency reserves. The budget serves as a baseline for tracking actual spending and managing cost performance.

A document that outlines what information will be shared, with whom, how often, and through which channels. It ensures stakeholders receive timely and relevant updates. Effective communication planning considers stakeholder preferences, information needs, and project complexity.

The process of ensuring project deliverables meet defined standards and stakeholder requirements. It includes quality planning, quality assurance (process-focused), and quality control (product-focused). Quality management balances delivering value while managing costs and timeline constraints.

A formal procedure for evaluating, approving, and implementing changes to project scope, schedule, or budget. All change requests are documented, assessed for impact, and require appropriate approval before implementation. This process prevents unauthorized changes and scope creep.

A regular update that communicates project progress, accomplishments, risks, and issues to stakeholders. Status reports typically include completed tasks, upcoming work, budget status, and any blockers. They keep stakeholders informed and maintain project transparency.

The process of identifying, tracking, and resolving problems that arise during project execution. Unlike risks (potential problems), issues are current problems requiring immediate attention. An issue log captures details, ownership, priority, and resolution status.

Activities and techniques to improve team performance, collaboration, and morale throughout the project. This includes training, team-building exercises, clear communication, and conflict resolution. Effective team development follows Tuckman's stages: forming, storming, norming, performing, and adjourning.

The process of raising issues to higher levels of authority when they cannot be resolved at the current level. Escalation ensures critical issues get appropriate attention and resources. Clear escalation paths and criteria should be established early in the project.

The process of overseeing relationships with external suppliers and contractors involved in the project. It includes evaluating proposals, negotiating contracts, monitoring performance, and ensuring deliverables meet specifications. Strong vendor management reduces risks and ensures quality external contributions.

The formal process of completing and concluding a project. Activities include obtaining final acceptance, documenting lessons learned, archiving project documents, releasing resources, and celebrating success. Proper closeout ensures knowledge transfer and organizational learning.

An iterative approach to project management that emphasizes flexibility, collaboration, and delivering value incrementally. Agile responds to change rather than following a rigid plan. The four core values are individuals over processes, working software over documentation, collaboration over contracts, and responding to change.

An Agile framework that organizes work into fixed-length iterations called sprints, typically 2-4 weeks. Scrum uses defined roles (Product Owner, Scrum Master, Development Team), events (ceremonies), and artifacts to deliver value incrementally. It emphasizes transparency, inspection, and adaptation.

A time-boxed iteration in Scrum, usually 2-4 weeks, during which a potentially releasable product increment is created. Each sprint has a goal, a defined scope of work from the backlog, and ends with a review and retrospective. Sprints provide regular opportunities to inspect and adapt.

An ordered list of all features, enhancements, and fixes that need to be done in a product. The Product Owner prioritizes items based on value, risk, and dependencies. Backlog items are refined over time with more detail added as they move closer to implementation.

A brief description of a feature from the end user's perspective, following the format: 'As a [user], I want [functionality] so that [benefit].' User stories focus on value and outcomes rather than technical specifications. They include acceptance criteria that define when the story is complete.

A Scrum ceremony where the team selects backlog items for the upcoming sprint and creates a plan to complete them. The team discusses the sprint goal, reviews backlog items, and estimates effort. The output is the sprint backlog with committed work and a clear objective.

A 15-minute daily meeting where team members share what they did yesterday, what they'll do today, and any blockers. The stand-up promotes transparency, identifies impediments quickly, and keeps the team aligned. It is not a status report to management but a team synchronization event.

A Scrum ceremony at the end of each sprint where the team demonstrates completed work to stakeholders. It provides an opportunity for feedback, validates that the increment meets acceptance criteria, and informs backlog prioritization. The review is collaborative, not just a presentation.

A Scrum ceremony where the team reflects on the past sprint to identify what went well, what could improve, and actions for improvement. Retrospectives promote continuous improvement and team learning. The focus is on process and collaboration, not individual performance.

A servant-leader who facilitates Scrum events, removes impediments, and coaches the team in Agile practices. The Scrum Master protects the team from external distractions and helps the organization adopt Scrum effectively. They are not a project manager but a process facilitator.

The person responsible for maximizing product value by managing and prioritizing the product backlog. The Product Owner represents stakeholders, defines requirements, and makes decisions about what to build. They must be empowered to make product decisions without committee approval.

An Agile method that visualizes work on a board with columns representing workflow stages. Teams pull work based on capacity rather than pushing fixed amounts. Kanban limits work-in-progress (WIP) to prevent overload and emphasizes continuous flow rather than time-boxed iterations.

A stakeholder analysis tool that maps stakeholders based on their level of power (authority) and interest (involvement) in the project. The four quadrants guide engagement strategies: manage closely (high power, high interest), keep satisfied (high power, low interest), keep informed (low power, high interest), and monitor (low power, low interest).

A document that records identified risks, their probability, impact, response strategies, and owners. The risk register is a living document updated throughout the project as new risks emerge and existing risks change. It serves as the central repository for all risk information.

A response strategy that reduces the probability or impact of a negative risk. Mitigation actions are proactive steps taken before the risk occurs. Examples include adding buffer time to schedules, conducting additional testing, or providing extra training to reduce skill-related risks.

Budget or time set aside to address identified risks if they occur. Contingency is based on risk analysis and is part of the approved project baseline. Unlike management reserve (for unknown risks), contingency is allocated to specific risks and managed by the project manager.

A document that outlines strategies and actions to effectively engage stakeholders throughout the project. It identifies stakeholder needs, communication preferences, and engagement levels. The plan helps build relationships, manage expectations, and gain stakeholder support.

A risk assessment tool that rates risks based on their likelihood of occurrence and potential effect on project objectives. Risks are plotted on a grid to prioritize response efforts. High probability and high impact risks require immediate attention and robust response plans.

Techniques project managers use to gain stakeholder support and cooperation without formal authority. Strategies include building relationships, demonstrating expertise, appealing to common goals, and negotiation. Effective influence is essential when managing diverse stakeholders with competing interests.

Knowledge gained from project experiences that can improve future projects. Lessons are documented throughout the project and formally captured during closeout. They include what went well, what could be improved, and recommendations. Sharing lessons learned contributes to organizational knowledge.