Interview questions

Agile Methodology Interview Questions

Agile methodology interview questions on Scrum, Kanban, estimation and team practice, with model answers. For candidates preparing and interviewers asking.

Agile Methodology Interview Questions

What's here

18 Agile Methodology interview questions, grouped into 4 areas: agile principles, scrum, kanban, estimation and metrics and backlog and stakeholders. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.

  • Ask for a specific Sprint, retrospective or incident; agile vocabulary is easy to learn, real practice is not
  • Check framework facts against the current Scrum Guide (2020), which replaced 'roles' with accountabilities and added the Product Goal
  • Give a short scenario, such as a stakeholder demanding fixed scope and date, and listen for trade-offs over slogans
For hiring teams

Cohesyve finds, contacts and tests Agile Methodology candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.

Preparing for this interview yourself? Practise it free →

Agile methodology interview questions come up for scrum masters, product owners, developers, testers, business analysts and project managers alike. Interviewers want to know whether you understand why agile practices exist, and whether you have used them well on a real team. These questions cover the principles, Scrum, flow-based methods, estimation and the awkward situations every agile team meets. Interviewers can use the 'what to look for' notes as a scoring guide; candidates can read them as model-answer guidance.

Agile Principles

Whether the candidate understands what agile is for, beyond the ceremonies.

  1. 1

    What is agile, in your own words?

    Why ask it

    A plain-language answer shows understanding. A recited definition often hides the lack of it.

    What to look for

    Delivering work in small, usable increments, getting feedback early and often, and adjusting plans as you learn. Strong candidates mention the Agile Manifesto (2001) and can explain at least one of its four values, such as 'responding to change over following a plan', with an example from their own work.
  2. 2

    The Agile Manifesto says 'working software over comprehensive documentation'. Does that mean agile teams do not document?

    Why ask it

    A common misreading that leads to teams with no shared knowledge.

    What to look for

    No. The manifesto says the items on the right still have value; the items on the left are valued more. Good answers describe documenting what the team and users genuinely need (decisions, interfaces, how to run the system) and skipping documents nobody reads.
  3. 3

    When is agile a poor fit for a piece of work?

    Why ask it

    Tests judgement over dogma.

    What to look for

    Work with fixed, well-understood requirements and hard sequential dependencies (some infrastructure, regulated or hardware work), or organisations where customers cannot give feedback. Strong candidates suggest hybrids, such as iterative build inside a fixed release plan, before rejecting agile outright.
  4. 4

    How does agile differ from Waterfall?

    Why ask it

    A baseline question that reveals how the candidate thinks about planning and risk.

    What to look for

    Waterfall moves through phases in sequence (requirements, design, build, test, release) with most learning arriving late. Agile repeats short cycles of planning, building and reviewing, so problems and changed needs surface sooner. A good answer avoids calling one method always better.
For hiring teams

Before the Agile Methodology interviews, see who can do the work

Cohesyve finds and contacts Agile Methodology candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.

Scrum

Scrum is the most common agile framework in interviews. These questions check accurate knowledge and real use.

  1. 5

    Walk me through the Scrum events and what each one is for.

    Why ask it

    Checks accurate framework knowledge.

    What to look for

    Per the 2020 Scrum Guide: the Sprint (a container of one month or less), Sprint Planning (what and how for the Sprint), the Daily Scrum (a 15-minute inspection of progress towards the Sprint Goal), the Sprint Review (inspect the outcome with stakeholders) and the Sprint Retrospective (improve how the team works). Strong candidates explain the purpose of each, not only the name.
  2. 6

    What are the three accountabilities in a Scrum Team, and where do they overlap or clash?

    Why ask it

    Role confusion causes most Scrum dysfunction.

    What to look for

    Product Owner (maximises value and owns the Product Backlog), Scrum Master (the team's effectiveness and Scrum adoption) and Developers (create a usable Increment each Sprint). Good answers name real tensions, such as a Product Owner who assigns tasks or a Scrum Master who acts as a project manager.
  3. 7

    What is the Definition of Done, and why does it matter?

    Why ask it

    Teams without one ship 'done' work that is not finished.

    What to look for

    The Definition of Done is the quality bar an Increment must meet; the 2020 Scrum Guide calls it the commitment for the Increment. Examples: code reviewed, tested, documented, deployed to a staging environment. Strong candidates describe how a team tightened its Definition of Done over time.
  4. 8

    What is the difference between the Product Goal and the Sprint Goal?

    Why ask it

    Tests knowledge of the 2020 Scrum Guide and whether the candidate connects daily work to outcomes.

    What to look for

    The Product Goal is the long-term objective for the product and the commitment for the Product Backlog. The Sprint Goal is the single objective for one Sprint and the commitment for the Sprint Backlog. Good answers explain how a clear Sprint Goal helps the team make trade-offs mid-Sprint.
  5. 9

    Your Daily Scrum has turned into a 30-minute status report to the manager. What do you change?

    Why ask it

    A common failure. Shows practical coaching ability.

    What to look for

    Return it to its purpose: the Developers inspect progress towards the Sprint Goal and adapt the plan. Move problem-solving to after the meeting, keep it to 15 minutes, and address why the manager needs status (perhaps a better board or a short written update).

Kanban, Estimation and Metrics

Flow-based methods and how agile teams plan and measure without false precision.

  1. 10

    When would you choose Kanban over Scrum?

    Why ask it

    Shows the candidate can fit the method to the work.

    What to look for

    Kanban suits continuous, unpredictable incoming work such as support, operations or maintenance, where fixed Sprints add little. Key ideas: visualise the work, limit work in progress, manage flow. Strong candidates mention teams that combine both.
  2. 11

    Why limit work in progress?

    Why ask it

    WIP limits are the core of flow-based methods and are often skipped.

    What to look for

    Less work started at once means less context switching, faster finishing and bottlenecks that become visible. A good answer gives an example of a WIP limit exposing a stuck review or testing stage.
  3. 12

    How do story points work, and what are their limits?

    Why ask it

    Estimation is a frequent source of conflict with stakeholders.

    What to look for

    Relative estimates of size, complexity and uncertainty, agreed by the people doing the work, often via planning poker. Limits: points are not hours, are not comparable across teams and should not measure individual performance. Strong candidates mention alternatives such as counting items or forecasting from cycle time.
  4. 13

    Which metrics do you track for an agile team, and which do you avoid?

    Why ask it

    Separates outcome thinking from activity tracking.

    What to look for

    Useful: cycle time, throughput, escaped defects, Sprint Goal success, customer outcomes. Risky when misused: velocity as a target, points per person, utilisation. Good answers explain that a metric used as a target tends to get gamed.

Backlog and Stakeholders

How agile works with the people outside the team.

  1. 14

    How do you write a good user story?

    Why ask it

    Backlog quality drives delivery quality.

    What to look for

    Who needs it, what they need and why ('As a ..., I want ..., so that ...'), plus clear acceptance criteria. Stories small enough to finish in a Sprint, independent where possible, and testable. Strong candidates describe splitting a large story by workflow step or business rule.
  2. 15

    A senior stakeholder wants a fixed date and fixed scope for an agile project. How do you respond?

    Why ask it

    Every agile practitioner meets this. Tests how they handle it.

    What to look for

    Acknowledge the need for predictability, then offer a forecast range based on the team's actual throughput, deliver the highest-value items first and agree which scope can flex. Weak answers either refuse or promise everything.
  3. 16

    How do you prioritise a backlog when everything is urgent?

    Why ask it

    Prioritisation is where value is won or lost.

    What to look for

    Tie items to the Product Goal, weigh value against cost and risk, use a simple method (cost of delay, MoSCoW, value versus effort) and make the trade-off visible to stakeholders. The Product Owner decides, with input.
  4. 17

    Tell me about a retrospective that changed how your team worked.

    Why ask it

    Real examples show whether retrospectives produce action.

    What to look for

    A specific problem, the change the team agreed, an owner, and evidence it worked or was dropped. Good candidates mention keeping actions few and following them up at the next retrospective.
  5. 18

    How would you introduce agile to a team that has always worked in Waterfall?

    Why ask it

    Many hires are expected to lead a transition.

    What to look for

    Start with the problem the team wants to solve, pilot on one piece of work, keep practices light, train by doing, and inspect and adapt the approach itself. Strong answers respect existing constraints and avoid a big-bang rollout.

Running the interview well

  • 1Ask for a specific Sprint, retrospective or incident; agile vocabulary is easy to learn, real practice is not
  • 2Check framework facts against the current Scrum Guide (2020), which replaced 'roles' with accountabilities and added the Product Goal
  • 3Give a short scenario, such as a stakeholder demanding fixed scope and date, and listen for trade-offs over slogans
  • 4Probe how the candidate handled a metric being misused, such as velocity used as a performance target
  • 5Treat certifications as a plus, and score evidence of delivery and team improvement above them
  • 6For developers and testers, ask how they contributed to the Definition of Done and to refining stories
  • 7Listen for judgement about when agile does not fit; dogmatic answers predict friction

Common questions

What are the most common agile methodology interview questions?

Expect questions on the Agile Manifesto values, Scrum events and accountabilities, the Definition of Done, Scrum versus Kanban, story points and estimation, handling fixed-date stakeholders and running retrospectives. Most interviewers follow up by asking for a real example.

How should I prepare for an agile interview?

Read the current Scrum Guide and the Agile Manifesto, then prepare three or four stories from your own work: a Sprint that went well, one that went badly, a retrospective action that stuck and a conflict with a stakeholder. Practise explaining each in two minutes.

Do I need a certification to pass an agile interview?

It depends on the employer. Certifications show you have studied a framework, but interviewers usually weigh practical examples more heavily. Be ready to explain how you applied what you learned.

Is Scrum the same as agile?

No. Agile is a set of values and principles. Scrum is one framework that puts them into practice. Kanban, Extreme Programming and others are different ways of working in an agile manner.

How long is a Sprint in Scrum?

The 2020 Scrum Guide sets Sprints at one month or less. Teams choose a fixed length within that limit and keep it consistent.

What do interviewers look for in agile answers?

Understanding of why each practice exists, honest examples including failures, and judgement about adapting practices to the team and the work. Reciting terms without examples is a common weak signal.

For hiring teams

Save these questions for the Agile Methodology candidates who can do the work

Cohesyve takes your Agile Methodology job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.

1,500+

assessments completed

50%

faster time-to-hire

5 min

from JD to assessment

14-day free trial · 10 candidates · Not charged until the trial ends

For job seekers

Preparing for an Agile Methodology interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.

Practise an Agile Methodology interview free →

See Cohesyve in action

Free 30-min walkthrough

See it on your role