Sprint
A sprint is a fixed-length, time-boxed development cycle in Agile/Scrum methodology — typically 1 or 2 weeks — during which a defined set of features or tasks are built, tested, and delivered.
In depth
Sprints come from Scrum, an Agile framework for managing software development. The core idea: break large projects into small, deliverable chunks and review progress frequently.
A sprint lifecycle: 1. Sprint Planning: team selects items from the backlog, estimates effort, commits to a goal 2. Daily Standup: 15-minute daily sync — what did I do yesterday, what am I doing today, any blockers? 3. Development: team builds the committed features 4. Sprint Review: demo of completed work to stakeholders 5. Retrospective: team reflects on process — what went well, what to improve
Sprint vs Kanban: Sprints have fixed duration and planning sessions. Kanban is continuous flow with WIP (work-in-progress) limits. Both are common in startup engineering teams.
For MVP development: we run 21-day sprints (3 weeks) that deliver a complete, production-ready MVP. Founders get daily updates and a weekly demo.
Real example
Week 1 sprint goal: 'Complete authentication, onboarding flow, and dashboard layout.' By end of week, those features are working on staging and the founder has approved the designs.
Related terms
MVP (Minimum Viable Product)
A Minimum Viable Product (MVP) is the simplest version of a product that can be released to early users to validate core assumptions, gather feedback, and begin learning — with the minimum amount of effort and cost.
Technical Debt
Technical debt refers to the implied cost of future rework required when shortcuts or suboptimal solutions are chosen during software development for the sake of speed.
API (Application Programming Interface)
An API (Application Programming Interface) is a set of rules and protocols that allows different software applications to communicate with each other — like a contract defining how one piece of software can request data or actions from another.
Technical Debt
Technical debt is the implied future cost of rework caused by choosing a faster, easier solution now instead of a better, slower one — analogous to financial debt accumulating interest.
API (Application Programming Interface)
An API (Application Programming Interface) is a set of rules and protocols that allows one software application to communicate with another — requesting data, triggering actions, or exchanging information.
Ready to build your product?
Fixed price. 21-day delivery. Senior team.
Get a free scoping call →