Preparing for an Agile Scrum interview requires a mix of theoretical knowledge, situational problem-solving, and a clear understanding of your specific role (Scrum Master, Product Owner, or Developer). Be ready to discuss the Scrum framework, roles, artifacts, ceremonies, and how you foster self-organization and continuous improvement.
Review these common Agile Scrum interview questions, categorized by topic:
1. Fundamentals & Frameworks
- What is the difference between Agile and Scrum? Agile is an overarching project management philosophy focused on iterative development and flexibility. Scrum is a specific, lightweight framework within Agile that uses set roles, artifacts, and timeboxed “sprints” (usually 1-4 weeks).
- What are the core roles on a Scrum Team? The three primary roles are the Product Owner (maximizes value, owns the backlog), the Scrum Master (servant-leader, removes impediments, ensures Scrum rules are followed), and the Developers (cross-functional team that delivers the increment).
- What is a “Spike”? A spike is a timeboxed research or exploration task used to reduce uncertainty, figure out a technical approach, or better understand a requirement before development begins.
2. Scrum Ceremonies (Events)
- What happens during a Sprint Planning meeting? The team collaborates to determine what work can be delivered in the upcoming sprint and creates a plan (the Sprint Backlog) for how to achieve this Product Goal.
- Can you give a 2-3 minute overview of the Daily Scrum? It is a 15-minute timeboxed event for the Developers to inspect progress toward the Sprint Goal and adapt the upcoming work. It is not a status report to management; it is for the team to synchronize and plan the next 24 hours.
- What is the purpose of a Sprint Retrospective? Held at the end of every sprint, the team inspects the past sprint regarding people, relationships, processes, and tools. The goal is to identify what went well and create a plan for implementing improvements.
- What is the difference between a Sprint Review and a Retrospective? The Review inspects the software/product increment to adapt the Product Backlog. The Retrospective inspects the team’s process and working environment.
3. Artifacts & Estimation
- What is the Definition of Done (DoD)? It is a shared, clear checklist of criteria that must be met for a product increment to be considered ready for release. It ensures consistency and quality across the team.
- What is Velocity? Velocity measures the total amount of work (usually in Story Points) a Scrum Team can deliver during a single sprint. It is typically calculated as an average over the last 3-4 sprints and helps predict future delivery.
- How do you handle scope creep? Emphasize that in Scrum, the sprint scope is locked once the sprint starts. If new work is urgent, it should go to the Product Backlog for future planning, or the team can negotiate with the Product Owner to remove an equally sized task from the current sprint to make room.
4. Situational & Behavioral (Scrum Master/Agile Coach focus)
- What do you do if a manager tries to dictate or assign tasks to the team? Coach the manager on Scrum principles (self-management) and act as a shield to protect the team from outside interference, allowing them to focus on the Sprint Goal.
- How do you build trust with your team? Focus on empathy, transparency, consistency, and active listening. Build a safe space where the team can fail forward, experiment, and voice concerns without fear of retaliation.
- How do you handle conflict within the team? Encourage the team to resolve conflicts themselves first, stepping in only if it affects the sprint goals. Facilitate open dialogue focusing on the issue (the process/problem), not the person.
PROject Templates 