Agile Project Management in the Google Certificate: What Course 5 Covers
Course 5 of the Google PM Certificate is Agile Project Management. It's a significant shift from the first four courses. Where Courses 1-4 cover traditional, sequential project management (define scope, plan detail, execute, close), Course 5 introduces iterative, adaptive methodologies. You learn Scrum, Kanban, and why Agile matters in fast-moving industries. This article breaks down everything Course 5 covers and why it's critical for modern PM work.
Why Course 5 Exists: The Agile Revolution
For decades, project management was Waterfall: define all requirements upfront, plan in detail, execute the plan, deliver at the end. This works for projects with stable requirements (building a bridge, large infrastructure projects). But in software development, startups, and fast-changing industries, requirements evolve. Customers realize mid-project what they actually want. Markets shift. Technologies change. Waterfall breaks down in this environment.
Agile flips the model: plan in small increments (sprints), deliver working pieces frequently, get feedback, adapt. Course 5 teaches you why Agile matters and how to run Agile projects.
Core Concepts in Course 5
What is Agile? (Beyond the buzzword)
Agile is a mindset and set of practices focused on: early and continuous delivery of value, responding to change over following a fixed plan, collaboration with customers, and motivated individuals. The Google course teaches that Agile isn't a single methodology; it's an umbrella of approaches (Scrum, Kanban, etc.) that share these principles.
Waterfall vs. Agile comparison
The course contrasts the two:
- Waterfall: sequential phases, detailed upfront planning, single delivery at the end, change is expensive
- Agile: iterative sprints, rolling planning, frequent deliveries, change is built in
You learn when to use each. Waterfall for fixed-scope construction. Agile for evolving software. Most companies use a hybrid (some projects waterfall, some agile, some in-between).
The Agile Manifesto and 12 Principles
The course references the Agile Manifesto: four values and 12 principles that guide Agile work. You don't memorize all 12, but you understand the spirit: people over processes, working software over documentation, responding to change, customer collaboration. This mindset matters as much as the mechanics.
Scrum Framework (The Most Detailed Section of Course 5)
Scrum is the most popular Agile framework. The course dedicates significant time to it. You learn:
Scrum Roles:
- Product Owner: Represents the customer/business. Maintains the product backlog (prioritized list of features/work). Decides what to build.
- Scrum Master: Facilitates the Scrum process. Removes blockers, coaches the team on Scrum practices. NOT a project manager (doesn't own scope/budget).
- Development Team: Builds the product. Cross-functional (developers, designers, QA). Self-organizing around sprint goals.
Scrum Artifacts (the things you create):
- Product Backlog: Prioritized list of all features, improvements, fixes. Lives in a tool (Jira, Azure DevOps, Trello). Owned by Product Owner.
- Sprint Backlog: Subset of the product backlog selected for the current sprint (usually 2 weeks). Team commits to completing it.
- Increment: Working product that results from the sprint. Should be "potentially shippable" (could go to users, even if you don't release it yet).
Scrum Ceremonies (the meetings):
- Sprint Planning: Team selects items from product backlog for the sprint, breaks them into tasks, estimates effort. Usually 2-4 hours for a 2-week sprint.
- Daily Standup: 15-minute daily sync. Each person: what did I do yesterday, what am I doing today, any blockers?
- Sprint Review: At the end of the sprint, team demonstrates completed work to stakeholders. Get feedback.
- Sprint Retrospective: Team reflects: what went well, what could improve, what will we change next sprint?
You learn why each ceremony matters. Standups prevent surprises. Retrospectives drive continuous improvement. Sprint planning ensures commitment.
Velocity and Burndown:
The course introduces velocity (how much work the team completes per sprint, usually measured in story points) and burndown charts (visual showing work remaining vs. days in sprint). These predict if the team can complete sprint commitments.
Kanban Basics (The Second Major Framework)
Kanban is simpler than Scrum. Instead of sprints, work flows continuously. Key concepts:
- Work-In-Progress (WIP) limits: Cap the number of items in progress. Forces focus and prevents overload.
- Visual workflow: Kanban board shows columns: To Do, In Progress, Done. Items move across as they progress.
- Continuous flow: Work pulls through the system based on capacity, not sprints.
- Metrics: Lead time (how long from request to delivery), cycle time (how long actively working). Kanban focuses on flow efficiency.
Kanban is good for ongoing work (support teams, operations) where you don't have distinct releases. Scrum is good for product development with defined releases.
Agile Metrics and Tracking
How do you track progress in Agile? Not Gantt charts (those assume you know what you're building upfront). Instead:
- Velocity tracking: How much does the team accomplish per sprint? Use past velocity to forecast future sprints.
- Burndown charts: Visual of remaining work. Slope tells you if you'll finish on time.
- Release burndown: Across the entire release (multiple sprints), remaining work.
- Cycle time: How long items spend in the system from start to done.
- Lead time: How long from request to delivery.
The course teaches these are different from traditional project metrics (Gantt, baseline, variance). They're suited to Agile's adaptive nature.
Common Agile Challenges and How to Handle Them
The course doesn't pretend Agile is perfect. It addresses real challenges:
Challenge: Scope creep ("We'll just add one more feature")
Solution: Product Owner prioritizes ruthlessly. Features not in the backlog don't get built. Sprint scope is locked.
Challenge: Stakeholders want detailed upfront forecasts**
Solution: Show velocity and historical data. "Based on 4 sprints at 35 points per sprint, we'll deliver 100 points of features in 3 months. New requirements will shift timeline accordingly."
Challenge: Team resists ceremonies ("More meetings!")**
Solution: Keep ceremonies short and valuable. 15-min standup, not 45-min. Skip retrospectives if everyone agrees (rare). Ceremonies exist because they prevent bigger problems.
Challenge: Scaling Agile (What if you have 50 developers, not 8?)**
Solution: The course introduces SAFe (Scaled Agile Framework) at a high level. Multiple Scrum teams, shared product vision, program-level planning. Complexity, but necessary for large organizations.
Real-World Application: When to Use Agile vs. Waterfall
The course doesn't say Agile is always better. It teaches judgment:
Use Agile when: Requirements will evolve (software, product development, marketing). Value from rapid feedback. Team can ship increments. Budget is flexible enough to adapt scope based on learning.
Use Waterfall when: Requirements are fixed upfront (regulatory compliance, construction, hardware). Single big delivery. Team can't iterate. Budget is fixed and scope-driven.
Use hybrid:** Many real projects blend waterfall planning with agile execution. You plan the high-level roadmap (waterfall), then execute in agile sprints.
How Scrum Master Differs From Traditional Project Manager
This is critical for understanding Agile: the Scrum Master isn't the project manager in the traditional sense. They don't own scope, budget, or timeline decisions.
Scrum Master: Facilitates team process, removes blockers, coaches on Scrum practices. Servant-leader role.
Traditional PM: Owns scope, budget, timeline. Makes decisions. Reports up the chain.
Understanding this distinction is important if you're aiming for Scrum Master or Product Manager roles (both related to but different from traditional PM).
Key Takeaways From Course 5
After Course 5, you understand:
- Why Agile exists and when it's appropriate
- How Scrum works end-to-end (roles, ceremonies, artifacts)
- How to track Agile progress (velocity, burndown)
- Basic Kanban principles for continuous flow work
- How to lead teams that expect Agile ways of working
This positions you for Agile PM or Scrum Master roles, which are increasingly in demand, especially in tech.
Related reading: Dive deeper into the Scrum framework specifically and explore how Waterfall and Agile compare.
Next Steps
If you want a structured study companion, our Google PM Certificate Study Guide covers the full 6-course breakdown, a week-by-week study plan, and 50 practice questions with answer explanations—everything you need in one place.
For AI-powered tutoring, SimpuTech's Google PM Certificate study coach walks you through practice questions, explains concepts you're stuck on, and builds a custom study plan around your schedule. Try it free for 1 day.
Program details verified against grow.google/certificates/project-management as of March 2026. Pricing and course structure are subject to change—confirm current details before enrolling.