What is Agile?
Key takeaways
Agile combines a mindset with practical routines that help teams deliver value in changing conditions.Contents
- Agile prioritises working software, collaboration, and adapting plans based on frequent feedback.
- Iterative, incremental delivery reduces risk by surfacing issues and learning earlier.
- Scrum uses timeboxed sprints and clear roles to create a predictable cadence for delivery and review.Contents
- Kanban improves flow by visualising work and limiting work in progress to expose bottlenecks.
- Healthy Agile adoption relies on clear roles, shared quality standards, and sustainable pace.Definition of Agile
- Measure outcomes and flow with metrics like lead time and defect rate, then refine through retrospectives.
Definition of AgileApproach
AgileIterative, adaptive, and incremental refers to a set of principles and practices that guide teams in developing software products through incremental delivery, adaptive planning, and continual improvement. Agile emphasises iterative development, close team collaboration, and frequent customer feedback to deliver high-quality solutions quickly and efficiently.Popular frameworks
Agile methodology at a glanceScrum
| Aspect, Kanban, Extreme Programming (XP) | DescriptionStakeholders |
|---|---|
| PurposeCustomers, product owners, cross-functional teams, Scrum Masters | Deliver working software frequently, respond to change rapidlySummary of the Agile Manifesto and Its values |
| Key valuesThe | Individuals and interactions, working software, customer collaboration, responding to changeAgile Manifesto |
| Approach, published in 2001 by 17 software development experts, established the foundation for | Iterative, adaptive, and incrementalAgile methodologies |
| Popular frameworks. It promotes four core values and twelve underlying principles to guide teams toward continuous improvement and customer satisfaction. | ScrumAgile Manifesto: Four values, Kanban, Extreme Programming (XP)Individuals and interactions over processes and tools |
| StakeholdersWorking software over comprehensive documentation | Customers, product owners, cross-functional teams, Scrum MastersCustomer collaboration over contract negotiation |
Summary of the Agile Manifesto and Its valuesResponding to change over following a plan
The Agile principlesAgile ManifestoAgile is supported by twelve guiding principles, intended to help teams create successful products in an ever-changing environment. These principles inform day-to-day Agile practices., published in 2001 by 17 software development experts, established the foundation for Satisfy the customer through early and continuous delivery of valuable softwareAgile methodologiesWelcome changing requirements, even late in development. It promotes four core values and twelve underlying principles to guide teams toward continuous improvement and customer satisfaction.Deliver working software frequently, from a couple of weeks to a couple of months
Agile Manifesto: Four valuesCollaborate daily between business people and developers
- Individuals and interactions over processes and toolsBuild
- Working software over comprehensive documentationprojects
- Customer collaboration over contract negotiation around motivated individuals and provide support
- Responding to change over following a planConvey information face-to-face whenever possible
Agile principlesWorking software is the primary measure of progress
Agile is supported by twelve guiding principles, intended to help teams create successful products in an ever-changing environment. These principles inform day-to-day Agile practices.Maintain a sustainable development pace
- Satisfy the customer through early and continuous delivery of valuable softwareContinuous attention to technical excellence and good design
- Welcome changing requirements, even late in developmentSimplicity – the art of maximising the work not done – is essential
- Deliver working software frequently, from a couple of weeks to a couple of monthsSelf-organising teams produce the best architectures, requirements, and designs
- Collaborate daily between business people and developersRegularly reflect and adapt to improve effectiveness
- Build Historical origins and evolution of AgileprojectsThe Agile approach originated in the late 1990s as software teams sought alternatives to rigid project management models like the around motivated individuals and provide supportWaterfall
- Convey information face-to-face whenever possible model. In 2001, seventeen thought leaders signed
- Working software is the primary measure of progressthe Agile Manifesto
- Maintain a sustainable development pace, formalising Agile values and sparking the formation of the Agile Alliance. Since then, Agile has evolved beyond software development into
- Continuous attention to technical excellence and good designproject management
- Simplicity – the art of maximising the work not done – is essential, product development, and operations.
- Self-organising teams produce the best architectures, requirements, and designsBenefits of Agile
- Regularly reflect and adapt to improve effectivenessFlexibility:
Historical origins and evolution of Agile Respond rapidly to changing customer needs and market conditions.
The Agile approach originated in the late 1990s as software teams sought alternatives to rigid project management models like the Continuous improvement:Waterfall Regular retrospectives help teams adapt and improve their processes. model. In 2001, seventeen thought leaders signed Customer satisfaction:the Agile Manifesto Frequent delivery ensures customer requirements are met early and often., formalising Agile values and sparking the formation of the Agile Alliance. Since then, Agile has evolved beyond software development into Transparency:project management Iterative development and open communication foster stakeholder trust., product development, and operations.Reduced risk:
Benefits of Agile Incremental delivery allows for earlier issue detection and correction.
- Flexibility:Enhanced team collaboration: Respond rapidly to changing customer needs and market conditions. Cross-functional teams communicate daily to resolve challenges efficiently.
- Continuous improvement:Agile vs waterfall model Regular retrospectives help teams adapt and improve their processes.Aspect
- Customer satisfaction:Agile Frequent delivery ensures customer requirements are met early and often.Waterfall
- Transparency:Process Iterative development and open communication foster stakeholder trust.Iterative and incremental
- Reduced risk:Sequential and linear Incremental delivery allows for earlier issue detection and correction.Flexibility
- Enhanced team collaboration:Adaptive to change Cross-functional teams communicate daily to resolve challenges efficiently.Resistant to change after initial planning
| Adaptive to changeIssues often found late | Resistant to change after initial planningAgile frameworks and practices | |
| Customer involvementScrum framework | High, continuous feedbackScrum | Typically only during requirements and acceptance stages is a widely adopted Agile framework structured around short, timeboxed periods called |
| Deliverysprints | Frequent, partial releases. Teams maintain a | Full product delivered at project endproduct backlog |
| Risk of features and tasks, delivering increments of working software at the end of each sprint. Roles in Scrum include Product Owner, | Problems discovered earlyScrum Master | Issues often found late, and Development Team. Daily stand-ups, sprint planning, reviews, and retrospectives reinforce team collaboration and transparency. |
Agile frameworks and practicesKanban
Scrum frameworkKanban emphasises visualising work, limiting work in progress, and optimising flow. Teams use Kanban boards to track tasks and identify bottlenecks, often integrating continuous improvement practices.
ScrumUser stories and Product Backlog is a widely adopted Agile framework structured around short, timeboxed periods called Features are typically described as sprintsuser stories. Teams maintain a in a product backlog. This backlog is prioritised by the Product Owner and guides the work to be pulled into each sprint or iteration.product backlogAgile project management of features and tasks, delivering increments of working software at the end of each sprint. Roles in Scrum include Product Owner, Agile project managementScrum Master focuses on iterative planning, adaptive resource allocation, and continuous stakeholder engagement. Leaders support self-organising, cross-functional teams, encourage regular customer feedback, and facilitate incremental value delivery., and Development Team. Daily stand-ups, sprint planning, reviews, and retrospectives reinforce team collaboration and transparency.Key concepts: Iterative and incremental delivery
KanbanAgile projects proceed in small iterations, each resulting in an incrementally improved product. This iterative approach enables rapid adaptation, regular feedback, and incremental value to stakeholders.
Kanban emphasises visualising work, limiting work in progress, and optimising flow. Teams use Kanban boards to track tasks and identify bottlenecks, often integrating continuous improvement practices.Team collaboration and cross-functional teams
User stories and Product BacklogAgile emphasises collaboration between customers, stakeholders, and team members from diverse disciplines. Cross-functional teams are empowered to make decisions and deliver complete solutions within each iteration.
Features are typically described as Continuous improvement practicesuser storiesAgile teams conduct regular retrospectives to identify areas for improvement and adjust their processes. This culture of continuous improvement leads to increased quality, productivity, and team morale over time. in a product backlog. This backlog is prioritised by the Product Owner and guides the work to be pulled into each sprint or iteration.Further Resources
Agile project managementAgile software development (Encyclopaedia)
Scrum is an Agile framework that organises work into fixed-length sprints and uses roles like Product Owner and Scrum Master. Kanban is a visual method for managing workflow, limiting work in progress, and focusing on incremental improvements.
How does Agile improve team collaboration?
Agile improves collaboration through daily communication, cross-functional team structures, and regular stakeholder engagement, ensuring all members align towards shared goals.