# What Is Agile? Meaning, Principles, Methods, Examples

> Agile is a software development approach built on short cycles. Learn the 4 values, 12 principles, Scrum, Kanban, XP, Agile vs Waterfall, and an example.

**URL:** https://www.ciptadusa.com/blog/agile-adalah  
**Type:** blog  
**Author:** PT Cipta Dua Saudara  
**Category:** Engineering  
**Published:** 2026-10-21  
**Cover:** https://www.ciptadusa.com/media/uploads/blog/2026-10/1792549576349-agile-adalah-20261021.webp  

## Article

Agile is an approach to software development that splits work into short cycles, releases usable results in increments, and adjusts the plan based on user feedback. Microsoft describes Agile as approaches to software development that emphasize incremental delivery, team collaboration, continual planning, and continual learning ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)). The term comes from the 2001 Manifesto for Agile Software Development, which sets out 4 values and 12 principles ([source](https://agilemanifesto.org/)).

Agile is not a single method. Scrum, Kanban, and Extreme Programming (XP) are frameworks that put Agile values into practice in their own ways. This article covers what Agile means, its history, its values and principles, Agile methods, Agile vs Waterfall, an example sprint in a business application project, and what a business owner should prepare when working with a vendor that uses Agile.

## What Agile Means

In everyday English, agile means quick and able to change direction easily. In software development, Agile is a way of working that does not wait until the whole system is finished before handing it over. The team builds part of the functionality, shows it to users, and uses their feedback to plan the next cycle.

Microsoft stresses that Agile is not a tool or a procedure you simply run. It is a mindset that drives an approach to software development, and the term covers a range of methods and practices that align with the values in the manifesto ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)).

Agile also does not replace the SDLC. The [SDLC](https://www.ciptadusa.com/en/blog/sdlc-adalah) is the framework of software development stages from planning to maintenance, while Agile is one model for running those stages in short, repeated cycles.

## A Short History of Agile

From February 11 to 13, 2001, seventeen people met at the Snowbird ski resort in Utah, United States. They represented Extreme Programming, Scrum, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and other approaches looking for an alternative to heavyweight, documentation-driven software processes. The meeting produced the Manifesto for Agile Software Development ([source](https://agilemanifesto.org/history.html)).

Some Agile methods therefore existed before 2001. Scrum, for example, was developed by Ken Schwaber and Jeff Sutherland from the early 1990s and first co-presented at the OOPSLA conference in 1995 ([source](https://scrumguides.org/scrum-guide.html)). The Agile Manifesto became an umbrella for the values these methods shared.

## The 4 Values of the Agile Manifesto

The Agile Manifesto states that its authors have come to value ([source](https://agilemanifesto.org/)):

1. **Individuals and interactions** over processes and tools.
2. **Working software** over comprehensive documentation.
3. **Customer collaboration** over contract negotiation.
4. **Responding to change** over following a plan.

The manifesto closes with an important line: while there is value in the items on the right, the items on the left are valued more ([source](https://agilemanifesto.org/)). In other words, Agile does not remove processes, documentation, contracts, or plans. It treats them as tools, not goals.

## The 12 Agile Principles

Behind the 4 values, the Agile Manifesto lists 12 principles. Here is a summary ([source](https://agilemanifesto.org/principles.html)):

1. Satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development.
3. Deliver working software regularly, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
4. Business people and developers work together daily throughout the project.
5. Build projects around motivated individuals, give them the environment and support they need, and trust them.
6. Convey information through face-to-face conversation.
7. Working software is the primary measure of progress.
8. Sponsors, developers, and users maintain a constant pace indefinitely.
9. Pay continuous attention to technical excellence and good design.
10. Simplicity, the art of maximizing the amount of work not done.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior.

For a business owner, principles 3 and 7 have a direct effect: project progress is measured by software you can try, not by a percentage in a report.

## Agile Methods and Frameworks

Microsoft describes Agile methods as frameworks that give comprehensive guidance across planning, development, delivery, and operations, while Agile practices are specific techniques such as collaborative estimation (planning poker) and continuous integration ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)). Here are three Agile frameworks and their characteristics.

### Scrum

The Scrum Guide defines Scrum as a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems ([source](https://scrumguides.org/scrum-guide.html)). The components of Scrum according to the 2020 Scrum Guide:

- **Scrum Team:** one Product Owner, one Scrum Master, and Developers, with no sub-teams or hierarchies. The team is small enough to stay nimble, with a reference point of 10 or fewer people.
- **Product Owner:** accountable for maximizing the value of the product and managing the Product Backlog, including ordering its items. The Product Owner is one person, not a committee.
- **Scrum Master:** accountable for establishing Scrum as defined in the Scrum Guide and for the team's effectiveness.
- **Sprint:** a fixed-length period of one month or less. A new Sprint starts immediately after the previous one ends.
- **Events within a Sprint:** Sprint Planning (up to 8 hours for a one-month Sprint), Daily Scrum (15 minutes), Sprint Review (up to 4 hours for a one-month Sprint), and Sprint Retrospective (up to 3 hours for a one-month Sprint).
- **Artifacts:** the Product Backlog (an ordered list of what the product needs), the Sprint Backlog (the plan for the Sprint), and the Increment (a usable piece of work).
- **Definition of Done:** a formal description of the quality a piece of work must meet. Work that does not meet it cannot be released or presented at the Sprint Review.

Source for all points above: [Scrum Guide 2020](https://scrumguides.org/scrum-guide.html).

### Kanban

Atlassian describes Kanban as a visual workflow management method: tasks are shown on a board, move through defined stages, and are limited in number so work does not pile up. The four principles of Kanban are visualize the workflow, limit work in progress (WIP), manage flow, and continuously improve ([source](https://www.atlassian.com/agile/kanban)).

Kanban has its roots in Toyota's production system in the late 1940s and was later adopted for software, IT, and operations work ([source](https://www.atlassian.com/agile/kanban)). A simple Kanban board has To Do, In Progress, and Done columns. A software team can add a Code Review column with a WIP limit, for example 2 tasks, so the team finishes reviews before starting new work ([source](https://www.atlassian.com/agile/kanban)).

### Extreme Programming (XP)

The Agile Alliance describes XP as an Agile framework that sets out engineering practices for software development in specific detail. The XP values are communication, simplicity, feedback, courage, and respect ([source](https://www.agilealliance.org/glossary/xp/)). Its practices include pair programming, test-first programming, continuous integration, a weekly cycle, and a target of building the whole system and running all tests automatically in ten minutes ([source](https://www.agilealliance.org/glossary/xp/)).

### Scrum vs Kanban vs XP

| Aspect | Scrum | Kanban | XP |
| --- | --- | --- | --- |
| Cadence | Fixed Sprints of one month or less | Continuous flow without Sprints | Weekly and quarterly cycles |
| Roles | Product Owner, Scrum Master, Developers | No prescribed roles | Customer, Developer, optional Tracker and Coach |
| Focus | Sprint Goal and a usable Increment | Smooth flow and WIP limits | Code quality and engineering practices |
| Change | Sprint plan is protected, changes go to the backlog | Priorities can change at any time | User stories are re-selected each week |

Table sources: [Scrum Guide](https://scrumguides.org/scrum-guide.html), [Atlassian Kanban](https://www.atlassian.com/agile/kanban), [Agile Alliance XP](https://www.agilealliance.org/glossary/xp/).

Atlassian notes that some teams blend Scrum and Kanban into Scrumban: fixed-length Sprints and roles come from Scrum, while WIP limits and cycle time come from Kanban ([source](https://www.atlassian.com/agile/kanban)).

## Agile vs Waterfall

Waterfall is a linear model that completes one phase before moving to the next: requirements, design, implementation, verification, and maintenance. The model traces back to Winston Royce's 1970 paper ([source](https://www.atlassian.com/agile/project-management/waterfall-methodology)).

| Aspect | Agile | Waterfall |
| --- | --- | --- |
| Workflow | Short, repeated cycles | Sequential phases, one pass |
| Requirements | Evolve throughout the project | Fixed at the start |
| Client involvement | Reviews results every cycle | Mainly at requirements and handover |
| First result you can try | At the end of an early cycle | After implementation is complete |
| Fits | Evolving requirements, client ready to take part | Stable requirements and predictable outcomes |

Table sources: [Atlassian](https://www.atlassian.com/agile/project-management/waterfall-methodology), [Agile Manifesto](https://agilemanifesto.org/principles.html).

Atlassian lists Waterfall's strengths as a clear structure, time and cost known upfront, and comprehensive documentation. Its limitations: limited room for client feedback once the requirements phase is done, and an issue in one phase can stall the whole project ([source](https://www.atlassian.com/agile/project-management/waterfall-methodology)). The four factors it suggests weighing are project complexity, organizational goals, team expertise, and stakeholder involvement ([source](https://www.atlassian.com/agile/project-management/waterfall-methodology)).

No model is better for every project. A comparison of other SDLC models such as the V-model, spiral, and RAD is in our article on the [SDLC](https://www.ciptadusa.com/en/blog/sdlc-adalah).

## Common Misconceptions About Agile

Microsoft lists several things Agile is not ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)):

- **Agile isn't cowboy coding.** Agile requires both a definition of done and explicit value delivered to customers in every sprint.
- **Agile isn't without rigor and planning.** Planning happens continually throughout the project, not just upfront.
- **Agile isn't an excuse for the lack of a roadmap.** Agile teams know where they are going and the results they want to achieve. Accepting change is different from pivoting every week.
- **Agile isn't development without specifications.** Specifications are still needed, sized right for the work at hand.

One more point from the Scrum Guide: implementing only parts of Scrum is possible, but the result is not Scrum ([source](https://scrumguides.org/scrum-guide.html)). A daily stand-up alone does not make a project Agile.

## Example: Agile in a Business Application Project

The following example is an illustration, not a specific client project. A distributor wants to replace a spreadsheet-based order log with a web application connected to customer data. The team uses two-week Sprints.

**Before the first Sprint.** The business owner appoints one person on the company side as Product Owner. Together with the vendor, they build a Product Backlog: order entry, customer list, delivery status, daily report, and WhatsApp integration. The backlog is ordered by business value. The team also agrees on a Definition of Done, for example: the feature is tested, has passed code review, and runs in the staging environment.

**Sprint 1.** Sprint Goal: the sales team can record orders and see the customer list. At the end of the Sprint, the Sprint Review shows features that can already be clicked through. The business owner notices there is no per-customer discount field yet, so that requirement goes into the backlog.

**Sprint 2.** The team works on delivery status and the discount field. Two warehouse admins try the result. The daily report is decided to be an Excel export for now, so the WhatsApp integration moves down in priority.

**Sprint 3 onward.** Features are released to users in stages. Before rolling out to the whole team, users run [UAT](https://www.ciptadusa.com/en/blog/uat-adalah) against the agreed acceptance criteria.

This pattern matches the idea of an [MVP](https://www.ciptadusa.com/en/blog/mvp-adalah): release the smallest usable version, then develop it further based on real use.

## Pros and Cons of Agile

Benefits for a business owner, based on the manifesto's values and principles:

- Software you can try is available earlier, so decisions are based on real results ([source](https://agilemanifesto.org/principles.html)).
- Changing requirements can be accommodated without waiting for the project to end ([source](https://agilemanifesto.org/principles.html)).
- Risk is limited per Sprint. The Scrum Guide states that shorter Sprints generate more learning cycles and limit the risk of cost and effort to a smaller time frame ([source](https://scrumguides.org/scrum-guide.html)).
- Progress is transparent because every Sprint ends with a review of the work done ([source](https://scrumguides.org/scrum-guide.html)).

Drawbacks and challenges:

- The client needs to set aside time for reviews and priority decisions. Atlassian treats stakeholder involvement as a deciding factor when choosing Agile ([source](https://www.atlassian.com/agile/project-management/waterfall-methodology)).
- Total cost and final scope are harder to pin down at the start than with Waterfall, where time and cost are known from planning ([source](https://www.atlassian.com/agile/project-management/waterfall-methodology)).
- Microsoft notes that time spent on demos and gathering feedback in each iteration reduces development time, although it can save rework time later ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)).

Because the cost of an Agile project depends on the number of Sprints and the agreed scope, also read about the components of [web application development cost](https://www.ciptadusa.com/en/blog/biaya-pembuatan-aplikasi-berbasis-web) and [application maintenance cost](https://www.ciptadusa.com/en/blog/biaya-maintenance-aplikasi) after launch.

## What to Prepare When Working with an Agile Vendor

If you hire a software house that works in an Agile way, prepare the following:

1. **One person who owns priorities.** The Scrum Guide sets the Product Owner as one person ([source](https://scrumguides.org/scrum-guide.html)). In a vendor project, this role is ideally held by someone on the business side with authority to decide.
2. **Time for reviews.** Schedule attendance at every Sprint Review. The Agile principles place daily collaboration between business people and developers at the foundation ([source](https://agilemanifesto.org/principles.html)).
3. **A Definition of Done and acceptance criteria.** Agree on when a feature counts as done before development starts.
4. **Change rules.** Ask how changes are logged and how their impact on schedule and cost is calculated.
5. **Access to the work.** Make sure you can try each Increment in a staging environment, not just watch a presentation.

More questions for assessing a vendor are in our [guide to choosing a software development company in West Java](https://www.ciptadusa.com/en/blog/pilih-jasa-pembuatan-software-jawa-barat-20260907). If you are not sure you need custom software yet, read [when a business needs custom software](https://www.ciptadusa.com/en/blog/kapan-bisnis-butuh-software-custom-2026).

## FAQ

### What kind of method is Agile?

Agile is an approach to software development that emphasizes incremental delivery, team collaboration, continual planning, and continual learning ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)). Agile itself is an umbrella of values and principles. Methods that put it into practice include Scrum, Kanban, and XP.

### What is the difference between Agile and Scrum?

Agile is the set of values and principles from the Agile Manifesto. Scrum is one Agile framework, with roles, events, and artifacts defined in the Scrum Guide ([source](https://scrumguides.org/scrum-guide.html)).

### What are the 4 Agile 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 ([source](https://agilemanifesto.org/)).

### How long is a Sprint?

The Scrum Guide sets a Sprint as a fixed-length period of one month or less ([source](https://scrumguides.org/scrum-guide.html)). The team chooses the exact length, for example one or two weeks.

### Is Agile only for software teams?

No. The Scrum Guide notes that Scrum has been adopted in many domains of complex work beyond software product development ([source](https://scrumguides.org/scrum-guide.html)), and Kanban is used in IT, operations, and marketing ([source](https://www.atlassian.com/agile/kanban)).

### Does Agile mean no documentation?

No. The Agile Manifesto still values documentation, it simply values working software more ([source](https://agilemanifesto.org/)). Microsoft also makes clear that Agile is not development without specifications ([source](https://learn.microsoft.com/en-us/devops/plan/what-is-agile)).

## Build Software in Increments with CDS

PT Cipta Dua Saudara builds web apps, mobile apps, internal dashboards, and API integrations in two-week sprints with a demo every Friday, and changing requirements are handled through the backlog and sprint reviews ([source](https://www.ciptadusa.com/en/services/software)). See our [custom software development](https://www.ciptadusa.com/en/services/software) service, or start with [IT consulting](https://www.ciptadusa.com/en/services/consulting) to map your processes and first-release priorities. We also build our own products such as [Zetta CRM](https://www.ciptadusa.com/en/incubating/zetta-crm), and you can see our work in our [portfolio](https://www.ciptadusa.com/en/works).


---

*Markdown version of https://www.ciptadusa.com/blog/agile-adalah — generated for AI agents and LLM crawlers.*