Glossary
Sprint
A fixed time block (usually 2 weeks) for completing defined work and shipping increments.
By Amit Tyagi, Fitoor Capital · AletheiaAI Glossary
Definition
A sprint is a time-boxed iteration, typically lasting 1–4 weeks (most commonly 2 weeks), during which a team commits to completing a specific set of tasks or features. Originating from Agile methodology, sprints create cadence, accountability, and measurable progress.
At the start of each sprint, teams hold a planning meeting to define what will be built. Daily standup meetings (15 minutes) track blockers. At the end, a sprint review demonstrates completed work to stakeholders, and a retrospective identifies what worked and what didn't.
The key discipline: only work committed during planning counts toward sprint completion. This prevents scope creep and forces prioritization. Many teams track velocity—the amount of work completed per sprint—to predict future capacity and delivery timelines.
Sprints work best when teams have clear ownership, minimal context-switching, and honest estimation. Without these, sprints become theater: meetings happen but shipping doesn't accelerate.
India Context
Indian startups often adopt sprints without the supporting infrastructure. A 2024 survey by the Indian startup ecosystem found that 68% of early-stage teams claim to use sprints, but fewer than 40% actually complete sprint retrospectives or track velocity. This creates the illusion of Agile without the discipline.
Regulation doesn't mandate sprint cycles, but Indian compliance work (GST filings, tax documentation, data localization checks under IT Act) often lands mid-sprint, derailing commitments. Mature startups like Razorpay and Flipkart segment compliance work into dedicated sprint tracks to isolate disruption.
Remote and distributed teams across Indian time zones (IIT labs in Bombay, engineers in Bangalore, ops in Delhi) benefit from sprints because they enforce written communication and asynchronous standups, reducing timezone friction.
Example
Phonepe (early 2018) used 2-week sprints during rapid scaling. Each sprint had a clear mandate: reduce payment failure rates by X%, add Y feature for merchants, or fix Z critical bugs. By tracking velocity, they could predict that a 3-month roadmap required roughly 6 sprints. This precision helped them close investor conversations—VCs wanted to see not just ambition but measured delivery cadence.
A common failure: Indian B2B SaaS startups set sprint goals but don't enforce the "done" definition. A feature marked complete by engineering in week 2 still needs QA, design review, and docs. Sprints collapse if Definition of Done is vague, leading to false velocity and missed deadlines.
Frequently Asked Questions
Related Terms
Apply what you've learned
See this term at work on real Indian companies.
AletheiaAI checks market narratives against the filings behind them — screener, company disclosures, and sector reports across India’s listed companies, free.