Agile and Scrum skills
employers want

Agile is a mindset described in the 2001 Agile Manifesto: four values (individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan) and twelve principles.¹ Scrum is the most widely used framework built on those ideas. The 2020 Scrum Guide defines three accountabilities, five events and three artifacts, each with a commitment: the product goal, the Sprint Goal and the Definition of Done.² It rests on empiricism — transparency, inspection and adaptation — and lean thinking.

Understanding the framework's purpose matters more than running the meetings. Atlassian's guide stresses that Scrum events exist to inspect progress and adapt, not to report status.³ Agile roles are well established in India. AmbitionBox lists scrum masters at a typical ₹16.5–18.2 lakh, up 11% in two years,⁴ and agile coaches at ₹27.8–30.7 lakh.⁵

Agile Manifesto values and principles

4 / 12

Scrum accountabilities, events and artifacts

3 / 5 / 3

Typical scrum master pay in India (AmbitionBox)

₹16.5–18.2 lakh

Typical agile coach pay in India (AmbitionBox)

₹27.8–30.7 lakh

Table: How agile and Scrum knowledge is assessed (editorial summary)

Table: Scrum elements, purposes and common mistakes (editorial guidance)

Table: How agile and Scrum developed (editorial summary)

• Explain the four values and Scrum's elements accurately
• A Sprint Goal you helped write
• A Definition of Done you improved
• A retrospective you facilitated with an action
• An impediment you removed
• A verified agile and Scrum certificate

Show improvement: "Introduced Sprint Goals and a testing-inclusive Definition of Done; sprint completion and client satisfaction improved within three sprints."

"What does a Scrum Master do?"

Establishes Scrum, coaches the team and organisation, removes impediments and helps everyone improve effectiveness.

"What's the purpose of the Daily Scrum?"

For developers to inspect progress towards the Sprint Goal and adapt the plan — 15 minutes.

"What happens if work isn't done at sprint end?"

It returns to the product backlog for the product owner to reorder; it isn't shown as done.

"How do you make retrospectives useful?"

Vary formats, focus on one or two improvements, assign owners and check results next time.

"Can the Sprint Goal change?"

The Sprint Goal stays; scope may be renegotiated with the product owner as more is learned.

• "How mature is Scrum here?" — starting point.
• "Do teams have a Definition of Done?" — quality.
• "How do managers interact with Scrum teams?" — self-management.
• "What impediments come up most?" — challenges.

Table: Agile roles and typical pay in India (AmbitionBox, October 2026; indicative)

Table: Common agile and Scrum tools (editorial guidance)

• Team member / coordinator — learns Scrum.
• Scrum master — one or two teams.
• Senior scrum master — several teams.
• Agile coach — organisation-level change.
• Head of agile / delivery — ways of working.

1. Week 1: Read — The Scrum Guide and Agile Manifesto; map each element.
2. Week 2: Practise and prove — Facilitate a retro; take the Agile and Scrum Certification.

Related: Product Owner, Kanban and User Stories. Guides: product owner, Kanban and user stories.

• Sprint events — planning, daily, review, retro.
• Impediments — removing blockers.
• Coaching — teams and stakeholders.
• Transparency — boards and metrics.
• Improvement — small changes each sprint.
• Collaboration — with product owners.

"Scrum vs Kanban?"

Scrum uses fixed sprints and roles; Kanban manages continuous flow with WIP limits. Teams can combine ideas.

"What's velocity and how should it be used?"

A team's own planning aid — not a performance metric or comparison between teams.

Table: A first-90-days plan (editorial guidance)

Observe first: how the team plans, communicates and finishes work. Introduce Sprint Goals and a stronger Definition of Done, then focus on removing the biggest impediments. Coach stakeholders on how to engage with the team so the framework works as intended.

AI tools now summarise stand-ups, draft sprint reports, flag at-risk work and suggest retrospective themes from team feedback. That reduces administrative work for scrum masters and frees time for coaching. AI coding assistants also change how much a team can deliver per sprint, so estimates and capacity planning need recalibrating.

The fundamentals don't change. Teams still need clear goals, real done-ness and honest reflection. AI-generated metrics can encourage surveillance if misused, so scrum masters should protect psychological safety and keep metrics as tools for the team. In interviews, show how you'd use AI to remove busywork while keeping Scrum focused on value and learning.

A useful retrospective has five steps: set the stage (remind everyone of the goal and make it safe to speak), gather data (what happened during the sprint), generate insights (why it happened), decide what to do (one or two specific actions with owners) and close (thank people and check how the retro went). Vary formats to keep energy up, start by reviewing last retro's actions, and keep discussions about systems, not blame. Teams improve fastest when retros reliably lead to small, visible changes.

A Sprint Goal gives the team a reason to work together rather than on unrelated tickets. Write it as an outcome, not a list: "Customers can pay with UPI in the checkout" rather than "Finish stories 41, 42 and 47." It should be achievable within the Sprint, meaningful to stakeholders and flexible enough that the team can adjust scope while still meeting it. The product owner proposes how the product could increase its value, and the whole team crafts the goal during Sprint Planning. Display it prominently and refer to it in every Daily Scrum. At Sprint Review, discuss whether it was met and what was learned.

• Treating Scrum as meetings.
• No Sprint Goal.
• Weak Definition of Done.
• Daily Scrum as status report.
• Velocity as a performance metric.

Agile values come from the Agile Manifesto; Scrum definitions from the 2020 Scrum Guide; practical guidance from Atlassian; and India pay from AmbitionBox (read October 2026). The framework table, retro steps and history are editorial. Science of Apps publishes the free test linked here. Last reviewed October 2026.

• Sprint — a fixed period, one month or less, to create value.
• Sprint Goal — the single objective for a Sprint.
• Increment — a usable step towards the product goal.
• Definition of Done — the quality standard for the increment.
• Empiricism — learning through transparency, inspection and adaptation.