Loading content
Agile software development is a set of principles and practices that emphasize iterative delivery, customer collaboration, and adaptive planning. It organizes work into short increments, supports continuous feedback, and prioritizes value over strict processes. Agile applies across teams and organizations to improve responsiveness and learning.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Agile software development is a principle-and-practice framework for building software under uncertainty. It organizes work into short increments, seeks early feedback from users and stakeholders, and continually adjusts priorities, collaboration, and planning.
Agile software development took shape around the 2001 Manifesto for Agile Software Development. Its 17 signatories reacted against heavyweight, documentation-driven processes that made fast feedback and change difficult. Agile has since served as an umbrella for principles of iterative work, customer collaboration, and value orientation; concrete methods such as Scrum and XP developed around it.
Picture a repeating learning loop: the team picks the smallest useful next goal, delivers a usable increment, inspects user response and technical signals, then replans. Rather than relying on one long upfront plan, a short cadence of backlog refinement, review, and retrospective steers the work. Direction stays stable while the path changes as new information arrives.
Work is split into small, usable slices so value can emerge early.
Feedback from use, review, and measurement shapes the next step.
Plans are updated as new knowledge or shifting priorities appear.
Close contact with users and sponsors helps refine requirements continuously.
A team combines the needed skills and decides within clear goals on its own.
Agile is useful when requirements are still changing, products are being discovered step by step, or early learning matters more than a fixed up-front plan. It still requires real decision authority, access to stakeholders, and disciplined technical quality; without those conditions, “agile” easily degrades into frantic mini-waterfall work.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.