Skip to main content Scroll Top

Agile Software Development: Process, Manifesto, Life Cycle and Scrum Explained

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
  1. What is agile software development?
  2. The Manifesto for agile delivery: the manifesto of agile software development
  3. What is the agile delivery process? The agile software development process, step by step
  4. The agile development life cycle
  5. What happens at the start and end of the agile software development life cycle?
  6. Scrum, Kanban and other agile frameworks
  7. Agile methodology of project management: how agile project management differs
  8. Agile vs waterfall software development
  9. Security in the agile delivery life cycle
  10. Agile and the MVP
  11. Agile application development when a new app replaces an old system
  12. How Progression Agency uses agile
  13. Scrum roles, events and artifacts
  14. Scrum methodology for software development: when it fits and when it strains
  15. What a sprint in agile software development looks like, day by day
  16. Comparing scrum software development with kanban agile software development
  17. Agile vs waterfall at a glance
  18. 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.

Value: Individuals and interactions. over processes and tools..
Value: Working software. over comprehensive documentation..
Value: Customer collaboration. over contract negotiation..
Value: Responding to change. over following a plan..
Lean: Eliminate waste. Build only what adds value..
Lean: Deliver fast. Small batches, frequent releases..

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 software development cycleThe agile software development cycle
Each cycle ends with working software, so feedback arrives every two weeks instead of at the end.

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.

Agile SDLC phases
PhaseWhat happens
ConceptDefine the problem, users and goals
InceptionForm the team, set up tooling, build the initial backlog
IterationDesign, code and test in sprints
ReleaseShip increments to users
MaintenanceSupport, monitor, fix
RetirementDecommission 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.

Agile vs waterfallAgile vs waterfall
Waterfall suits fixed, well-understood requirements; agile suits products where learning changes the plan.

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.

Scrum at a glance (2020 Scrum Guide)
ElementWhat it isTimebox or commitment
Product OwnerMaximizes product value; owns the Product BacklogAccountability
Scrum MasterEstablishes Scrum and helps the team improveAccountability
DevelopersCreate a usable Increment each SprintAccountability
SprintFixed-length cycle of workOne month or less
Sprint PlanningDecides why, what and how for the SprintUp to 8 hours for a one-month Sprint
Daily ScrumInspects progress toward the Sprint Goal15 minutes
Sprint ReviewInspects the outcome with stakeholdersUp to 4 hours
Sprint RetrospectivePlans improvements to quality and effectivenessUp to 3 hours
Product BacklogOrdered list of what is neededProduct Goal
Sprint BacklogSprint Goal plus selected workSprint Goal
IncrementUsable step toward the Product GoalDefinition 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.

Scrum vs Kanban compared
FactorScrumKanban
CadenceFixed-length SprintsContinuous flow
RolesProduct Owner, Scrum Master, DevelopersNo prescribed roles
Change during workSprint scope protectedItems can change any time
Key metricSprint Goal achieved, velocityCycle time, throughput
Best forProduct developmentSupport, 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.

Agile vs waterfall
FactorAgileWaterfall
RequirementsEvolve with feedbackFixed up front
DeliveryWorking software every few weeksOne delivery at the end
Customer involvementContinuousMainly at start and end
Risk discoveryEarlyLate
Best forProducts with uncertaintyFixed, 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.

Talk it through

Software and app development

Frequently asked questions

What is agile software development?
An iterative approach that delivers working software in short cycles and adapts based on feedback.
What are the four values of the Agile Manifesto?
Individuals and interactions, working software, customer collaboration and responding to change, each preferred over its counterpart.
When was the Agile Manifesto written?
In 2001, by seventeen software practitioners.
What is the agile delivery process?
A repeating cycle of backlog, sprint planning, build and test, daily standup, review, retrospective and release.
What is a sprint?
A fixed period, commonly two weeks, in which a team delivers a working increment.
What is the difference between agile and Scrum?
Agile is the philosophy; Scrum is a specific framework for practicing it.
What is Kanban?
An agile method that manages continuous flow of work on a visual board with work-in-progress limits.
What is lean software development?
Applying lean principles such as eliminating waste and delivering fast to software.
Agile vs waterfall: which is better?
Agile for evolving products; waterfall for fixed, well-understood requirements.
What are the phases of the agile SDLC?
Concept, inception, iteration, release, maintenance and retirement.
How is security handled in agile?
Built into every sprint through threat modeling, code review, automated scanning and testing.
What does a product owner do?
Owns the backlog and decides priorities based on value.
What is a retrospective?
A meeting at the end of a sprint to improve how the team works.
What is the difference between agile and waterfall?
Agile delivers in short iterations; waterfall moves through fixed phases once.
What is a user story?
A short description of a feature from the user’s perspective.
What is a Scrum Master?
The person who facilitates Scrum and removes obstacles.
How long is a sprint?
Commonly one to four weeks; two is typical.
What is a burndown chart?
A chart showing remaining work in a sprint.
Can agile work with fixed budgets?
Yes, by fixing time and budget and prioritizing scope.
What is DevOps?
Practices combining development and operations for fast, reliable releases.
What is an agile delivery methodology?
An agile work methodology is any framework that delivers software in short iterations with continuous feedback. Scrum, Kanban, Extreme Programming and SAFe are the most used; each applies the values of the Agile Manifesto in a different structure.
What does the agile work manifesto say?
The Manifesto for agile work, written in 2001, states four values and twelve principles: individuals and interactions, working software, customer collaboration and responding to change, valued over process, documentation, contracts and plans.
What is the agile work process in practice?
In practice the agile delivery process is a repeating loop: plan a short iteration, build a working increment, review it with stakeholders, adjust the backlog and repeat, with the product growing in usable steps rather than one late delivery.
What are agile user stories?
Short descriptions of a need from the user’s point of view, used to plan and prioritize work.
How does testing work in agile delivery?
Automated tests are written with the code and run every sprint; acceptance testing happens at each review.
What is an agile delivery project plan?
A prioritized backlog and a release roadmap, revised every sprint rather than fixed at the start.
How do you write an agile software development project plan?
Start with a prioritized backlog of user stories and a release roadmap that names the outcome expected from each release instead of a fixed list of tasks. Add a sprint length, a definition of done and a capacity estimate based on what the team actually finished in recent sprints, then revise the plan at every sprint review rather than locking it at kickoff. An agile software development project plan stays useful because scope can move while the dates, the budget and the next sprint goal remain visible.
Which project management tools suit agile software development?
Any tool that shows the backlog, the sprint board and the burndown to the whole team will do the job. Jira is the common choice for larger teams that need workflows and reporting, while Trello, Linear, Asana and ClickUp suit smaller teams that want a lighter board. Choose the one the team will keep current, because a stale board is worse than none. The best project management tools for software development matter less than the habits around them: a groomed backlog, a short sprint and a review at the end.
What metrics matter in agile software development?
Velocity (work finished per sprint), cycle time (how long an item takes from start to done), sprint burndown, defects found after release and release frequency are the usual set. Agile software development metrics exist to help the team spot trouble early, not to rank people, and velocity is only comparable within one team. Add one outcome measure, such as activation or conversion for the feature that shipped, so the numbers show whether the work mattered and not only whether it shipped.
Do you work as an agile software development company?
Yes. Progression Agency builds custom software, web apps and SaaS platforms in short sprints, with a written scope up front, a working build to review at the end of each sprint and a backlog that is reprioritized with you at every review. Tell us about the project and we will show you how the first sprints would run.
What is SAFe agile methodology?
SAFe, the Scaled Agile Framework, is a framework published by Scaled Agile, Inc. for applying lean and agile practices across many teams in a large organization. It adds portfolio, program and team levels above Scrum or Kanban. A single product team rarely needs it.
What is an epic in agile development?
An epic is a large piece of work that is too big to finish in one cycle, so the team splits it into smaller user stories. Epics bundle related stories under one goal, which keeps the roadmap readable while the daily work stays small.
What is agile programming?
Agile programming means writing software in short cycles with frequent testing, small releases and regular feedback, rather than writing everything to a fixed specification first. Practices such as pair programming, test-driven development and continuous integration come from Extreme Programming and support the agile approach.
When did agile software development start?
Agile software development was named in 2001, when seventeen practitioners published the Manifesto for Agile Software Development. The ideas were older, because iterative development, Scrum and Extreme Programming were already in use in the 1990s, and the manifesto gave them a shared name.
What is agile methodology in simple terms?
Agile methodology is a way of working that delivers something useful early, collects feedback and adjusts the plan in short cycles instead of planning everything up front. Teams choose a framework such as Scrum or Kanban to put it into practice.
What is the agile software development process improvement cycle?
It means changing how the team works in small steps, based on what the last few sprints showed. A retrospective picks one or two changes, the team tries them in the next sprint, and they stay only if defects, cycle time or predictability get better.
Which agile software development terms should a client know?
Backlog, sprint, increment, velocity and definition of done cover most conversations. Ask your team to define done in writing before the first sprint, because that one phrase decides whether a demo means finished, tested and releasable or merely started.
What does agile software development team structure look like on a client project?
Small and cross-functional: a handful of people who between them can design, build and test. The roles in agile software development stay the same on an agency project: someone on your side or ours owns priorities as product owner, a delivery lead keeps the process moving, and developers own the estimates.
How much agile software development documentation does a project need?
Enough for someone new to run, change and support the product without asking the original team. That normally means setup and deployment notes, architecture decisions with their reasons, API references and acceptance criteria on each story. Anything nobody will read again can stay in a conversation.
What is agile Scrum software development, and what does each sprint deliver?
Scrum is the framework teams use to run agile work in fixed-length Sprints: a Scrum Team of typically 10 or fewer people builds toward one Sprint Goal, and each Sprint ends with a usable Increment the business can inspect. Its events rest on the three pillars the Scrum Guide names, transparency, inspection and adaptation, so every review can change what gets built next.

Need software built?We design, build and support custom software, web apps and SaaS platforms, with a written scope first.

Get a software proposal

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.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us