Updated September 2026 · Written and maintained by the Progression Agency strategy team
Agile software development is an iterative way of building software in short cycles, releasing working increments and changing course based on feedback. It is the agile methodology of software development that most product teams now start from. This guide explains the Agile Manifesto, the agile software development process and life cycle, Scrum and Kanban, lean principles, and how agile compares with waterfall: plainly, with the terms defined.
On this page · 18 sections
- What is agile software development?
- The Manifesto for agile delivery: the manifesto of agile software development
- What is the agile delivery process? The agile software development process, step by step
- The agile development life cycle
- What happens at the start and end of the agile software development life cycle?
- Scrum, Kanban and other agile frameworks
- Agile methodology of project management: how agile project management differs
- Agile vs waterfall software development
- Security in the agile delivery life cycle
- Agile and the MVP
- Agile application development when a new app replaces an old system
- How Progression Agency uses agile
- Scrum roles, events and artifacts
- Scrum methodology for software development: when it fits and when it strains
- What a sprint in agile software development looks like, day by day
- Comparing scrum software development with kanban agile software development
- Agile vs waterfall at a glance
- Agile delivery cycles, user stories and testing: agile software development cycles in practice
The short answerAgile work delivers software in short iterations, typically two-week sprints, each ending with working software that users or stakeholders can review. It follows the 2001 Manifesto for agile development, which values individuals and interactions, working software, customer collaboration and responding to change. Scrum and Kanban are the most common agile frameworks; lean software development focuses on eliminating waste and delivering value continuously.
What is agile software development?
Agile work is an approach to building software in which cross-functional teams deliver working increments in short, repeated cycles and adapt the plan based on feedback, rather than defining everything up front and delivering once at the end. Companies using agile software development run from two-person startups to banks and public agencies, which is why the word covers very different day-to-day habits.
The Manifesto for agile delivery: the manifesto of agile software development
Published in 2001 by seventeen software practitioners, the Agile Manifesto sets out four values and twelve principles. The values prefer the items on the left while recognizing value in those on the right. The twelve agile development principles behind the values cover early and continuous delivery, welcoming changing requirements, working software as the main measure of progress and regular reflection on how to work better. No single agile method for software development came out of the manifesto: its authors already practiced Scrum, Extreme Programming and others, and they set down what those approaches had in common.
What is the agile delivery process? The agile software development process, step by step
The agile process runs in cycles: maintain a prioritized backlog, plan a sprint, build and test, hold short daily standups, demo the working increment in a review, reflect in a retrospective, release, and repeat. Those agile software development process steps repeat every sprint, so a slip in one shows up at the next review and not months later at a final handover. The software development process in Scrum keeps this loop but fixes the cycle length in advance and names who owns the backlog.
The agile development life cycle
The agile SDLC repeats concept, iteration (design, build, test), release, maintenance and feedback continuously, rather than moving once through requirements, design, build, test and deploy as in waterfall. A typical agile development workflow moves each item from backlog to ready, in progress, review, testing and done, and the same agile methodology workflow applies whether the team uses a Scrum sprint board or a Kanban board. Mapped on a wall, the agile software development process flow is a loop and not a line, with each review feeding the next planning session. In the Scrum software development life cycle, the sprint rather than the project becomes the unit that is planned, built and released. The release process in agile need not match the sprint: a team may ship several times within one sprint, or hold finished increments until a planned release date.
| Phase | What happens |
|---|---|
| Concept | Define the problem, users and goals |
| Inception | Form the team, set up tooling, build the initial backlog |
| Iteration | Design, code and test in sprints |
| Release | Ship increments to users |
| Maintenance | Support, monitor, fix |
| Retirement | Decommission when replaced |
What happens at the start and end of the agile software development life cycle?
Inception opens the cycle and retirement closes it, and both sit outside the sprint loop. Of the six agile software development phases, these two get the least attention, yet they decide how quickly the first sprint starts and how cleanly an old system is switched off.
Inception covers the work before sprint one: naming the product owner, forming the team, writing the first user stories into the backlog, and setting up the repository, build pipeline and staging environment so the first increment has somewhere to run. A team that starts sprinting without it tends to spend its first sprint on setup instead of features.
Retirement begins when a product is replaced or costs more to keep than it returns. The team moves data and users to the replacement, announces an end of support date, archives the code and documentation, and shuts down hosting and accounts so nothing keeps billing or holding customer data after the switch.
Scrum, Kanban, SAFe agile development and other agile development frameworks
Scrum
Fixed-length sprints with three roles, product owner, Scrum Master and developers, and events for planning, daily coordination, review and retrospective. See the Scrum Guide. In the Scrum software development model, an item that misses the Definition of Done cannot be presented at the Sprint Review and goes back to the Product Backlog, which keeps half-finished work out of the demo.
Kanban
A continuous flow of work visualized on a board with limits on work in progress; no fixed sprints.
Extreme Programming (XP)
Engineering practices such as test-driven development, pair programming and continuous integration. Extreme Programming in agile software development is the framework most focused on engineering habits, so teams often borrow its practices while running Scrum for planning.
Lean software development
Principles from lean manufacturing applied to software: eliminate waste, build quality in, deliver fast, defer commitment and optimize the whole. In practice, the lean methodology in software development shows up as small batches, a cap on work in progress and a value stream map that exposes where requests sit waiting between handoffs.
SAFe: agile development at scale
SAFe, the Scaled Agile Framework published by Scaled Agile, Inc., is a framework for scaling lean and agile practices across an organization, and it is the usual answer when people ask about safe agile development for large programs. It organizes the work into five competency areas: Lean Portfolio Management, Team and Technical Agility, Product Development Flow, Large Solution Integration and Delivery, and Leadership and Culture. The agile methodology SAFe describes sits above team-level Scrum or Kanban, because its job is to coordinate many teams working toward one release. For a single product team it adds more coordination than it removes, so most of the agile development frameworks in everyday use start with Scrum or Kanban and add scaling only when several teams depend on each other’s work. The difference between SAFe and agile is one of scope: agile is the set of values and principles in the Manifesto, while SAFe is one published framework for applying them across many teams, with its own roles and planning cadence.
Agile methodology of project management: how agile project management differs
The agile methodology of project management applies the same short-cycle thinking to planning and tracking work that agile software development applies to code. Instead of one fixed plan agreed at the start, a project management agile methodology keeps a prioritized backlog, plans one cycle at a time, reviews working output at the end of each cycle and reorders what comes next. The project manager’s job shifts from enforcing a schedule to removing blockers, keeping the backlog honest and making trade-offs visible to the people paying for the work. Agile methodology in project management also changes reporting: progress is shown by working increments and the backlog that remains, not by percent complete against a Gantt chart.
Software helps but does not create the discipline. Agile development project management software usually combines a backlog, a sprint or Kanban board, estimates, and burndown or flow charts, and the same goes for agile development project management tools. When you compare agile software development management tools, check how they handle story points, work in progress limits and reporting for stakeholders who do not use the tool every day. The same test applies to any tools for agile methodology: a team that has not agreed what done means will not be rescued by a board. Choose tools for agile development after the team has run two or three cycles by hand, on a wall or a spreadsheet, so the tool follows working habits rather than inventing them. Agile software development tools extend beyond the board as well, since version control, automated tests and a deployment pipeline are what make a working build possible every sprint.
Agile vs waterfall software development
Waterfall moves through fixed phases once and delivers at the end; agile delivers working software every sprint and adjusts. Agile reduces the risk of building the wrong thing; waterfall offers more up-front predictability when requirements are fixed. On paper the agile software development process model looks less tidy than waterfall’s stages, so buyers used to sign-off gates should agree early what they will approve at each review.
Pros and cons of agile software development
The gains are early feedback, visible progress and the freedom to stop once enough value has shipped. The disadvantages of agile software development are just as real: a final cost and date are harder to fix at the start, the product owner has to give time every week, written records can lag behind the code, and a backlog that never ends can hide scope creep. It fits products whose requirements will move, and suits a fully specified, unchanging job less well.
Security in the agile delivery life cycle
Security is built into each sprint rather than tested at the end: threat modeling during design, code review and automated scanning on every change, and penetration testing before major releases. The NIST Secure Software Development Framework describes these practices.
Agile and the MVP
In agile, the minimum viable product is the first increment released to real users; later sprints iterate on what they do. An agile software development diagram often shows this as a skateboard becoming a bike and then a car: each stage is usable, which is the point.
Agile application development when a new app replaces an old system
Replacing a working system is the case where sprints help most and are easiest to misuse. The safer pattern moves one workflow at a time: the new app takes over, say, order entry for one department, while the old system keeps running everything else, and a sync job keeps both holding the same records until that slice is proven.
Each sprint then retires a little more of the old system instead of rebuilding all of it before anyone can use the new one. Users test real work early, the unwritten rules buried in the old system surface while they are cheap to handle, and every release leaves the business with something that runs. The final sprints switch the old system off once nothing reads from it.
How Progression Agency uses agile
Our software and app development projects run in two-week sprints with a written first-release scope, an installable or deployable build at the end of every sprint, and a shared backlog you can see and reprioritize. Our agile software development best practices are plain ones: a definition of done agreed before the first sprint, automated tests written with the code, and a demo you can attend at the end of each cycle.
Agile mobile app development: what changes on a phone
Store review sits between a finished sprint and the person holding the phone, so mobile teams usually send a test build to a small circle of testers every sprint and release to the public on a planned cadence. Agile methodology for mobile application development also has to allow for people who never update: older app versions stay in use for months, so each backend change must keep working for them while the new screens roll out.
Which agile principles matter most in agile app development?
Three stand out on a phone app: deliver working software frequently, have business people and developers work together daily, and give continuous attention to technical excellence and good design. They come from the 12 principles of agile software development that sit behind the Manifesto’s four values, and on an app they mean a build the client can install each sprint, a product owner who answers questions within the day, and code clean enough that a screen can change late without breaking another.
Simplicity, which the principles describe as maximizing the amount of work not done, decides the first release. Every feature cut from launch is one less screen to design, test across devices and support in later versions, so the smallest useful app reaches the store sooner and real usage sets what the next sprints build.
The characteristics of agile software development a client notices most are short feedback loops and a backlog they can reorder. On an app, that loop reaches past the team: crash reports and comments from the people testing each build feed the next sprint, so a confusing screen gets fixed before launch rather than after the first round of store reviews. Our agile software development services turn that tester feedback into backlog items the product owner ranks alongside new features.
Scrum roles, events and artifacts
The 2020 Scrum Guide defines three accountabilities, five events and three artifacts. Teams that talk about agile methodology ceremonies mean these same five events, and the agile development retrospective at the end of each sprint is where the team inspects how it worked and picks improvements for the next one.
| Element | What it is | Timebox or commitment |
|---|---|---|
| Product Owner | Maximizes product value; owns the Product Backlog | Accountability |
| Scrum Master | Establishes Scrum and helps the team improve | Accountability |
| Developers | Create a usable Increment each Sprint | Accountability |
| Sprint | Fixed-length cycle of work | One month or less |
| Sprint Planning | Decides why, what and how for the Sprint | Up to 8 hours for a one-month Sprint |
| Daily Scrum | Inspects progress toward the Sprint Goal | 15 minutes |
| Sprint Review | Inspects the outcome with stakeholders | Up to 4 hours |
| Sprint Retrospective | Plans improvements to quality and effectiveness | Up to 3 hours |
| Product Backlog | Ordered list of what is needed | Product Goal |
| Sprint Backlog | Sprint Goal plus selected work | Sprint Goal |
| Increment | Usable step toward the Product Goal | Definition of Done |
Scrum methodology for software development: when it fits and when it strains
Scrum suits a product that can be built in small, testable increments, with one person who can speak for the business and settle priorities within a day. Scrum methodology for software development strains when that person is hard to reach, when much of the work arrives as interruptions such as support tickets, or when a fixed outside deadline leaves no room to reorder the backlog.
A missing decision-maker stalls the team in the first case. In the second, a Kanban board often suits the support stream better while Scrum keeps the feature work moving. Settling that split at kickoff costs far less than finding it out in the third sprint. Agile software development with Scrum also depends on that decision-maker attending each sprint review, since the review is where scope gets traded against the date.
What a sprint in agile software development looks like, day by day
Take a two-week cycle. On the first morning the team and product owner agree a goal and pull the stories that serve it from the top of the backlog, sized against what the team actually finished last time. Each day after that opens with a short check on progress toward the goal, and blocked work gets raised there and sorted out straight afterward.
Midway, someone usually looks ahead and tidies the next stories so the following planning session is quick. The last day holds the review, where stakeholders see working software and react to it, followed by the retrospective, which is for the team alone. The length of a software development sprint is a choice: one week brings quicker reactions from stakeholders, while three or four weeks let bigger stories finish inside one cycle.
New requests that arrive mid-cycle go into the backlog unless they are urgent enough to justify changing the goal. That single habit protects most of the predictability clients are paying for.
Comparing scrum software development with kanban agile software development, and agile development vs scrum
Both are agile. Scrum works in fixed Sprints; Kanban manages a continuous flow of work with limits on work in progress. Kanban software development suits support and maintenance work, where requests arrive unpredictably and a fixed sprint plan would break in its first days.
| Factor | Scrum | Kanban |
|---|---|---|
| Cadence | Fixed-length Sprints | Continuous flow |
| Roles | Product Owner, Scrum Master, Developers | No prescribed roles |
| Change during work | Sprint scope protected | Items can change any time |
| Key metric | Sprint Goal achieved, velocity | Cycle time, throughput |
| Best for | Product development | Support, maintenance, operations |
Agile vs Scrum: is Scrum a methodology?
Agile is a set of values and principles, and Scrum is one specific way of following them. Framing agile development vs scrum as a choice between two rivals therefore misses the point: a team can be agile without Scrum, but a team that practices Scrum properly is following agile values. The Scrum Guide itself calls Scrum a lightweight framework rather than a methodology, which settles the common question of scrum or agile methodology: the two phrases are used loosely, but agile is the umbrella and Scrum is a framework inside it. In a scrum vs agile methodology comparison, Scrum prescribes roles, events and artifacts, while the agile methodology vs scrum distinction comes down to prescription: agile tells you what to value, and Scrum tells you what to do each week.
Agile vs waterfall at a glance
Waterfall completes each phase before the next begins; agile repeats all phases in short cycles. Gantt charts in software development belong to the first of those habits: they suit fixed phases with known dependencies, and they go stale quickly once each sprint can change the plan.
| Factor | Agile | Waterfall |
|---|---|---|
| Requirements | Evolve with feedback | Fixed up front |
| Delivery | Working software every few weeks | One delivery at the end |
| Customer involvement | Continuous | Mainly at start and end |
| Risk discovery | Early | Late |
| Best for | Products with uncertainty | Fixed, well-understood projects |
Agile delivery cycles, user stories and testing: agile software development cycles in practice
Agile work cycles are the sprints: each starts with planning, ends with a review and a retrospective, and delivers working software. Work is described as agile user stories (who, what, why), the project plan is a prioritized backlog with a release roadmap rather than a fixed Gantt chart, and testing happens inside every cycle through automated tests written with the code. For how agile compares with the other software development life cycle models, see the software development life cycle. That is the core difference in agile software development vs the waterfall model: feedback arrives every cycle, not after the final phase.
User stories, story points and epics
In agile software development user stories are short descriptions of a need written from the user’s side: as a type of user, I want something so that I get a benefit. A user story in agile development is deliberately small enough to finish in one cycle, which is why a larger need is written as an epic and then split into stories. Agile development epics bundle related stories under one goal, such as a new checkout flow, so the roadmap stays readable while the daily work stays small. Teams estimate each story in story points, a relative measure of effort and uncertainty rather than hours, and the user story agile methodology convention is to agree acceptance criteria before work starts. Agile methodology user story points are comparable only within one team, so do not use them to rank teams. Agile software development testing follows the same rhythm: tests are written alongside the code, run automatically on every change, and a story is not done until they pass. Project management tools for software development can track all of this, but only if the team marks a story done when those tests pass and not when the code is merged.
Want to see agile in practice?
Tell us about your project and we will show you how the first sprints would run.
Getting found in search
AI, AEO and what is changing
Paid media and lead generation
Websites and design
Choosing and working with an agency
Software and app development
- Mobile app development company
- Software development company
- Software consulting services
- AI consulting services
- UI/UX design services
- .NET development services
- Desktop application development
- Progressive web app development
- AR/VR app development
- Wearable app development
- EHR software development
- Hire dedicated developers
- Software development life cycle
- Web application development
- AI app development
- AI agent development
- AI chatbot development
- AI receptionist development
- AI integration services
- Cross-platform app development
- React Native app development
- Flutter app development
- Native app development
- iOS app development
- Android app development
- IoT app development
- MVP development
- SaaS development
- Enterprise app development
- App development outsourcing
- Hire app developers
- App development cost
- How to build an app
- App development tools
- Custom CRM development
- ERP development
- Web portal development
- Marketplace development
- Dashboard development
- API development
- Backend development services
- Healthcare software development
- Healthcare app development
- Telemedicine app development
- Fintech software development
- Insurance software development
- Logistics software development
- Manufacturing software development
- Real estate software development
- Education software development
- Retail software development
- Ecommerce app development
- Delivery app development
- Restaurant app development
- Fitness app development
- Dating app development
- Taxi app development
- Travel app development
- Social media app development
- Video streaming app development
- App development in NYC
- App development in Dallas
- App development in Los Angeles
- App development in Houston
- App development in Atlanta
- App development in Austin
- App development in Miami
- App development in Chicago
- App development in San Diego
Web development, platforms and hosting
Social, content and brand
By industry and by situation
Frequently asked questions
What is agile software development?
What are the four values of the Agile Manifesto?
When was the Agile Manifesto written?
What is the agile delivery process?
What is a sprint?
What is the difference between agile and Scrum?
What is Kanban?
What is lean software development?
Agile vs waterfall: which is better?
What are the phases of the agile SDLC?
How is security handled in agile?
What does a product owner do?
What is a retrospective?
What is the difference between agile and waterfall?
What is a user story?
What is a Scrum Master?
How long is a sprint?
What is a burndown chart?
Can agile work with fixed budgets?
What is DevOps?
What is an agile delivery methodology?
What does the agile work manifesto say?
What is the agile work process in practice?
What are agile user stories?
How does testing work in agile delivery?
What is an agile delivery project plan?
How do you write an agile software development project plan?
Which project management tools suit agile software development?
What metrics matter in agile software development?
Do you work as an agile software development company?
What is SAFe agile methodology?
What is an epic in agile development?
What is agile programming?
When did agile software development start?
What is agile methodology in simple terms?
What is the agile software development process improvement cycle?
Which agile software development terms should a client know?
What does agile software development team structure look like on a client project?
How much agile software development documentation does a project need?
What is agile Scrum software development, and what does each sprint deliver?
Need software built?We design, build and support custom software, web apps and SaaS platforms, with a written scope first.
Get a free marketing proposal
Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.
