Google PM Certificate Course 4: Project Execution Covered

Course 4 (Project Execution and Closing) covers the long middle and end phases of projects. You'll learn how to monitor progress, manage quality, handle stakeholder communication, respond to risks, manage changes, and close projects successfully. This course teaches the day-to-day PM work.

What Is Course 4?

Project Execution is where your plan becomes reality. Your team is working, tasks are progressing, and issues arise. Course 4 teaches how to keep projects on track, manage quality, communicate progress, handle problems, and eventually close projects and capture lessons learned. This is the longest project phase and the most critical for PM success.

Duration and Workload

Estimated time: 40-50 hours (4-5 weeks at 10 hours per week)

Course 4 is substantial but slightly shorter than Course 3 because it's less tool-heavy (no Gantt charts to create). It's conceptually rich but less technical.

Major Topics in Course 4

Monitoring and Tracking Progress

What you learn: How to track whether a project is on schedule and within budget. What metrics do you monitor? How do you report status?

Key concepts:

• Earned Value: Percentage of work complete based on actual progress, not time elapsed
• Schedule variance: Are you ahead/behind timeline?
• Cost variance: Are you under/over budget?
• Status tracking: % complete, milestones, burn-down charts, dashboards

Practical application: Weekly status meetings where team reports progress, identifies blockers, and discusses next week. You track against plan. If schedule slipping, you escalate.

Quality Management

What you learn: How to ensure project deliverables meet quality standards. What constitutes "done"? How do you verify quality?

Quality aspects:

• Acceptance criteria: What defines acceptable? Set before work, verify during execution
• Testing and QA: How do you validate quality before delivery?
• Defect management: What happens when quality issues are found?
• Continuous improvement: Learning from quality issues to improve processes

Key insight: Quality is managed in, not inspected in. Prevention is cheaper than correction.

Stakeholder Communication

What you learn: Keeping stakeholders informed, managing expectations, addressing concerns proactively.

Communication dimensions:

• Frequency: How often do you communicate? (Weekly for team, monthly for executives, quarterly for sponsors)
• Channel: Email, meetings, dashboards, reports?
• Content: What information do different stakeholders need?
• Tone: Transparent, honest, professional
• Two-way: You listen to feedback, address concerns

Real example: Executive sponsor wants monthly status update in 5-minute meeting. Team wants daily standups. Client wants weekly detailed reports. You tailor communication to each stakeholder.

Risk Management

What you learn: Identifying risks, assessing probability/impact, developing mitigation strategies, monitoring for risk realization.

Risk management process:

• Identify: What could go wrong? Technical risks, resource risks, schedule risks, market risks
• Assess: Probability and impact. High probability + high impact = high priority
• Respond: Avoid (change plan), mitigate (reduce probability/impact), accept (live with it), transfer (buy insurance)
• Monitor: Watch for trigger events. If risk occurs, implement response plan

Key insight: Identifying risks early and planning mitigation prevents disasters. Reacting after something goes wrong is costly.

Change Management

What you learn: Handling requests to change scope, timeline, budget. How do you decide whether to accept changes? How do you assess impact?

Change process:

• Request: Someone requests change. Document it thoroughly.
• Assess: Impact on scope, timeline, budget, resources, quality?
• Decide: Approve or deny? If approve, how does it affect plan?
• Implement: Update plan and communicate change to stakeholders
• Track: Ensure change is executed as approved

Philosophy: Change is often necessary, but unmanaged change is chaos. Formal change management prevents scope creep and ensures stakeholder alignment.

Project Closing

What you learn: Finalizing projects, delivering to stakeholders, capturing lessons learned, celebrating success.

Closing activities:

• Final deliverables: Is everything handed off? Are stakeholders satisfied?
• Documentation: Project records archived for reference
• Lessons learned: What went well? What should we do differently next time?
• Resource release: Team members transition to other projects
• Celebration: Recognizing success and team effort

Often neglected: Many PMs rush closing to move to the next project. Course emphasizes proper closure matters—it preserves institutional knowledge and team morale.

Key Tools and Concepts

Status Reports and Dashboards

How do you present project health? Typical dashboard includes: % complete, schedule variance (on/ahead/behind), cost variance (under/on/over), key risks, major decisions pending, next milestone.

Risk Register

Document of identified risks with probability, impact, and response strategies. Living document updated throughout project.

Change Control Board (CCB)

Group that reviews and approves changes. Ensures changes are evaluated consistently and stakeholders agree before implementation.

Issues Log

Problems that have occurred and need resolution. Track status: open, in progress, resolved. Distinguish from risks (which haven't occurred yet).

Assessment in Course 4

Graded Quizzes

Content: Monitoring techniques, quality management, stakeholder communication, risk assessment, change control, closing processes

Example question: "Your project has a high-probability risk that a key resource might leave. To mitigate, you should: A) Hire a backup immediately. B) Cross-train other team members. C) Reduce scope to lower resource needs. D) Accept and plan for departure."

Right answer: B. Cross-training reduces risk impact if resource does leave.

Peer-Graded Assignment

Typical task: Develop risk management and communication plans for your ongoing project scenario. Or analyze a case study and identify risks/recommend responses.

What gets graded: Risk identification completeness, realistic probability/impact assessment, appropriate mitigation strategies, communication plan detail and appropriateness to stakeholders.

Common Challenges in Course 4

Risk Assessment Subjectivity

Challenge: Probability and impact are subjective. One person's "high probability" is another's "medium."

Approach: Use scales (High/Medium/Low or 1-5) consistently. Discuss with team and stakeholders. Document assumptions. There's no perfect assessment—consistency and transparency matter.

Change Management Rigor

Challenge: In practice, change feels bureaucratic. "Can't we just add this feature?" requires formal change request?

Reality: Yes. Informal changes cause scope creep and budget overruns. Formal change management protects schedule and budget while enabling necessary changes. It feels rigid initially but prevents problems.

Balancing Flexibility and Plan Adherence

Challenge: Should you stick to the plan or adapt? Course teaches both—execute according to plan but adapt when circumstances change.

Approach: Default to plan. Adapt when facts change (market conditions, technology, resources), not when someone requests scope change outside the change management process.

How Course 4 Connects to Course 5

Course 4 teaches execution in traditional (waterfall) environments. Course 5 teaches Agile execution, where planning and execution overlap iteratively. Course 4 is prerequisite to understanding why Agile differs.

Time Management for Course 4

Week 1: Monitoring, tracking, earned value

Week 2: Quality management

Week 3: Stakeholder communication and risk management

Week 4: Change management and closing

Week 5: Complete assignment and take quizzes

Real-World Application

Course 4 teaches day-to-day PM. If you're in a project-based role, you're likely doing execution phase work now. Course teaches frameworks for what you're already doing informally.

Many learners use the SimpuTech AI tutor to practice execution scenarios interactively, strengthening their ability to make decisions about risk, change, and quality management.

Related reading: Google PM Certificate Course 3: Project Planning Breakdown and How to Study for the Google PM Certificate.

Next Steps

Course 4 teaches the PM work most people associate with project management: keeping projects on track, managing problems, and delivering successfully. By the end of Course 4, you understand the full waterfall project lifecycle from initiation through closing. You're ready to manage real projects. Course 5 (Agile) will show an alternative approach, but the execution fundamentals you learn here apply across methodologies.