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

Capacity is the amount of work a team can handle in a sprint. Velocity is the amount of work a team can complete in a sprint.

• Capacity is calculated by estimating the number of hours each team member can work in a sprint and multiplying it by the number of team members.

• Velocity is calculated by adding up the number of story points completed in a sprint.

• Capacity and velocity can be adjusted based on factors such as team member availability, skill level, and external dependencie...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

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

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

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

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

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

Manage new requirements by assessing impact, prioritizing, and communicating with stakeholders while adhering to constraints.

• Assess the impact of the new requirement on the current deployment timeline and budget.

• Engage with stakeholders to understand the necessity and urgency of the new requirement.

• Prioritize the new requirement against existing tasks using a framework like MoSCoW (Must have, Should have, Could have, Won't have).

• Consider a phased approach: implement the new r...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

Addressing architectural changes requires collaboration, prioritization, and effective communication within the Scrum team.

• Engage stakeholders early to understand the need for architectural changes and gather their input.

• Facilitate a discussion with the development team to assess the impact of the changes on current work and backlog items.

• Prioritize the architectural changes in the product backlog, ensuring they align with the overall project goals.

• Encourage the team to break...read more

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.

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

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 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.

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 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

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

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

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