Agile and Scrum Guide: Roles, Events, Artifacts, User Stories, Estimation and How Indian Teams Apply It

Agile is a way of delivering work in small, frequent increments with constant feedback instead of one big plan. Scrum is the most popular framework for doing it. Used widely across Indian IT services, product companies and startups, it is a core skill for developers, testers, analysts and managers. This guide explains the ideas and how to apply them sensibly.

The Agile mindset

The Agile Manifesto (2001) values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. The items on the right still matter, but those on the left matter more.

Scrum in one paragraph

A Scrum team works in fixed-length sprints, typically one to four weeks. Each sprint produces a usable increment of the product. The team plans the sprint, meets daily to coordinate, reviews the result with stakeholders and reflects on how to improve.

Scrum roles

• Product Owner: owns the product backlog and the value of the product. Decides priorities after listening to stakeholders.
• Scrum Master: a servant leader who helps the team follow Scrum, removes obstacles and protects focus. Not a project manager who assigns tasks.
• Developers: everyone who builds the product, including designers, testers and engineers. They are self-managing.

Scrum events

• Sprint: the container for all other events.
• Sprint Planning: the team selects backlog items and agrees on a sprint goal and plan.
• Daily Scrum: a 15-minute event for developers to synchronise and adapt the plan. It is not a status report to a manager.
• Sprint Review: the team shows the increment and gathers feedback.
• Sprint Retrospective: the team inspects how it worked and picks improvements.

Artifacts and commitments

• Product Backlog with the Product Goal: an ordered list of everything the product may need.
• Sprint Backlog with the Sprint Goal: items selected for the sprint plus the plan to deliver them.
• Increment with the Definition of Done: a usable, tested slice of the product that meets agreed quality criteria.

Writing user stories

A common template is: As a [type of user], I want [goal] so that [benefit]. For example: "As a first-time buyer, I want to see my monthly EMI so that I can decide how much loan to take." Add acceptance criteria that are testable, such as "EMI updates when amount, rate or tenure changes." Keep stories small enough to finish within a sprint. Use the INVEST checklist: independent, negotiable, valuable, estimable, small and testable.

Estimation

Many teams estimate in story points, using a relative scale like 1, 2, 3, 5, 8, 13, via planning poker. Points measure effort, complexity and uncertainty together, not hours. Track velocity, the number of points completed per sprint, only to help the team plan. Never use velocity to compare teams or judge individuals.

Kanban vs Scrum

• Scrum: time-boxed sprints, defined roles and events.
• Kanban: continuous flow, a visual board, work-in-progress limits, and no fixed sprints.
• Many teams blend them, which is often called Scrumban.

Useful metrics

• Sprint goal success rate.
• Cycle time and lead time for items.
• Defects found after release.
• Customer satisfaction and feedback.

Common mistakes in practice

• Treating the Scrum Master as the manager who assigns tasks.
• Daily stand-ups that become status meetings for a boss.
• Changing sprint scope mid-sprint without agreement.
• Skipping retrospectives or never acting on them.
• "Water-scrum-fall": detailed upfront plans disguised with Agile terms.
• No clear Definition of Done, leading to unfinished work.
• Using Jira ticket counts as the measure of productivity.

Agile with distributed teams

Teams spread across cities or time zones need clear written communication, overlapping hours for key events, recorded demos and shared tools such as Jira, Trello or Azure Boards. Keep ceremonies short and purposeful.

Careers and certifications

Popular credentials include Professional Scrum Master (PSM) from Scrum.org, Certified ScrumMaster (CSM) from Scrum Alliance, SAFe certifications for large organisations and PMI-ACP. A certificate helps, but practical experience on real teams matters more. Combine Agile skills with technical depth, as in Java or Python, and compare options in our career change guide. Freelancers can read freelance developer tips.

A sample sprint for a small team

A five-person team starts a two-week sprint on Monday. In planning, the Product Owner explains the goal: allow users to save a loan comparison. The team splits the work into stories, estimates them, and commits to what fits their past velocity. Each morning, they spend fifteen minutes on progress and blockers. Midway, they refine the next sprint's backlog. On the last Friday, they demo the feature to stakeholders and collect feedback, then hold a retrospective where they decide to write acceptance criteria before development next time. Small, steady cycles like this reduce risk because wrong assumptions surface within two weeks, not after six months of work.

Frequently asked questions

What is the difference between Agile and Scrum?

Agile is a mindset and set of values, while Scrum is a specific framework for applying it.

How long is a sprint?

Typically one to four weeks.

Is the Scrum Master a manager?

No, the role supports the team and removes obstacles.

What are story points?

A relative measure of the effort and complexity of work items.

What is the Definition of Done?

A shared checklist that defines when work is complete.

Is Kanban Agile?

Yes, it follows Agile principles with continuous flow instead of sprints.

Last reviewed 8 November 2026. Rates, limits and rules change, so confirm figures with the official source before you act.