Google PM Certificate Course 5: Agile Project Management Explained

Course 5 (Agile Project Management) shifts from waterfall (plan-then-execute) to Agile (iterative planning and execution). You'll learn Scrum, Kanban, sprint planning, and how Agile teams deliver value incrementally. This course is different from Courses 1-4 and is essential for modern PM practice.

What Is Course 5?

Courses 1-4 teach traditional (waterfall) project management: you plan everything upfront, then execute the plan. Course 5 introduces Agile, a fundamentally different approach. In Agile, you plan a few weeks ahead, execute, gather feedback, and adjust. You deliver working products iteratively rather than all at the end.

Modern tech, startups, and increasingly traditional organizations use Agile. Understanding Agile is essential for contemporary PM practice.

Duration and Workload

Estimated time: 35-45 hours (3.5-4.5 weeks at 10 hours per week)

Course 5 is slightly shorter than earlier courses but feels more conceptual. You're learning frameworks and philosophies more than creating detailed documents. However, the mindset shift from waterfall to Agile can make it feel harder initially.

Major Topics in Course 5

Agile Philosophy and Principles

Core idea: Traditional waterfall assumes you can plan projects completely upfront. Agile assumes uncertainty is inevitable and plans should adapt to change.

Agile Manifesto values:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Twelve Agile principles: Course covers these, emphasizing customer satisfaction, embracing change, delivering frequently, and collaboration.

Key difference from waterfall: Waterfall says "follow the plan precisely." Agile says "adapt the plan as you learn."

Scrum Framework

What it is: The most popular Agile framework. Structures work into sprints (1-4 weeks), with daily communication and regular ceremonies.

Scrum roles:

• Product Owner: Represents customer, prioritizes work, accepts completed items
• Scrum Master: Facilitates process, removes blockers, coaches team
• Development Team: Creates the product, self-organizing, cross-functional

Scrum artifacts:

• Product Backlog: Prioritized list of features to build
• Sprint Backlog: Tasks the team commits to complete in current sprint
• Increment: Working product delivered at sprint end

Scrum events:

• Sprint Planning: Team decides what to complete in sprint
• Daily Standup: 15-minute sync on progress and blockers
• Sprint Review: Demo finished work to stakeholders
• Sprint Retrospective: Team reflects on process improvements

User Stories and Product Backlog

User story format: "As a [user type], I want [feature], so that [benefit]." Example: "As a customer, I want to save my cart, so I can complete purchase later."

Why user stories matter: They focus on user value, not technical implementation. Developers think about how to deliver value, not just code features.

Product backlog: Ordered list of user stories, prioritized by value. Team works through backlog sprint by sprint. Backlog is never "done"—it evolves as product vision changes.

Sprint Planning and Execution

Sprint cycle: Team commits to features, executes for 1-4 weeks, delivers working product, reflects and improves, repeats.

Key metrics:

• Velocity: How many story points can team complete per sprint? Helps forecast when features will be done
• Burndown: Visual showing remaining work per day. Trending down means on pace; flat or up means behind
• Sprint goals: What will this sprint accomplish? Focal point for decision-making

Daily standup: Each team member shares: yesterday's progress, today's plan, blockers. Keeps team synchronized and surfaces problems quickly.

Kanban Methodology

What it is: Alternative to Scrum. Visualizes work as it flows through stages: To Do, In Progress, Done. Work-in-progress (WIP) limits prevent bottlenecks.

Key concepts:

• Visualize: See all work and its status on a Kanban board
• Limit WIP: Only allow certain amount of work in progress. Forces completion before new work starts
• Manage flow: Focus on completing work, not starting work
• Continuous delivery: Features released as soon as ready, not in batches

Kanban vs. Scrum: Scrum uses fixed-length sprints; Kanban is continuous. Scrum plans upfront; Kanban is more reactive. Both are Agile; different flavors.

Iteration and Continuous Improvement

Retrospectives: End-of-sprint meeting where team discusses what went well, what went poorly, what to improve next sprint.

Feedback loops: Regularly demo work to customers and stakeholders, gather feedback, incorporate into backlog. Reduces risk of building wrong thing.

Adaptation: Backlog, process, team composition can evolve based on learning. Not rigid—responsive to change.

Agile vs. Waterfall

When to use waterfall: Project is well-defined upfront, requirements are stable, change is costly (construction, manufacturing). Plan upfront; execute plan; deliver at end.

When to use Agile: Requirements are uncertain, customer needs evolve, feedback is frequent, change is cheap (software, digital products). Plan incrementally; deliver frequently; adapt to feedback.

Hybrid approaches: Many organizations use hybrid: waterfall for infrastructure/setup, Agile for product development.

Assessment in Course 5

Graded Quizzes

Content: Agile philosophy, Scrum roles/artifacts/events, user stories, sprint planning, Kanban, retrospectives

Example question: "In your Scrum sprint, a team member discovers a major bug in finished work. How should the Scrum Master respond? A) Immediately pull from backlog to fix. B) Add to sprint backlog and discuss in standup. C) Wait until next sprint. D) Escalate to product owner."

Right answer: B. Team decides in standup how to address bugs discovered mid-sprint.

Peer-Graded Assignment

Typical task: Develop user stories for your project scenario. Or design a Kanban board for a workflow. Or plan a sprint and explain velocity estimation.

What gets graded: User story quality (clear value proposition, acceptance criteria), backlog organization (prioritization makes sense), Scrum understanding (roles, events clear)

Common Challenges in Course 5

Mindset Shift from Waterfall

Challenge: If you've learned waterfall (Courses 1-4), Agile's "plan as you go" can feel scary. How can you ship if you don't know everything upfront?

Reality: You're not shipping unknowingly. You're getting feedback early and adapting. In waterfall, you discover surprises at the end (too late to fix). Agile discovers them early (in time to adapt).

Understanding Velocity

Challenge: Velocity (story points per sprint) feels abstract. How do you estimate story points? How does velocity help?

Practical approach: Velocity is a team metric. Team estimates relative difficulty of user stories (is this twice as hard as that?). After sprints, team knows their velocity. "We complete 20 points per sprint" helps forecast when features ship.

User Story Writing

Challenge: Writing good user stories takes practice. Too vague? Too detailed? Wrong format?

Formula: "As a [user type], I want [feature], so that [benefit]." Include acceptance criteria (how do you know this is done?). Discuss with product owner and team. Iterate on clarity.

Agile in Practice: Real Environments

If you work in tech or startups, you're likely using Agile. Course 5 teaches frameworks for what you might already be doing. Non-tech environments are increasingly adopting Agile too (marketing teams, nonprofits, healthcare).

Course 5 is where theory meets practice most directly. Real Agile teams vary—pure Scrum is rare; hybrid approaches are common. Course teaches foundational concepts that apply across variations.

How Course 5 Connects to the Capstone

The capstone project scenario (Sauce & Spoon restaurant expansion) can be approached waterfall or Agile. You choose based on what makes sense for the scenario. Course 5 gives you the Agile option.

Time Management for Course 5

Week 1: Agile philosophy, Scrum overview

Week 2: Scrum roles, artifacts, sprint planning

Week 3: User stories, daily standups, retrospectives

Week 4: Kanban, hybrid approaches, assignment/quizzes

Course 5 benefits from time to let concepts settle. Mindset shift from waterfall to Agile takes a few weeks to internalize.

Related reading: Google PM Certificate Course 4: Project Execution Covered and Agile Project Management in the Google Certificate.

Next Steps

Course 5 opens your eyes to modern PM. Waterfall and Agile aren't competing approaches—they're tools for different situations. By learning both, you can choose the right approach for each project. You're now equipped with two PM toolkits. After Course 5, you're ready for the capstone, where you'll integrate everything you've learned across all five courses.