Skip to content

Module 3 Challenge :Agile Project Management (Google Project Management Professional Certificate) Answers 2025

1. Why is the Product Backlog a “living artifact”?

✅ The Product Owner can add items at any time.
❌ Team members only add at the end of a Sprint
❌ Product Owner only adds at the end of a Sprint
❌ Stakeholders can add items at any time

Explanation:
The Product Backlog is constantly evolving because the Product Owner can update it anytime.


2. Including a clear Definition of Done makes a user story _____.

❌ independent
❌ negotiable
❌ valuable
✅ estimatable

Explanation:
Clear DoD helps the team understand effort → makes the story estimatable (I.N.V.E.S.T.).


3. Private estimates prevent influencing others. This avoids what?

❌ Build team trust
✅ Avoid anchoring bias
❌ Lead to effort discovery
❌ Promote inclusivity

Explanation:
Anchoring bias = when the first estimate influences others. Private estimates avoid this.


4. Setting the initial Sprint duration refers to what Scrum concept?

❌ Time frame
❌ Schedule
❌ Interval
✅ Timebox

Explanation:
Scrum uses timeboxes to define fixed lengths for Sprints and events.


5. Which event includes velocity, availability, task planning?

❌ Sprint Review
❌ Sprint Retrospective
✅ Sprint Planning
❌ Daily Scrum

Explanation:
Sprint Planning determines capacity, velocity, availability, and task ownership.


6. What typically occurs during the Sprint Review? (Select all)

❌ Synchronize & prioritize team activities
❌ Discuss how to work better as a team
✅ Explore which items should be considered done in the Backlog
✅ Demonstrate and inspect the product

Explanation:
Sprint Review focuses on inspecting the increment and adjusting the product backlog.


7. How can the Scrum Master help a quiet team member participate? (Select all)

✅ Quiet journaling for first 10 minutes
❌ Ask them to speak first
❌ Make no changes
✅ Pair team members for discussion

Explanation:
Creating psychological safety requires gentle methods—not forcing someone to speak.


8. Overall goal of a burndown chart?

✅ Keep the team aware of how they’re doing against their goals
❌ Quantify individual performance
❌ Compare productivity among teams
❌ Communicate with outside stakeholders

Explanation:
Burndown shows team progress vs. remaining work.


9. Compare Kanban board vs. Scrum board

❌ Scrum board is more visual
❌ Kanban is better for tracking Sprint tasks
✅ They’re essentially the same tool with minor differences
❌ Teams have little use for Kanban

Explanation:
Both visualize work; main differences = workflow vs. sprint focus.


10. Tools that make progress visible embody which Scrum pillar?

❌ Inspection
✅ Transparency
❌ Adaptation
❌ Commitment

Explanation:
Transparency = making work visible, clear, and accessible to all team members.


🧾 Summary Table

Q# Correct Answer(s) Key Concept
1 PO can add anytime Backlog evolution
2 Estimatable I.N.V.E.S.T.
3 Avoid anchoring bias Estimation behavior
4 Timebox Scrum time limits
5 Sprint Planning Capacity & planning
6 Done items, demo product Sprint Review
7 Quiet journaling, pairing Inclusivity
8 Track progress vs goals Burndown chart
9 Same tool, minor differences Kanban vs Scrum
10 Transparency Scrum pillars