Top Scrum Master Question for 2022

1. Differentiate Between Agile and Scrum.

Agile is a software development method that focuses on the adaptive delivery of requirements in an iterative, incremental manner. It's a framework that enables teams to deliver working software frequently and with high quality.

Scrum is an agile framework that provides a set of principles and practices to help teams develop software more effectively.

2. What do you mean by user stories in Scrum? What are the advantages of using them?

User stories describe a specific feature and its requirements without understanding how it should be implemented. They are used in Scrum to help focus on what the user is trying to achieve, and they help ensure that users build the product for users.

The advantage of using them is that they help to ensure that the right features get built and that features are developed in a way that allows users to understand what they do, why they do it, and how they do it.

3. How are user stories, epics, and tasks different?

User stories are the smallest unit of work that a single team member can complete.

An epic describes a single feature or story.

Tasks are the smallest unit of work that only one person can complete.

4. What do you mean by timeboxing in Scrum?

The timebox is a constraint that you place on the development team. The purpose of the timebox is to limit the amount of time spent on any given task and ensure that work is going to be used while waiting for other tasks to complete or considering other constraints. Timeboxing is a critical part of Scrum because it helps keep the development team focused on achieving their work as quickly as possible and helps them stay within their sprint goal.

5. What are the tools used in Scrum projects?

• Microsoft Azure DevOps
• Asana
• Jira
• Trello

6. What do you mean by 'Confidence Vote' in Scrum? Why is it important?

In Scrum, a team will have to release their product on time. If they don't meet the deadline, then they can be penalized. This is called a 'confidence vote. The team will vote on if they think they can meet the deadline or not. If they are confident they can reach the deadline, they can release their product and be confident in themselves.

The confidence vote is important because it helps teams know whether or not they have enough time to finish their project by the deadline. For example, suppose a team has a lot of work left to do. In that case, it is more likely that they won't make it in time for the next release date, and this could lead to them being penalized for not meeting their goal by missing deadlines which could lead to them losing money or even losing customers if someone else releases before them!

7. What do you understand about Scope Creep? How can Scope Creep be managed?

Scope creep is a common problem in agile development. "scope creeps" refers to adding new functionality, features, and requirements to a project after it has started. This can be a costly problem, as it can increase the project's scope without adding any value.

In Scrum, scope creep is managed by allocating time for each task and ensuring the team stays within their sprints. If a team member can't complete their task within their sprint, they should be removed from the sprint, and they will have no impact.

8. What is the role of a Scrum Master in a sprint retrospective?

A Scrum Master is a person who has the role of managing the Scrum project. They usually work in tandem with the Product Owner to help ensure that the project is successful and that everyone works together towards a common goal.

The Scrum Master has two prominent roles:

To help guide and coach the team through the Sprint review, helping them identify any issues they may have faced during their sprints and any improvements they want to make.

To help manage communication between stakeholders throughout the development process - is available to advise on how to deal with issues that may arise and step back and let others take control where appropriate.

9. What exactly do you mean by Sprint in Scrum?

Sprint is the term for the period you are working on your product. It can be any period from a few hours to several months, depending on your needs and how much work you want to do in that time.

A sprint is a self-organizing event with no fixed start or end date but rather a focus on achieving specific goals within a sprint. Sprint starts with planning and ends with a review, so it can be considered a cycle of events.

Scrum sprints are typically 2 weeks (1 week each way) long and take place every 2 weeks or when specific events occur, such as when something hits an important milestone or some other special occasion that requires team attention.

10. When should you use Waterfall over Scrum?

The reasons to use Waterfall over Scrum are :

First, Scrum is a framework, while Waterfall is a methodology. A waterfall can be applied to any project lifecycle, not just software development.

Second, the Agile Manifesto states that people and stakeholders should be involved early and often in the project lifecycle. But this is not possible when using Scrum because it needs an explicit process for communication between stakeholders and developers.

Third, Waterfall is better suited for large projects with clear goals, high-level planning, detailed specifications, and well-defined roles for all parties involved.

11. What are the Scrum Process Artifacts?

The Product Backlog lists all items needed for the product or feature. In addition, it contains all user stories, acceptance criteria, and other requirements for that particular item in the product backlog.

The Sprint Backlog contains all tasks necessary to complete each sprint to meet its goal(s). These tasks may include analyzing the current status, creating designs and prototypes, developing code or tests needed to test completed functionality according to user stories in the product backlog, etc.

The product increment is the new functionality added to the product during each iteration, i.e., after each sprint. This is done so that all stakeholders can see how far along you are in your progress toward delivering functionality and making changes based on feedback from stakeholders or customers.

12. Describe Scrumban?

Scrumban is a business management software that allows you to automate your daily tasks and give your employees more freedom.

With Scrumban, you can create simple or complex workflows to save time and increase efficiency. You can also use Scrumban to automate the most tedious parts of your business by creating scripts that will run on specific dates or times of the day.

This approach allows you to reuse scripts as much as possible without having to worry about constantly creating them from scratch each time you want to rerun them.

MCQ’s on Scrum

Who can be the best user proxy?

1. Agile coach
2. Scrum Master
3. Customers
4. Developer

When can a Sprint be canceled?

1. The Sprint items are no longer needed
2. Sprint can never be canceled
3. Information required to start the development is not available
4. Whenever the Product Owner say

How is Product Backlog Arranged?

1. High priority items on top, followed low-priority items
2. Large items at the top, small items at the bottom
3. Items are randomly arranged
4. Newer stories prioritized on top, followed by older stories

Who is responsible for ensuring that the scrum values and pillars are adhered to at all times?

1. Product Owner
2. Development Team
3. Scrum Master
4. None of above

Which one is not part of the Agile Manifesto?

1. Maximize utilization
2. Working Daily Together
3. Continuous Attention
4. Early & Continuous Delivery of Business Value

Should product backlog be ordered based on?

1. The complexity of the items being delivered
2. Size of the items being delivered
3. Value of the items being delivered
4. The risk associated with the items

Which of these is not a scrum pillar?

1. Adaptation
2. Focus
3. Transparency
4. Inspection

The Product Owner in a Scrum project?

1. Collaborates with the developers over prioritization of product backlog items, but the product owner has the final say
2. Creates a product backlog items but leaves prioritization to the business analyst
3. Collaborates with the developers over prioritization of product backlog items, but the developers have the final say
4. Has no control over the prioritization of product backlog items

Iterative development is NOT a good idea for?

1. Back end development
2. Front end development
3. Software development
4. Middleware development

What is the role of a tester in Scrum?

1. In Scrum, there is no such thing as a tester.
2. Bug hunting
3. Create test scenarios and test cases as needed.
4. Write scripts for automation

1. What is conveyed by the BurnDown chart?

1. The progress in the project.
2. The team's rate of doing work.
3. The team members' capabilities.
4. The amount of work that needs to be completed in relation to the amount of time available.