Agile LivingAgile Thinking

Preparing for an Agile Scrum Interview? Follow The Guideline

As you move closer to your dream job at globally renowned MNCs, like Apple and Google, ensure you score high in your agile scrum interview. Otherwise, it would be extremely hard to impress the interviewer.

In this article at, CaSandra Minichiello lists 20 interview questions that a scrum master can ask to judge your efficiency as an agile project manager.

The Snappy One-Liners

Answering these questions will prepare you to leave a lasting impression on the interviewer:

  • Explain Agile: It encourages timely production of quality software for the customer.
  • Differentiate Between Agile and Waterfall: Agile encourages change, while traditional waterfall discourages it.
  • Certification in Scrum: If you do not hold certification in Scrum methodology, mention it as your future plan Highlight the years of experience you currently hold.
  • Define Roles in Scrum: Explain the three major roles of the product owner, the scrum master, and the delivery team. These roles are cross-functional and do not allow the luxury of hiring more people.
  • Define the Daily Stand-Up: It is a 15-minute daily meeting held in the morning to discuss team’s  last and current productivity. Team members address the bottlenecks they faced while completing the assigned tasks.
  • Define Sprint Planning Meeting: In this meeting, the product owner defines the sprint goal and talks about the product backlog items that demand immediate responses . The delivery team then estimates the time to finish the sprint.
  • Define the Scrum Master’s Role: A scrum master guards the teams against distractions that prevent them from finishing a sprint goal.
  • Differentiate Between Agile and Scrum: Scrum falls under agile that contains 4 major values and 12 principles. However, scrum has its own set of values and principles determined for agile teams.
  • Name Other Agile Frameworks: In addition to scrum, the others include Kanban, test-driven development, and feature-driven development.
  • Waterfall Over Scrum: Using waterfall over scrum is possible in predictable, well-defined situations that discourage change.
  • Recommend Automated Testing: Scrum promotes automated testing for quick delivery of quality software.
  • Define Length of Your Sprints: Ideally, it falls between one and four weeks. Usually, a two-week sprint is used.
  • Explain Velocity: It is an average of the points scored during the last three or four sprints to predict the delivery time of backlog items.
  • Changing Requirements: Agile embraces change and constant feedback from stakeholders and customers. It helps in product improvement.
  • Types of Metrics Used: Mention sprint burndown, epic and release burndown, and burn-up charts, etc.
  • Define Burn Down Chart: This chart records the hours a team has spent during the sprint. Explain it by quoting an incident from your past experiences.
  • Explain Retrospective: It is a meeting to review and adapt the process. Describe the ways you conduct it.
  • The Number of Scrum Teams Managed at Once: A scrum master needs to lead not manage, so answer smartly.
  • Requirements Used for the Teams: The scrum master does not write user stories but assists the product owner to write and prioritize them, while preparing for the sprint.
  • How to Handle Difficult Delivery Team Members: To present yourself as an effective leader, share your efficient efforts from the past. Your action in the past to resolve a complicated issue may make you eligible candidate for the role.

To view the original article, click on the following link:

Show More
Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.