PSM 1 Sample Questions to Master Scrum Certification Exam
- CertiMaan
- Oct 16, 2025
- 12 min read
Updated: Jan 19
Sharpen your Scrum knowledge with these expertly designed PSM 1 sample questions and real-time practice tests. Tailored for the Professional Scrum Master 1 (PSM I) certification, this question set covers Scrum roles, events, artifacts, and principles aligned with the Scrum Guide. Whether you're looking for a PSM 1 practice exam, mock test, or updated dumps, these resources simulate the real exam environment to boost your confidence and accuracy. Perfect for aspiring Scrum Masters and agile professionals, this content helps you identify knowledge gaps, strengthen core concepts, and pass the PSM 1 exam on your first attempt. Get ready with top-quality preparation material and practice smarter, not harder.
PSM 1 Sample Questions List :
1. A key stakeholder starts using the product several Sprints in and expresses quality concerns to the Product Owner, who informs the Scrum Master. What are the Scrum Master’s two best responses?
* Raise testing issues with testers for adjustments
* Defer discussion to the next Sprint Retrospective
* Tell the Product Owner that Developers set quality standards
* Urge the Product Owner to add quality items to the Product Backlog and share stakeholder concerns with Developers
* Guide the Product Owner on addressing this with Developers
2. When can Developers cancel a Sprint?
* If selected Product Backlog items become unreleasable
* When functional expectations are unclear
* They can’t—only the Product Owner can
* If the Product Owner is often absent
3. What are three ways Scrum fosters self-organization?
* By barring stakeholders from the development space
* By letting Developers choose their Sprint tasks
* By eliminating titles for Developers
* By offering a simple framework
* By forbidding documentation
4. When must a new working software Increment be ready for transparency?
* Before the release Sprint
* After acceptance testing
* Every 3 Sprints
* At each Sprint’s end
* When the Product Owner requests it
5. When does a Sprint conclude?
* When the Product Owner declares it finished
* When its timebox runs out
* When all tasks are done
* When all Product Backlog items are 'Done'
6. Must a product Increment be released to production each Sprint?
* FALSE
* TRUE
7. Which roles belong to a Scrum Team?
* Customers
* Developers
* Product Owner
* Users
* Scrum Master
8. What do self-organizing Developers decide?
* Release timing based on progress
* Sprint Review stakeholders
* How to best execute their work
* Sprint duration
* Product Backlog order
9. Is it true that cross-functional teams should specialize in one system layer or component?
* FALSE
* TRUE
10. What’s the Scrum Master’s role during the Daily Scrum?
* All of the above
* Train Developers to keep it within 15 minutes
* Lead Developer discussions
* Ensure all three questions are answered
* Manage equal speaking time
11. What best characterizes Scrum?
* A recipe for software development best practices
* A comprehensive software development methodology
* A framework for tackling complex products in dynamic environments
* A predictable process aligned with Scientific Management
12. What does a timeboxed event imply?
* A minimum duration is set
* A maximum duration is enforced
* It must occur by a deadline
* It happens at a fixed time
13. What two behaviors reflect a Scrum Team’s commitment?
* Work late to complete all tasks
* Assist fellow Scrum Team members
* Always meet Sprint forecasts
* Deliver top-quality effort
14. Who ensures Product Backlog items meet the Definition of 'Done'?
* The Scrum Team
* QA Specialists
* The Developers
* The Scrum Master
* The Product Owner
15. What three questions do Developers address in the Daily Scrum?
* Are there impediments blocking me or the team from the Sprint Goal?
* How’s the Sprint going?
* What’s my plan for tomorrow?
* Why was I delayed?
* What did I do yesterday to aid the Sprint Goal?
* What will I do today to support the Sprint Goal?
16. What expertise must the Scrum Team have?
* Finish the project within Product Owner’s time and budget
* Conduct all testing with extra tools
* Develop the product (no testing) for handoff
* Convert Product Backlog items into a valuable Increment
17. What best defines a software Increment?
* An automated test suite for past functionality
* UML diagrams for future features
* A task breakdown for future Sprints
* Usable new features enhancing prior deliveries
* A new UI design for existing features
18. What three purposes does the Definition of Done serve?
* Outline purpose, objective, and timebox of Scrum events
* Enhance transparency
* Establish a common understanding of completed work
* Assist Developers in Sprint item selection
* List tasks to finish the Sprint
19. How should a Scrum Master split 120 people into multiple Scrum Teams?
* Seek management’s help
* Group by skills across layers (e.g., Front End, Database, UI)
* Ask the Product Owner for assistance
* Let the group self-divide into teams
20. When does the second Sprint begin?
* After customer acceptance of the first Sprint
* Once architectural changes are approved
* After selecting the second Sprint’s Product Backlog
* Right after the first Sprint ends
21. Are a Product Owner and Scrum Master mandatory for every Scrum Team?
* False—Scrum Master is optional if not requested
* True—Their involvement affects outcomes
* True—Both must be fully dedicated
* False—A skilled team member can replace the Product Owner
22. How does a Scrum Master keep Developers at peak productivity?
* By aiding Developer decisions
* By enforcing meeting schedules
* By clearing impediments
* By prioritizing high-value features
23. What are three ways Scrum supports self-management?
* By stripping titles from Scrum Team members
* By the team selecting Sprint tasks
* By removing titles for team members
* By the Scrum Master shielding the team from disruptions
* By being a lightweight framework
24. What does cross-functionality mean for Developers?
* A virtual team of analysts, architects, and testers
* Individuals with diverse skills for Increment delivery
* Collaboration with external specialists
* Inclusion of analysts and testers in the team
25. If a Scrum Team disputes agile practices, what should the Scrum Master do?
* Consult an external agile coach
* Refer team members to HR
* Involve the whole Scrum Team in decisions
* Use coaching with open questions and listening
26. What three goals does the Definition of 'Done' achieve?
Provides a template for technical documentation
Controls Developer task completion
Guides forecasting in Sprint Planning
Specifies Increment release readiness
Tracks item completion percentage
Ensures transparency at Sprint Review
27. What’s the Product Owner’s role in a Sprint Retrospective?
Report discussions to stakeholders
Skip the event
Gather Product Backlog requirements
Participate as a team member
28. After nine Sprints, a new Product Owner joins, unsure of their role. What two tasks define their Scrum responsibilities?
Supplying Developers with detailed specs
Writing functional test cases
Engaging with stakeholders
Detailing features as Use Cases
Prioritizing highest-value functionality
29. What are two key outcomes of the Daily Scrum?
An updated Scrum board for stakeholder visibility
New impediments for the Scrum Master to address
Task updates for the Scrum Master’s next-day plan
Agreement on priority work for Sprint Goal progress
A status update for management
30. Who is responsible for clearly defining Product Backlog items?
The business analyst
The Scrum Master
The Product Owner
The Project Manager
31. What comprises a Scrum Team?
Customers
Users
Developers
Project Managers
One Product Owner
One Scrum Master
32. Why does the Product Owner insist Developers follow the Definition of Done?
To predict deliveries over future Sprints
To monitor Story Point commitments
To forecast team productivity
To gain visibility into Sprint outcomes
33. Who determines how many Product Backlog items Developers take for a Sprint?
The Developers
The Scrum Team
Project Managers
The stakeholders
The Product Owner
The Scrum Master
34. When should a Sprint Retrospective occur?
At the end of a project’s last Sprint
Only when the team requests it
At each Sprint’s start
At each Sprint’s end
35. Are cross-functional teams designed for one technical layer only (e.g., GUI, database)?
FALSE
TRUE
36. What do self-managing Developers oversee?
Sprint length
Sprint Backlog
Sprint Review invitations
Product Backlog priority
Increment release
37. During a Sprint Retrospective, the team flags high-priority process improvements. What’s the best approach?
Add one to the Sprint Backlog
Skip improvements if things are smooth
Add one to the Product Backlog
Scrum Master picks one for the Sprint Backlog
38. Should all Increments from multiple Scrum Teams on one product be integrated each Sprint?
No—too hard, save for a hardening Sprint
Yes—but only for dependent teams
No—teams work separately
Yes—to fully inspect progress
39. How do multiple Scrum Teams select Product Backlog items from a shared backlog?
The Product Owner assigns them
Each team gets its own backlog
Teams split items equally
Developers coordinate with the Product Owner
Highest-velocity team chooses first
40. Who ensures Product Backlog items align with the Definition of Done?
The Testing Team
The Scrum Master
The Developers
The Scrum Team
The Product Owner
41. What’s the goal of a Sprint Review?
To boost team morale
To assess team activities and processes
To evaluate project validity
To review the Increment with stakeholders and gather feedback
42. Which three Scrum events are feedback loops?
Sprint Review
Sprint Retrospective
Refinement Meeting
Release Planning
Daily Scrum
43. What advice should a Scrum Master give a Product Owner on estimating in Scrum?
Estimates come from those doing the work
PBIs require story points
Scrum prohibits estimating
Product Owner estimates
44. If the Definition of Done requires user documentation but technical writers are scarce and external, what should the Scrum Team do?
Form a separate writer team for Product Owners
Wait for a writer to join the team
Have Developers write the documentation
Delay documentation until the final Sprint
45. What might Developers deliver at Sprint’s end?
Failing unit tests for next Sprint planning
Software with minor bugs
A document per Scrum Master request
A 'Done' working software Increment
46. When Developers struggle with a functional requirement and can’t deliver a working Increment, what’s their next step?
Work with the Product Owner to find viable solutions
Add a specialist to the team
Partially finish and review later
Push the work to a future Sprint
47. How should 100 people be split into Scrum Teams per Scrum theory?
Rotate teams each Sprint for knowledge spread
Use past collaboration from allocation
Group self-organizes with product and Scrum insight
Assign via skill and experience matrix
48. What’s true about Sprint length?
Extends until all work is done
Must be one month or less
Set in Sprint Planning based on planned features
Varies with work selected
49. Is the Sprint Goal, like the Sprint Backlog, an outcome of Sprint Planning?
TRUE
FALSE
50. What’s true about the Sprint Backlog as a Sprint Planning result?
It’s the Scrum Team’s Sprint plan
Product Owner orders it
It lists all tasks exhaustively
Each item has an owner
51. How does Scrum encourage self-organization in three ways?
By removing Developer titles
By keeping stakeholders out of the work area
By being a lightweight framework
By banning documentation
By Developers picking Sprint work
52. Five new Scrum Teams work on one product, and some Developers ask how to align with others. What’s the Scrum Master’s action?
Merge Sprint tasks into a unified plan
Teach them to coordinate for an integrated Increment
Guide the Product Owner on overlap-free ordering
Check team Sprint Backlogs daily
53. At the fifth Sprint Review, stakeholders are frustrated, feeling the product won’t meet needs or budget. What likely caused this?
Stakeholders couldn’t prioritize Product Backlog items
Stakeholders skipped Sprint Reviews
Product Owner didn’t update stakeholders on progress
Poor engagement with the PMO
54. What two tasks does a Product Owner perform during a Sprint?
Prioritize Developer Sprint Backlog work
Collaborate with stakeholders
Update the Sprint burndown chart
Run the Daily Scrum
Address Developer questions on Sprint items
55. Who makes up the Scrum Team?
Project Manager
Scrum Master
All of the Above
None of the above
Developers
Product Owner
56. What do burndown charts measure?
Individual Developer output
Total project cost to date
Work remaining over time
Delivered business value
57. If the Product Owner isn’t engaging with Developers, what should the Scrum Master do?
Coach the Product Owner on Scrum values and delivery
Raise it in the Sprint Retrospective
Appoint a proxy Product Owner
Escalate to the Product Owner’s manager
58. If the Daily Scrum shifts to every 2-3 days, what three issues arise?
Slower impediment resolution
Missed chances to adjust the Sprint Backlog
Product Owner struggles to report progress
Excessive Scrum board updates
Inaccurate Sprint planning
Scrum Master can’t update Gantt charts
59. What does 'Done' mean for a Sprint Increment?
Any quality the Product Owner sets
Nothing left per the Definition of Done
Ready for user release
Developers agree to any work
60. What phrase best captures a Product Owner?
Value optimizer
Team manager
Requirements engineer
Liaison between Developers and customers
61. Who ensures Product Backlog items are clearly expressed?
The Scrum Master or delegated to Developers
A business analyst for the Product Owner
The Product Owner
The Scrum Master
62. Who initiates the Daily Scrum?
The last build breaker
The token holder
The Scrum Master to enforce timeboxing
The latest arrival to encourage punctuality
The Developers
63. Can a Scrum Team only meet stakeholders at the Sprint Review?
TRUE
FALSE
64. Is it true that multiple Scrum Teams on one product share a single Product Backlog?
TRUE
FALSE
65. Which two team-forming methods align with Scrum principles?
Managers reassign current staff
Chief Product Owner sets team structure
Managers collectively assign teams
Group self-forms into Scrum Teams
Existing teams suggest their organization
66. Who needs the most updates on Product Goal progress?
The Scrum Master
The Developers
The Project Manager
Stakeholders
The Product Owner
67. What’s a Product Owner’s key duty during a Sprint?
Answer Developer questions on Sprint items
Monitor meeting timeboxes
Lead the Daily Scrum
Prioritize Sprint Backlog work
Update management on progress
68. When does the next Sprint start?
Immediately after the previous Sprint ends
When the Scrum Master approves
When the Product Owner is prepared
After the next Sprint Review
69. What two factors guide Sprint length decisions?
Uncertainty in technology used
Organizational mandate for uniform lengths
Risk of stakeholder disconnect
Frequency of team changes
70. As a new Scrum Master for six teams on one product, what two conditions should you target?
Each team with its own Product Backlog
Six Product Owners under a chief
One Product Owner per team
One shared Product Backlog
A single Product Owner
71. How does the Scrum Master ensure effective Developer-Product Owner communication?
Arrange meetings with the Scrum Team and Project Managers
Oversee and encourage direct collaboration
Act as an intermediary
Educate the Product Owner on tech details
Mentor Developers on business goals
72. Does a healthy Scrum Team require at least one Release Sprint, possibly more?
TRUE
FALSE
73. What should the Scrum Master do if the Product Owner struggles with Product Backlog ordering?
Provide a pre-ordered backlog
Help the Product Owner focus on value maximization
Push for Developer input on feasibility
Suggest Developers order it
Propose extending the Sprint
74. When should Developers update the Definition of 'Done'?
During Sprint Planning
Before a new project
During the Sprint Retrospective
Before a new Sprint
75. What three phrases best describe the Definition of Done’s purpose?
Guides Sprint Planning forecasts
Ensures transparency at Sprint Review
Defines Increment release readiness
Verifies Developer task completion
Tracks item completion percentage
Templates technical documentation
FAQs
1. What is the Professional Scrum Master (PSM) certification?
The PSM is a globally recognized certification from Scrum.org that validates your knowledge of Scrum principles and your ability to apply them effectively.
2. How do I become a Professional Scrum Master?
You need to prepare for Scrum concepts, register for the exam through Scrum.org, and pass the assessment.
3. What are the eligibility requirements for the PSM exam?
There are no formal prerequisites; anyone with interest in Scrum can take the exam.
4. How much does the Professional Scrum Master certification cost?
The cost for PSM I is around $150 USD per attempt. Higher levels (PSM II and III) cost more.
5. How many questions are in the PSM exam?
PSM I: 80 questions
PSM II: 30 questions
PSM III: 34 essay-based questions
6. What is the passing score for the Professional Scrum Master exam?
PSM I: 85%
PSM II: 85%
PSM III: 85%
7. How long is the PSM exam and what is the format?
PSM I & II: 60 minutes, multiple-choice online exam
PSM III: 120 minutes, essay-based online exam
8. What topics are covered in the Professional Scrum Master certification?
Scrum principles, roles, events, artifacts, agile mindset, and servant leadership.
9. How difficult is the Professional Scrum Master exam?
PSM I: Moderate for beginners
PSM II & III: Advanced, requiring deeper Scrum experience
10. How long does it take to prepare for the PSM exam?
On average, 2–6 weeks depending on prior Scrum knowledge and experience.
11. Are there any Professional Scrum Master sample questions or practice tests available?
Yes, Scrum.org provides free sample assessments, and CertiMaan offers practice tests and dumps.
12. What is the validity period of the PSM certification?
The PSM certification has lifetime validity and does not require renewal.
13. Can I retake the Professional Scrum Master exam if I fail?
Yes, but you must purchase a new attempt from Scrum.org.
14. Which PSM level should I choose: PSM I, PSM II, or PSM III?
PSM I: For beginners or entry-level Scrum Masters
PSM II: For experienced practitioners
PSM III: For experts and advanced professionals
15. What jobs can I get with a Professional Scrum Master certification?
Scrum Master, Agile Coach, Product Owner, Agile Project Manager, or Delivery Manager.
16. How much salary can a Professional Scrum Master earn?
Certified Scrum Masters often earn between $80,000–$120,000 annually, depending on region and role.
17. Is the PSM certification worth it?
Yes, it boosts your career in agile environments and enhances credibility with employers.
18. What is the difference between PSM and CSM certifications?
PSM (Scrum.org): Lifetime validity, exam-only approach.
CSM (Scrum Alliance): Requires training + exam, renewable every 2 years.
19. What are the best study materials for the Professional Scrum Master exam?
Scrum Guide (official), Scrum.org open assessments, and CertiMaan practice tests.
20. Where can I register for the Professional Scrum Master certification exam?
You can register directly on the official Scrum.org website.

Comments