Unlock hundreds more features
Save your Quiz to the Dashboard
View and Export Results
Use AI to Create Quizzes and Analyse Results

OR
Sign inSign in with Facebook
Sign inSign in with Google
Quizzes > Quizzes for Business > Technology

Scrum Master Onboarding Knowledge Test Quiz

Evaluate Your Scrum Master Onboarding Skills

Difficulty: Moderate
Questions: 20
Learning OutcomesStudy Material
Colorful paper art depicting a quiz on Scrum Master Onboarding Knowledge Test.

Jump into the Scrum Master Onboarding Knowledge Test to sharpen your agile leadership skills and validate your understanding of key Scrum ceremonies and roles. Aspiring Scrum Masters and team leads will find this 15-question quiz both challenging and insightful - plus it's fully customizable in our editor. Ready to deepen your Scrum toolbox? Check out the Scrum Fundamentals Quiz for core concepts and explore the Team Onboarding Knowledge Quiz to broaden your perspective. Discover more free quizzes to build momentum in your agile journey.

What is the primary responsibility of a Scrum Master during team onboarding?
Assign tasks to team members
Coach the team on Scrum principles and practices
Define the project scope
Manage resource allocation
A Scrum Master serves as a coach and facilitator to help the team understand Scrum values and processes during onboarding. They do not assign tasks or manage resources. Defining project scope is the Product Owner's responsibility.
Which Scrum artifact contains all of the planned work for the product?
Sprint Backlog
Product Backlog
Increment
Definition of Done
The Product Backlog is the single source of work items for the product, maintained by the Product Owner. The Sprint Backlog is a subset selected for a Sprint, and the Increment is completed work. The Definition of Done is a quality checklist.
What is the main purpose of the Daily Scrum?
To report status to the project manager
To plan the work for the next 24 hours
To solve detailed design problems
To present the increment to stakeholders
The Daily Scrum is a timeboxed event for the Development Team to synchronize and create a plan for the next 24 hours. It is not a status report, detailed problem-solving session, or stakeholder demo. Detailed issues are raised as impediments.
Who is primarily responsible for prioritizing items in the backlog?
Product Owner
Scrum Master
Stakeholders
Development Team
The Product Owner is accountable for maximizing product value by ordering the Product Backlog. The Scrum Master facilitates but does not prioritize, and the Development Team and stakeholders provide input but do not own prioritization.
What best describes a Sprint Goal?
A detailed list of tasks for the Sprint
A metric for team velocity
A documentation of the Definition of Done
A short statement of what the team aims to achieve in the Sprint
A Sprint Goal is a concise objective that guides the Development Team during the Sprint. It is neither a task list nor a velocity metric, and it is separate from the Definition of Done. It provides focus and alignment.
During Sprint Planning, how does a Scrum Master best support the team?
By estimating story points alone
By assigning work to individual developers
By facilitating discussion between the Product Owner and Development Team
By approving the final Sprint Goal
The Scrum Master ensures the planning meeting runs smoothly by facilitating dialogue and guiding the team through Scrum practices. They do not assign tasks, estimate alone, or approve goals. The team collaboratively defines the Sprint Goal.
Which artifact demonstrates a usable, potentially shippable product increment?
Product Backlog
Increment
Sprint Backlog
Burn-down Chart
The Increment is the sum of all completed Product Backlog items at the end of a Sprint and must be potentially releasable. Backlogs and charts track work but do not represent the actual deliverable.
Which prioritization technique uses relative weight of job duration and cost of delay?
SWOT analysis
MoSCoW
WSJF
Fishbone diagram
Weighted Shortest Job First (WSJF) calculates a priority score by dividing cost of delay by job duration. SWOT and MoSCoW are different strategic and categorical prioritization approaches. Fishbone diagram is for root cause analysis.
Which communication style encourages open and honest feedback among team members?
Passive
Assertive
Passive-aggressive
Aggressive
Assertive communication balances respect for others with clarity of intent, fostering transparency and constructive feedback. Aggressive or passive styles hinder open dialogue. Passive-aggressive creates hidden conflict.
Which retrospective activity helps identify what to start, stop, and continue doing?
MoSCoW
Burn-up Chart
Start-Stop-Continue
5 Whys
Start-Stop-Continue is a structured exercise that guides teams to list practices to begin, end, or maintain. The 5 Whys is root cause analysis, MoSCoW is prioritization, and the Burn-up Chart tracks progress over time.
If a stakeholder requests a change mid-Sprint, what should the Scrum Master do first?
Add the change directly to the Sprint Backlog
Politely refuse the request
Direct the stakeholder to the Product Owner
Call an emergency Sprint Review
The Scrum Master redirects change requests to the Product Owner so that they can evaluate priority and impact. The Scrum Team should not alter the Sprint Backlog mid-Sprint without PO agreement. Emergency Reviews are not standard practice.
Which metric provides the daily progress of work remaining in a Sprint?
Cycle Time
Burn-down Chart
Burn-up Chart
Velocity
The Sprint Burn-down Chart shows the total effort remaining in the Sprint at each day's end. Velocity measures completed work over multiple Sprints. Burn-up tracks delivered work relative to scope, and Cycle Time tracks individual item flow.
What facilitation technique can help a team reach a quick decision?
Random assignment
Waterfall Gantt chart
Consensus voting
Use of a RACI matrix
Consensus voting allows team members to express agreement or concerns and quickly converge on a decision. Random assignment isn't deliberative, Gantt charts are planning tools, and RACI defines roles rather than facilitating decisions.
How can a Scrum Master help ensure backlog items are ready for a Sprint?
Allowing the team to pick any items
Writing all user stories alone
Coaching the Product Owner on the DEEP principle
Ignoring backlog refinement
The DEEP acronym (Detailed appropriately, Emergent, Estimated, Prioritized) guides well-prepared Product Backlogs. Writing stories alone or ignoring refinement undermines collaboration. The team should pick from a groomed backlog.
Which practice helps drive continuous improvement beyond Sprint retrospectives?
Expanding the Definition of Done
Implementing a code freeze
Encouraging frequent feedback loops
Increasing Sprint length
Frequent feedback loops, such as informal reviews and pair programming, reinforce a culture of continuous improvement outside retrospectives. Code freezes and longer Sprints hinder agility. The Definition of Done guides quality but isn't a feedback loop.
In a distributed Scrum team, what is the most effective way to conduct the Daily Scrum?
Allow team members to skip if busy
Send an email summary at end of day
Use video conferencing and timebox the meeting
Postpone until an in-person meeting
Video conferencing maintains real-time interaction and transparency for distributed teams, and strict timeboxing keeps the meeting focused. An email summary or skipping members reduces collaboration. Postponing loses daily synchronization.
Which tool is most appropriate for root cause analysis when a team faces recurring defects?
Velocity chart
PERT chart
SWOT analysis
Fishbone (Ishikawa) diagram
The Fishbone diagram systematically explores potential causes of a problem and is well-suited for recurring defects. PERT charts plan schedules, velocity charts track throughput, and SWOT analyzes strategic factors rather than root causes.
A stakeholder is concerned about product progress. Which artifact offers the clearest view of overall progress?
Burndown Chart
Product Backlog
Sprint Backlog
Burn-up Chart
A Burn-up Chart shows both total scope and work completed over time, providing stakeholders with clear progress and scope-change visibility. A Burndown Chart only shows work remaining. Backlogs list work but don't visualize progress.
A team's velocity has steadily declined over several Sprints. How should the Scrum Master address this?
Assign more developers
Reduce the Definition of Done
Inspect and remove impediments
Extend Sprint length
Declining velocity often signals impediments or process issues. The Scrum Master should help the team identify and remove those impediments. Changing Sprint length or team size disrupts stability, and reducing the Definition of Done lowers quality.
Which measure can help a Scrum Master track the effectiveness of retrospective action items?
Team size change
Hours spent in meetings
Number of action items completed per Sprint
Total number of user stories delivered
Tracking the number of action items completed per Sprint directly measures how well the team implements improvements. User stories delivered and meeting hours don't reflect improvement adoption. Team size is unrelated.
0
{"name":"What is the primary responsibility of a Scrum Master during team onboarding?", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"What is the primary responsibility of a Scrum Master during team onboarding?, Which Scrum artifact contains all of the planned work for the product?, What is the main purpose of the Daily Scrum?","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}

Learning Outcomes

  1. Identify core Scrum Master responsibilities during onboarding
  2. Analyse essential Scrum artifacts and their uses
  3. Demonstrate facilitation of key Scrum ceremonies
  4. Apply effective communication strategies with stakeholders
  5. Evaluate tools and techniques for backlog prioritization
  6. Master retrospective and continuous improvement practices

Cheat Sheet

  1. Core Responsibilities of a Scrum Master - As a Scrum Master, you're the team's go-to guide, ensuring everyone follows Scrum principles and keeps the momentum high. You'll facilitate key events like sprint planning and daily stand-ups, coach the team on Agile best practices, and swoop in to remove any blockers. Embrace your inner problem-solver and cheerleader rolled into one! GeeksforGeeks: Scrum Artifacts
  2. Understand Scrum Artifacts - Scrum artifacts are your team's roadmap, to-do list, and proof of progress all rolled into one. The Product Backlog houses every feature idea, the Sprint Backlog pinpoints the tasks for the upcoming sprint, and the Increment is your shippable work at sprint's end. Master these, and you'll have a clear view of where you're headed! Scrum.org: Scrum Artifacts
  3. Facilitate Scrum Ceremonies - Scrum ceremonies are your secret sauce for team alignment and continuous improvement. From Sprint Planning (setting the sprint's course) to Daily Stand-ups (quick status updates), Sprint Reviews (showing off the work), and Retrospectives (identifying improvements), each event keeps the engine running smoothly. Host them with energy and a sprinkle of fun! GeeksforGeeks: Scrum Artifacts
  4. Communicate with Stakeholders - Clear, open communication is the glue that holds your project together. Regular check-ins and transparent updates help manage expectations, gather timely feedback, and keep everyone on the same page. Think of stakeholders as your extended team - keep them in the loop and they'll cheer on your successes! GeeksforGeeks: Scrum Artifacts
  5. Backlog Prioritization Techniques - Not all tasks are created equal, so use methods like MoSCoW (Must have, Should have, Could have, Won't have) or value-based prioritization to focus on what truly matters. By ranking backlog items, you ensure the team tackles the highest value work first, delivering maximum impact each sprint. It's like triaging your to-do list for superhero efficiency! GeeksforGeeks: Scrum Artifacts
  6. Conduct Effective Retrospectives - Retrospectives are your team's growth engine - time to reflect on wins, spot roadblocks, and agree on improvements. Encourage open, honest feedback and turn insights into actionable steps. With each retrospective, your team becomes sharper, faster, and more collaborative - making every sprint a learning adventure! GeeksforGeeks: Scrum Artifacts
  7. Definition of Done (DoD) - The Definition of Done is your quality checkpoint before any increment goes live. It lists all criteria - testing, documentation, reviews - that ensure work is truly complete. A crystal-clear DoD prevents misunderstandings, keeps quality high, and lets your team ship confidently! Scrum.org: Scrum Artifacts
  8. Read and Interpret Burndown Charts - Burndown charts are your sprint's heartbeat, showing remaining work over time. By tracking progress visually, you can spot slowdowns early and adjust tasks or scope before it's too late. Think of it as a game-time scoreboard - keep an eye on it to stay on course! GeeksforGeeks: Scrum Artifacts
  9. Define and Share the Product Vision - A powerful Product Vision inspires the team and aligns stakeholders toward a common goal. It's your north star, guiding decisions and prioritizations throughout the project. Craft a clear, compelling vision, share it often, and watch motivation soar! GeeksforGeeks: Scrum Artifacts
  10. Set a Strong Sprint Goal - The Sprint Goal is your sprint's mission statement - concise, achievable, and aligned with the Product Vision. It gives the team a shared focus and helps everyone make trade-off decisions when surprises pop up. A well-defined goal turns busy work into meaningful progress! GeeksforGeeks: Scrum Artifacts
Make a Quiz (FREE) Copy & Edit This Quiz Create a Quiz with AI

Technology Quizzes

Powered by: Quiz Maker