200+ Scrum Master Interview Questions and Answers

As a Scrum Master, I would handle the situation by following these steps:

• Assess the impact of the developer's absence on the critical user story

• Communicate with the team and stakeholders about the situation

• Identify if there are any other team members who can take over the work

• If no immediate replacement is available, prioritize the critical user story and adjust the sprint plan accordingly

• Work with the Product Owner to manage expectations and potentially reprioritize other us...read more

The three pillars of Scrum are transparency, inspection, and adaptation. They are interrelated and support the Scrum framework.

• Transparency ensures that all information is visible and accessible to the team, stakeholders, and customers.

• Inspection involves regularly reviewing the progress, artifacts, and processes to identify any deviations or issues.

• Adaptation refers to making necessary changes based on the inspection results to improve the product and the process.

• These pilla...read more

Velocity is the amount of work completed in a sprint, while capacity is the amount of work a team can handle in a sprint.

• Velocity is a measure of the team's productivity in completing user stories or tasks in a sprint.

• Capacity is the amount of work a team can handle in a sprint, taking into account factors such as team size, availability, and skill level.

• Velocity is calculated by dividing the total number of story points completed in a sprint by the length of the sprint in da...read more

Poker is an estimation technique used in Agile project management. Fibonacci series is used for story points to reflect uncertainty.

• Poker is a collaborative estimation technique where team members assign story points to user stories.

• It helps in determining the effort required to complete a user story.

• Fibonacci series (0, 1, 2, 3, 5, 8, 13, etc.) is used to reflect the uncertainty and complexity of the work.

• Larger numbers in the Fibonacci series indicate higher uncertainty and...read more

To plan the capacity for a sprint, consider team velocity, individual availability, and any external factors.

• Calculate the team's velocity by reviewing past sprints and measuring the average number of story points completed.

• Consider individual team member availability, taking into account vacations, holidays, and other commitments.

• Factor in any external dependencies or constraints that may impact the team's capacity, such as shared resources or dependencies on other teams.

• Adj...read more

The principles of Agile are a set of values and beliefs that guide the Agile methodology.

• Customer satisfaction is the highest priority

• Welcome changing requirements, even late in development

• Deliver working software frequently

• Collaboration between business people and developers

• Build projects around motivated individuals

• Face-to-face conversation is the best form of communication

• Working software is the primary measure of progress

• Maintain a sustainable pace

• Continuous attention to ...read more

Methodology refers to a set of principles and guidelines for a specific process, while framework is a structure that provides a foundation for a process.

• Methodology is a set of rules and guidelines for a specific process, while framework is a structure that provides a foundation for a process.

• Methodology is more prescriptive, while framework is more flexible.

• Examples of methodologies include Waterfall, Agile, and Lean, while examples of frameworks include Scrum, Kanban, and S...read more

A task is a unit of work that needs to be completed within a project. It can be categorized into different types based on its nature and complexity.

• A task is a specific piece of work that needs to be accomplished.

• Tasks can be categorized into different types such as development tasks, testing tasks, documentation tasks, etc.

• Tasks can vary in size, complexity, and duration.

• Tasks are usually represented on a task board or in a project management tool.

• Tasks should be well-define...read more

Having two daily scrum calls can be beneficial in certain situations.

• If the team is distributed across different time zones, having two calls can ensure everyone is able to attend at a reasonable time.

• If the team is large, having two calls can help ensure everyone has a chance to speak and share their updates.

• However, having two calls can also be time-consuming and may not be necessary for smaller teams or those in the same time zone.

• Ultimately, the decision to have two daily...read more

KPIs used to measure project health

• Velocity: Measure of work completed in each sprint

• Sprint Burndown Chart: Tracks progress of work remaining in a sprint

• Cycle Time: Time taken to complete a user story from start to finish

• Defect Density: Number of defects found per unit of work

• Customer Satisfaction: Feedback from stakeholders and end-users

Scrum metrics include velocity, burn-down charts, sprint burndown, team happiness index, and cycle time.

• Velocity - measures the amount of work completed in a sprint

• Burn-down charts - track the remaining work in a sprint

• Sprint burndown - shows the progress of the sprint

• Team happiness index - measures the team's satisfaction and engagement

• Cycle time - measures the time it takes to complete a user story

It is not recommended to add user stories in the middle of the sprint.

• Product owner should be advised to wait until the next sprint planning meeting to add the user story.

• If the user story is critical, the team should discuss and decide if it can be accommodated within the current sprint.

• Adding user stories in the middle of the sprint can disrupt the team's focus and impact the sprint goal.

• The Scrum Master should facilitate a discussion with the team and product owner to dete...read more

Velocity is calculated by summing up the story points completed in a sprint. Capacity is the amount of work a team can handle in a sprint.

• Velocity is calculated by summing up the story points completed in a sprint

• Capacity is the amount of work a team can handle in a sprint

• Velocity is used to forecast the amount of work a team can complete in future sprints

• Capacity is determined by considering factors like team size, availability, and individual skills

• Velocity and capacity are...read more

The different columns in a Kanban Board are Backlog, To Do, In Progress, and Done.

• Backlog: Contains all the tasks that are yet to be started

• To Do: Contains the tasks that are ready to be worked on

• In Progress: Contains the tasks that are currently being worked on

• Done: Contains the tasks that have been completed

Scrum is a framework for agile project management.

• Scrum provides a set of guidelines and principles for managing and organizing work.

• It emphasizes iterative and incremental development.

• Scrum is flexible and allows teams to adapt and self-organize.

• It focuses on delivering value to the customer.

• Scrum includes specific roles, events, and artifacts.

• Examples of Scrum artifacts are product backlog, sprint backlog, and increment.

Scrum Master handles four events in Scrum framework.

• Sprint Planning

• Daily Scrum

• Sprint Review

• Sprint Retrospective

Both roles involve managing the project, but the approach and responsibilities differ.

• Both roles are responsible for ensuring the project is completed on time, within budget, and meets the requirements.

• Scrum Master focuses on facilitating the Scrum process and removing impediments for the team.

• Project Manager focuses on planning, organizing, and controlling the project.

• Scrum Master is a servant-leader, while Project Manager is a traditional manager.

• Scrum Master encourages col...read more

The recommended team size in Scrum is 5-9 members.

• The Scrum Guide recommends a team size of 5-9 members.

• Smaller teams may have difficulty completing all necessary work, while larger teams may face coordination challenges.

• A larger team may also lead to decreased individual accountability and increased complexity in communication.

• Having a cross-functional team with diverse skills and perspectives is important for successful collaboration.

• Examples: A team of 7 developers, a team...read more

I approach customer requirements by understanding their needs, prioritizing them, and collaborating with the team to deliver a solution.

• Listen carefully to the customer's requirements and ask questions to clarify any doubts.

• Prioritize the requirements based on their importance and impact on the project.

• Collaborate with the team to come up with a solution that meets the customer's needs and fits within the project constraints.

• Communicate the solution to the customer and get th...read more

Metrics for measuring success as a Scrum Master

• Velocity of the team

• Sprint burndown charts

• Team satisfaction surveys

• Number of completed user stories

• Percentage of defects found in production

• Cycle time for user stories

• Lead time for user stories

Scrum principles can be implemented through daily stand-ups, sprint planning, retrospectives, and backlog grooming.

• Daily stand-ups ensure team communication and progress tracking.

• Sprint planning involves setting goals and prioritizing tasks for the upcoming sprint.

• Retrospectives allow for reflection and continuous improvement.

• Backlog grooming ensures the backlog is up-to-date and prioritized.

• Using visual aids such as burndown charts and task boards can aid in transparency and...read more

Scrum fundamentals are the basic principles and values that guide the Scrum framework.

• Empirical process control

• Self-organizing teams

• Iterative and incremental development

• Time-boxed events

• Product backlog

• Sprint backlog

• Incremental delivery

• Continuous improvement

• Transparency

• Inspection and adaptation

I address conflicts during Sprint planning meetings by facilitating open communication, encouraging collaboration, and focusing on finding a mutually agreeable solution.

• Encourage team members to express their concerns and perspectives

• Facilitate open and respectful communication among team members

• Focus on finding a mutually agreeable solution that aligns with the Sprint goals

• Remain neutral and objective while guiding the team towards resolution

• Seek input from the Product Owner...read more

Different types of status codes in API include 1xx informational, 2xx success, 3xx redirection, 4xx client error, and 5xx server error.

• 1xx status codes are informational responses

• 2xx status codes indicate success

• 3xx status codes indicate redirection

• 4xx status codes indicate client errors

• 5xx status codes indicate server errors

Yes, OSS and BSS stand for Operations Support System and Business Support System respectively.

• OSS is responsible for managing and maintaining the network infrastructure.

• BSS is responsible for managing customer-facing activities like billing and customer service.

• Both systems are critical for the smooth functioning of a telecom or IT organization.

• Examples of OSS include network inventory management and fault management systems.

• Examples of BSS include billing systems and custome...read more

Listen to their concerns, collaborate to find a solution, and prioritize based on business value.

• Listen actively to understand their concerns

• Collaborate with the team to find a solution that meets both the product owner's needs and the team's capabilities

• Prioritize based on business value and impact on the product

• Communicate transparently with the product owner and stakeholders throughout the process

• Be open to feedback and willing to adjust plans as needed

It indicates that work is not being completed at the expected rate.

• A straight line on a burn down chart indicates that work is not being completed as planned.

• It may suggest that the team is not making progress or facing obstacles.

• It could also indicate that the initial estimation of work was incorrect.

I use various techniques such as Mad Sad Glad, Start Stop Continue, and 4Ls for Sprint retrospective.

• Mad Sad Glad: team members write down what made them mad, sad, or glad during the sprint and discuss it as a group

• Start Stop Continue: team members identify what they should start doing, stop doing, and continue doing in the next sprint

• 4Ls: team members write down what they liked, learned, lacked, and longed for during the sprint and discuss it as a group

Experience with Agile transformation, metrics in Jira, tools used, and ensuring team meets sprint goal

• I have experience leading Agile transformations and forming high-performing teams through coaching and training

• I am familiar with metrics available in Jira such as burndown charts, velocity, and sprint reports

• I use tools like Jira, Trello, and Slack to facilitate communication and collaboration within the team

• To ensure there is no spillover and the team meets the sprint goal,...read more

SAFe Agile is a framework for scaling Agile practices to large organizations, while Scrum is a specific Agile methodology for smaller teams.

• SAFe Agile is used when scaling Agile practices to large organizations with multiple teams

• Scrum is used for smaller teams working on a single project

• SAFe Agile includes additional roles, events, and artifacts compared to Scrum

• SAFe Agile provides guidance on how to coordinate multiple Agile teams working on a common goal

• Experience in imple...read more

Cost of estimation can be calculated by considering the time and effort put in by the team.

• Calculate the total time spent by the team on estimation

• Multiply the total time by the hourly rate of the team

• Add any additional costs such as tools or software used for estimation

• Divide the total cost by the number of items estimated to get the cost per item

• Use the cost per item to make informed decisions about future estimation efforts

Address the concerns and facilitate a discussion to reach a consensus

• Encourage open communication and active listening among team members

• Facilitate a discussion to understand the reasoning behind each team member's perspective

• Help the team explore alternative solutions and weigh the pros and cons of each option

• Guide the team towards reaching a consensus that aligns with the project goals and technical requirements

Handled tasks include project management, team coordination, stakeholder communication, and agile coaching.

• Managed project timelines, budgets, and resources

• Coordinated team efforts and facilitated collaboration

• Communicated with stakeholders to ensure project alignment

• Coached team members on agile principles and practices

• Assisted with product backlog management and sprint planning

• Identified and resolved impediments to team progress

Story points are a unit of measure used in Agile project management to estimate the effort required to complete a user story.

• Story points are relative estimates of effort, not time.

• They are assigned to user stories during sprint planning.

• They take into account factors such as complexity, risk, and uncertainty.

• They help the team to plan and track progress more effectively.

• Examples of story point values include 1, 2, 3, 5, 8, 13, 20, 40, and 100.

Agile metrics used in previous project included velocity, burndown charts, and cycle time.

• Velocity - measuring the amount of work completed in a sprint

• Burndown charts - tracking the remaining work in a sprint

• Cycle time - measuring the time taken for a task to be completed

Scrum is an agile framework for managing and completing complex projects.

• Scrum involves a team-based approach to project management

• It emphasizes on iterative and incremental development

• It involves regular meetings such as daily stand-ups, sprint planning, sprint review, and retrospective

• It uses artifacts such as product backlog, sprint backlog, and burn-down charts

• It promotes transparency, inspection, and adaptation

To ensure proper participation from all stakeholders in Sprint Planning meeting, the Scrum Master can set clear expectations, create a collaborative environment, encourage open communication, and facilitate discussions.

• Set clear expectations for the meeting agenda and goals

• Create a collaborative environment where all stakeholders feel comfortable sharing their input

• Encourage open communication and active participation from all team members

• Facilitate discussions and ensure tha...read more

My favourite Scrum ceremony is the Sprint Review.

• I enjoy the opportunity to showcase the team's work to stakeholders.

• It's a chance to receive feedback and make improvements for the next sprint.

• I also appreciate the collaborative nature of the ceremony, as it involves the entire team.

• Other ceremonies are important too, but the Sprint Review stands out to me.

• For example, the Daily Scrum helps keep the team aligned and focused.

• The Sprint Retrospective allows for continuous impro...read more

The 3 pillars of the Scrum framework are transparency, inspection, and adaptation.

• Transparency: All aspects of the process must be visible to those responsible for the outcome.

• Inspection: Scrum artifacts and progress must be inspected frequently to detect variances.

• Adaptation: If an inspection reveals that one or more aspects of the process deviate outside acceptable limits, adjustments must be made.

There are two types of estimation in Agile: Relative and Absolute.

• Relative estimation involves comparing the size of one item to another, using techniques like Planning Poker or T-Shirt sizing.

• Absolute estimation involves assigning a numerical value to an item, using techniques like Wideband Delphi or Affinity Mapping.

• Relative estimation is more commonly used in Agile, as it is quicker and more collaborative.

• Absolute estimation is useful for more complex projects or when a mo...read more

The term 'master' in Scrum Master signifies the role's expertise in guiding and coaching the team in the Scrum framework.

• The term 'master' implies a level of expertise and knowledge in the subject matter.

• The Scrum Master is responsible for guiding and coaching the team on Scrum practices and principles.

• The role involves facilitating meetings, removing obstacles, and ensuring the team follows Scrum processes effectively.

• The Scrum Master acts as a servant-leader, helping the te...read more

The events of Scrum are Sprint, Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective.

• Sprint: Time-boxed iteration where work is completed and reviewed.

• Sprint Planning: Meeting to plan the work to be done in the Sprint.

• Daily Standup: Daily meeting for the team to synchronize and plan the day's work.

• Sprint Review: Meeting at the end of the Sprint to review the work completed.

• Sprint Retrospective: Meeting at the end of the Sprint to reflect on what went well a...read more

I would discuss the impact on the sprint goal and team capacity with the PO before making a decision.

• Discuss the impact on the sprint goal and team capacity with the PO

• Analyze the current workload and team capacity to see if additional user stories can be accommodated without jeopardizing the sprint goal

• Prioritize the new user stories based on their importance and impact on the sprint goal

• Consider splitting larger user stories into smaller ones if necessary to fit them into t...read more

Metrics like velocity, burndown charts, sprint backlog progress, and team satisfaction are used to gauge project progress.

• Velocity: Measure of work completed in a sprint.

• Burndown charts: Track remaining work in a sprint.

• Sprint backlog progress: Monitor completion of sprint tasks.

• Team satisfaction: Assess team morale and collaboration.

Yes, release plan is a high-level view of the product roadmap, release planning is the process of creating a detailed plan for a specific release, and release management is the ongoing process of managing and monitoring the release.

• Release plan is a strategic plan that outlines the product roadmap and high-level features to be delivered in each release.

• Release planning is a detailed planning process that involves breaking down the high-level features into smaller tasks, estim...read more

KPIs are Key Performance Indicators used to measure the success of a project. Examples include velocity, sprint burndown, and team happiness.

• KPIs are metrics used to evaluate the performance and success of a project

• Common KPIs in Agile projects include velocity, sprint burndown, and team happiness

• KPIs help teams track progress, identify areas for improvement, and make data-driven decisions

All stakeholders including the development team, product owner, and customers can participate in Sprint Review.

• Development team presents the completed work to stakeholders

• Product owner reviews the progress and provides feedback

• Customers can provide feedback on the product

• All attendees collaborate to identify improvements for the next sprint