Brief test introduction
Are you looking for a Scrum Master to help your team get the most out of the Scrum framework? Whether you're seeking a full-time or part-time Scrum Master, this test will help you assess your candidate's knowledge of the Scrum framework. These questions will measure your candidate's understanding of the fundamentals of the Scrum framework, as well as their ability to help your team execute when following an agile approach. After this test, you'll have the answers you need to decide if your candidate can help your team be successful using the Scrum framework.
The Kandio Method
Kandio’s assessment tests let you assess the candidates, employees, agencies, or freelancers you have, and offers guidelines on which programmers to proceed with, and which ones to discard. Kandio will give you clear indications, so you can hire on proven candidates instead of empty talk.
How to use the test
We suggest that you use our tests before your interview process to know which ones to shortlist. The final Kandio report should be a piece of conversation with strong candidates, rather than a disqualifying process in a late-stage interview process.
Who can users use the test?
Ideal candidates for the test are
- Customers should use this test when evaluating the skills of a mid-level Scrum Master
- This test would work equally well for a full-time Scrum Master as well as for a part-time Scrum Master who is serving the Scrum Master role in addition to another role on the team (such as developer, tester, or designer)
- This test is designed for teams following the Scrum framework and is not ideal for customers evaluating team members for other agile frameworks, such as Kanban
- Scrum Masters interviewing for a full-time or part-time role with a team
- Scrum Masters with 2-3 years of experience
Which areas (chapters) will be covered in the test, and why was it chosen that way?
This chapter covers the underlying theories of the Scrum framework and how these theories relate back to Scrum.
Mid-level and above Scrum Masters should have a basic understanding of these concepts so they can best alter the practices of the Scrum framework to be successful in their unique organizations, while still preserving the underlying outcomes.
This chapter covers the key events of the Scrum framework: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
I’ve focused primarily on the desired outcomes of each event, as this should be the area of focus for a Scrum Master working with their team.
This chapter covers the 3 roles of the Scrum framework: Scrum Master, Product Owner, and Development Team.
The focus is on the responsibilities of each role as well as the interaction between the three roles. This chapter also pays particular attention to which roles are not traditionally found on a Scrum team.
This chapter covers the 3 artifacts produced by a team using the Scrum framework: Product Backlog, Sprint Backlog, and Increment.
The focus is on the goal of each artifact, as well as which role is primarily responsible for its creation.
Complementary Scrum Techniques
This chapter focuses on techniques often used by teams following the Scrum framework, but that is not actually part of the core Scrum framework.
Specifically, this chapter addresses User Stories and common visualization tools such as burndown charts.