Agile Living

Tips to Prepare for An Agile Scrum Interview

As you head towards getting a step closer to your dream job at MNCs like Apple and Google, it is important to remember that the scrum role demands high score in an agile interview. It would be tricky to impress the interviewer.

In this article at, CaSandra Minichiello lists out 20 interview questions to be asked by a scrum master while checking your efficiency to fill agile project manager position.

The Mock-Up

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

  1. Explain Agile: It encourages last minute production with an approach to deliver quality software to the customer.
  2. Differentiate Agile and Waterfall: Agile encourages change, while traditional waterfall discourages change.
  3. Certification in Scrum: If you do not hold a certification, tell the interviewer your plans for future while highlighting the years of experience you hold.
  4. Define Roles in Scrum: Explain the three major roles of the product owner, scrum master, and delivery team. These roles are cross-functional and does not allow luxury of hiring more people.
  5. Define Daily Stand-Up: It is a 15-minute daily meeting held in the morning to discuss the team’s yesterday’s productivity and plan for today while addressing the blocks they face in finishing the assigned tasks.
  6. Define Sprint Planning Meeting: In this meeting, the product owner defines the sprint goal and talks about the backlog product items that demand high priority action. The delivery team then forecasts the time to finish the sprint.
  7. Define Scrum Master’s Role: The scrum masters guard the team against distractions from finishing a sprint goal.
  8. Differentiate Agile and Scrum: Scrum falls under agile that contains 4 major values and twelve principles. While Scrum has its own set of values and principles to form agile teams.
  9. Name Agile Frameworks: In addition to scrum, the others include kanban, test drive development, and feature driven development.
  10. Waterfall Over Scrum: Using waterfall over scrum is possible in predictable, well-defined situations that discourage change.
  11. Recommending Automated Testing: Scrum promotes automated testing for quick delivery of software.
  12. Define Length of Your Sprints: Ideally, it falls between one and four weeks, usually, a two-week sprint is used.
  13. Explain Velocity: It is an average of the points scored during the last 3 or 4 sprints used to predict he delivery time for backlog items
  14. Changing Requirements: Agile embraces change and constant feedback from stakeholders and customers. It helps in product improvement.
  15. Types of Metrics Used: Sprint burndown, epic and release burndown, and burn-up charts are to name a few.
  16. Define Burn-Down Chart: This chart records the hours a team has spent during the sprint and explains it by quoting an incident from your past experiences.
  17. Explain Retrospective: It is a meeting to review and adapt the process. Must define the ways to conduct it.
  18. The Number of Scrum Teams Managed at Once: The scrum master needs to lead not manage, so answer smartly.
  19. Requirements Used for the Teams: The scrum master does not write user story but assists the product owner to write and prioritize, while preparing for the sprint.
  20. How to handle difficult delivery team member: To present yourself as an effective leader, share your efficient efforts from the past. Your action to address the situation may bring you the desired role.

Read the original guidelines shared by the author by clicking the following link:

Show More

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.