Google PM Certificate Capstone Project: What It Is and How to Nail It

Google PM Certificate Capstone Project: What It Is and How to Nail It

Course 6 of the Google Project Management Certificate is the capstone. Unlike the first five courses—which layer foundational concepts, tools, and frameworks—the capstone asks you to synthesize everything into a single, substantial deliverable. You're given a realistic project scenario, and your job is to apply every discipline you've learned: initiation, planning, execution, and Agile methodologies. You produce a portfolio-quality project charter, schedule, risk register, and stakeholder communication plan. This article breaks down exactly what the capstone is, what hiring managers expect, and how to build a capstone project that becomes evidence of your PM capabilities.

What the Capstone Project Actually Is

The capstone is Course 6 of 6. You're given a realistic project scenario—often something like "You're the PM for a non-profit launching a new website" or "You're managing the rollout of a new software feature for a tech company." The scenario includes constraints: a budget, a timeline, stakeholders with competing interests, and a scope that's somewhat ambiguous (like real projects).

Your task: create a project management plan as if you were actually running this project. The deliverables typically include:

• A project charter (project name, business case, goals, success criteria, stakeholders)
• A project schedule with milestones and task dependencies
• A resource plan (who does what, effort estimates)
• A risk register with mitigation strategies
• A stakeholder communication plan
• A final project closure document or retrospective

The capstone isn't a video to watch or a quiz to pass. It's a portfolio project. You're building artifacts that you'll actually show to hiring managers and use as evidence during job interviews.

The Grading Criteria: What Hiring Managers Care About

Google publishes a rubric for the capstone. Understand it deeply—these criteria are exactly what managers assess when they look at your project work:

Completeness: Did you deliver all required documents? Are they filled out, not half-baked? Hiring managers see incomplete capstones as a red flag: can this person actually finish projects?

Accuracy: Are your timeline estimates realistic? Does your risk register actually reflect the project scenario, or did you copy template language? Can you explain your choices? A PM who estimates 200 hours for a 3-month website redesign with 2 people shows they don't understand effort allocation.

Application of frameworks: Do you use the tools and language from the courses? Is your RACI matrix actually a RACI (not just a list of names)? Do you reference specific risk response strategies (avoid, mitigate, transfer, accept)? Hiring managers want to hear: "We identified 12 risks, prioritized by probability and impact, and chose mitigation strategies for the critical three." Not: "Risks might happen."

Clarity of communication: Can someone who hasn't taken the Google certificate understand your project documents? If your stakeholder communication plan is jargon-filled, that's a fail. PMs translate complexity into clarity. Your capstone should prove you can do that.

Realistic constraints: Did you actually work within the budget and timeline given, or did you ignore them? Real PM work is about trade-offs. If your capstone pretends constraints don't exist, it shows you don't understand the job.

Step-by-Step: How to Build Strong Capstone Deliverables

The Project Charter

Your charter is the foundation. Spend time here. It should be 1-2 pages and include:

A clear problem statement. Don't just say "Build a website." Say: "The non-profit's current website is 10 years old, loses donors due to poor UX, and can't process donations. We're rebuilding it to improve conversion by 25% and reduce support tickets by 40%."

Specific, measurable success criteria. "Website is launched" is not a criterion. "Website is launched on time and under budget, and donors report improved UX in post-launch survey" is. Include actual numbers: launch date, budget cap, adoption targets.

A stakeholder map. Not a list—a matrix showing each stakeholder's interest and influence. Sponsor (high/high) gets weekly updates. Developers (low/high) need technical clarity but less visibility into financials. Donors (low/interest) get launch announcements.

Assumptions and constraints. "We assume the design vendor will deliver mockups by March 1. We're constrained to a $50k budget and a 6-month timeline. We must use our existing hosting infrastructure." Be specific. Vague assumptions cause project failure.

The Project Schedule

Use a Gantt chart (Google Sheets, Excel, or free tools like Lucidchart) with realistic task breakdown. Include:

• Tasks broken down into chunks (not "Build website" but "Design homepage, Design product pages, Design checkout flow").
• Dependencies shown (Homepage design must finish before development starts).
• Resource assignments (Who does each task? Is one person overallocated?).
• Milestones for major deliverables (Design approved by April 1, development half-done by May 1, UAT launch by June 15).
• Realistic duration estimates (You researched website projects and found that design takes 6-8 weeks, not 2.)

Many candidates create schedules that are either too vague ("Phase 1: Build") or unrealistic (20 tasks each taking 1 day for a complex project). Study real project schedules. Ask: "Can one designer really produce a full mockup in 1 week?" If no, adjust. This is how hiring managers spot who's done real work vs. who hasn't.

The Resource Plan

Show who does what and why. Example:

• Project Manager: Full-time, oversees schedule, communicates with stakeholders, manages risks.
• Designer: 0.8 FTE, handles all visual design; needs to start early to unblock developers.
• Senior Developer: 1.0 FTE, leads architecture, code reviews; highest cost due to expertise.
• Junior Developer: 0.5 FTE, builds features under senior developer's guidance; lower cost, supports learning.
• QA: 0.4 FTE, starts testing mid-project to catch issues early; ramping up to 1.0 FTE during UAT phase.

Show effort estimates in person-hours. If your senior developer is $150/hr and 1.0 FTE for 6 months, that's roughly $180k labor (6 months × 4.3 weeks × 40 hrs/wk × $150). Does that fit your $50k budget? No? You've found a constraint. Revise: maybe the senior developer is 0.5 FTE (more junior dev to balance), or the timeline extends, or the scope shrinks. This is real PM work.

The Risk Register

Most candidates list risks as simple statements: "Design might be delayed." Instead, create a real register:

Notice: specific risks tied to the project context, realistic probabilities, and concrete response strategies. Not generic "bad things might happen" language. Hiring managers see this and think: "This person knows how to plan for reality."

The Stakeholder Communication Plan

Create a simple table:

Show that you understand different stakeholders need different messages at different cadences. The board doesn't need daily stand-up notes. Developers don't need quarterly financial reviews. This proves stakeholder management competency.

Common Capstone Mistakes (and How to Avoid Them)

Mistake 1: Treating it like a template exercise. You fill in every field but don't customize. "Assumptions: The project is feasible. Constraints: We have a budget." These are filler. Instead: "Assumptions: Design vendor will hit April 1 based on signed contract and weekly check-ins. Constraints: $50k budget with no contingency (tight) and 6-month timeline competing with Q3 sprint planning (high risk)." Be specific to your scenario.

Mistake 2: Unrealistic estimates. You schedule a full website redesign (design, development, QA, UAT) in 3 months with a team of 2. That's not feasible for a professional non-profit site, and hiring managers know it. Research similar projects. If your timeline is off, adjust scope or team size, and document why.

Mistake 3: Ignoring the budget constraint. You build a perfect schedule but never calculate labor costs. Then you add it up: it's $500k and your budget is $50k. You've just shown you can't manage to a constraint—a core PM skill. Always work backward from budget to see what's actually feasible.

Mistake 4: Vague risk responses. "Risk: Scope creep. Response: Prevent it." How? "Risk: Scope creep. Response: Establish a change control process where any scope additions go to Phase 2; communicate this at kickoff and in monthly steering meetings." The second is what a PM actually does.

Mistake 5: Generic language throughout. Your risk register, schedule, and charter could apply to any project. But your scenario is specific. Your capstone should feel tied to the non-profit's mission, the tech stack mentioned, the specific team roles described. Customization shows depth.

How to Present Your Capstone as Portfolio Evidence

When you finish the capstone, don't just submit it for a grade and forget it. Convert it into portfolio pieces.

Build a portfolio site. Use Notion, a personal website, or Google Drive. Create one page per artifact: Project Charter, Schedule, Risk Register, Communication Plan. For each, write a 2-3 sentence intro: "This project charter establishes goals and scope for a non-profit website redesign. Note the specific success criteria (25% donor conversion improvement) and the stakeholder matrix, which guided communication frequency throughout the project."

Anonymize as needed. If your capstone used a real organization, keep it. If it's fictional, say so: "This is a capstone project from the Google PM Certificate; the non-profit is fictional, but the constraints and team dynamics reflect real projects I've observed." Hiring managers understand these are exercises.

Prepare a 2-minute verbal summary. In interviews, you'll say: "I led a project to redesign a non-profit website. The main challenge was a tight 6-month timeline with a $50k budget and a team of 3. I created a detailed schedule with dependencies, identified 12 risks using an impact/probability matrix, and prioritized budget toward the highest-risk areas. We planned for potential scope creep from the board by establishing a change control process." This is the language of experienced PMs.

Reference it in your resume. Under "Projects" or "Portfolio," link to your capstone. In your Cover Letter: "I've completed the Google PM Certificate and built a full project management plan for a website redesign capstone, including charter, schedule, risk register, and stakeholder communication strategy. This capstone demonstrates my ability to synthesize multiple PM disciplines into actionable project work." Then link to your portfolio site.

The Capstone as Your Bridge to the First PM Job

Here's the truth: most people without work experience don't have PM portfolio pieces. Your capstone is one of the few artifacts you can show. Use it.

In interviews, when asked "Walk us through how you'd approach project planning," you can reference your capstone: "In my Google PM capstone, I built a project schedule with 30 tasks and identified key dependencies. For this role, I'd follow the same process: break deliverables into granular tasks, identify what must happen sequentially vs. in parallel, estimate effort, and build in contingency." You've just shown concrete methodology, not generic platitudes.

On your LinkedIn, mention the capstone and link to your portfolio. When recruiters see you've synthesized a full PM plan, not just watched videos, they take you seriously.

Related reading: Learn more about building a PM portfolio with your Google Certificate and how to highlight your capstone on your resume.

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.