Answer: Agile methodologies are iterative and incremental ways of developing software in short cycles, with close customer involvement and readiness to change. Common ones are Scrum, Extreme Programming (XP), Kanban, Lean, Feature Driven Development (FDD), DSDM and Crystal. Scrum is explained below.
Features of agile methodologies (from the Agile Manifesto):
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
- Work is delivered in short iterations (1–4 weeks), each producing a working increment; feedback after every iteration improves the next one.
Scrum
Scrum is a lightweight agile framework in which a small, self-organising, cross-functional team delivers the product in fixed time-boxes called sprints.
Roles:
- Product Owner: represents the customer, owns and prioritises the product backlog.
- Scrum Master: coaches the team in Scrum, removes obstacles, runs the events smoothly.
- Development team: usually 3–9 people who design, build and test the increment.
Artifacts:
- Product backlog: ordered list of all features (user stories) wanted in the product.
- Sprint backlog: items chosen for the current sprint plus the tasks to finish them.
- Increment: the working, potentially shippable product at the end of the sprint.
Events / life cycle (diagram in words: Product backlog → Sprint planning → Sprint backlog → Sprint of 1–4 weeks with a loop for the Daily Scrum → Increment → Sprint review → Sprint retrospective → back to the next sprint):
- Sprint planning: team picks top backlog items and plans how to build them.
- Sprint: a time-box of one month or less in which the increment is built; the next sprint starts right after.
- Daily Scrum: 15-minute daily stand-up: what was done, what will be done, any blockers.
- Sprint review: the increment is shown to stakeholders and feedback updates the backlog.
- Sprint retrospective: the team discusses what went well and what to improve in the next sprint.
- Release: when enough increments are complete, the product is released.
Advantages: fast delivery of working software, quick response to changing requirements, high customer satisfaction, visible progress.
Disadvantages: hard to predict final cost and time, needs experienced and committed team members, less documentation, not ideal for very large or fixed-contract projects.