agile-methodology
A type of project management process that is used for software development, where demands and solutions evolve through the collaborative effort of self-organizing and cross-functional teams.
Agile methodology is a project management and software development framework that prioritizes iterative development, collaboration, customer feedback, and rapid adaptation to change. Unlike traditional 'waterfall' models where requirements are fixed upfront and development proceeds linearly through distinct phases (requirements, design, implementation, testing, deployment), Agile breaks projects into small, manageable increments called sprints or iterations. Each iteration typically lasts 1-4 weeks and results in a potentially shippable product increment. Key principles include 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, as outlined in the Agile Manifesto. Common Agile frameworks include Scrum, Kanban, Extreme Programming (XP), and Lean. Scrum, for instance, utilizes roles like Product Owner, Scrum Master, and Development Team, along with events such as daily stand-ups, sprint planning, sprint reviews, and sprint retrospectives. Kanban focuses on visualizing workflow, limiting work in progress (WIP), and managing flow. The core trade-off is a shift from upfront predictability and comprehensive documentation to flexibility and continuous delivery, which can sometimes lead to scope creep if not managed carefully, but generally results in higher customer satisfaction and faster time-to-market for valuable features. Continuous integration and continuous delivery (CI/CD) practices are often tightly integrated with Agile methodologies.
graph LR
Center["agile-methodology"]:::main
Rel_continuous_deployment_cd["continuous-deployment-cd"]:::related -.-> Center
click Rel_continuous_deployment_cd "/terms/continuous-deployment-cd"
Rel_site_reliability_engineering_sre["site-reliability-engineering-sre"]:::related -.-> Center
click Rel_site_reliability_engineering_sre "/terms/site-reliability-engineering-sre"
Rel_functional_programming["functional-programming"]:::related -.-> Center
click Rel_functional_programming "/terms/functional-programming"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Knowledge Check
🧒 Explain Like I'm 5
Agile is like building a house room by room instead of trying to build the whole thing at once. You build a small room, live in it, see what you like and what you don't, and then use that knowledge to build the next room better. It lets you change your mind as you go!
🤓 Expert Deep Dive
Agile methodologies, fundamentally, are rooted in a set of values and principles advocating for adaptive planning, evolutionary development, early delivery, and continuous improvement. Architecturally, this translates to systems designed for modularity and loose coupling, facilitating frequent integration and deployment (CI/CD pipelines).
In Scrum, a popular framework, project progression is managed through fixed-length iterations called Sprints (typically 1-4 weeks). Each Sprint begins with a planning meeting where the team commits to a subset of the Product Backlog, forming the Sprint Backlog. Daily Stand-ups (Scrum meetings) ensure synchronization and impediment identification, fostering transparency. At the Sprint Review, stakeholders inspect the increment, and the Sprint Retrospective allows the team to optimize its processes.
Key metrics often tracked include Velocity (story points completed per sprint), Cycle Time (time from start to finish for a work item), and Lead Time (time from request to delivery). The underlying principle is to minimize work-in-progress (WIP) and maximize feedback loops, often aligning with Lean principles. For instance, Kanban visualizes workflow on a board, using WIP limits to control flow and identify bottlenecks. The mathematical underpinnings can be seen in queueing theory applied to optimize throughput and minimize latency in the delivery pipeline.