Iterative delivery with sprints and continuous feedback.
Agile values working software, collaboration and responding to change. Scrum organises work into sprints (1–4 weeks) with roles (product owner, scrum master, team), backlog, daily stand-up, review and retrospective. Kanban visualises flow and limits work in progress.
A two-week sprint delivers a small, tested feature increment.
Agile methods deliver working software in short cycles and adapt to changing needs, which suits projects where requirements evolve.
Iterative delivery with sprints and continuous feedback.
Agile methods deliver working software in short cycles and adapt to changing needs, which suits projects where requirements evolve.
A fixed time box, often one to four weeks, in which a team builds a set of planned features.
Defined roles such as product owner and scrum master, plus ceremonies like planning, review and retrospective.
Typical applications include running two-week sprints to deliver a web feature with user feedback, holding daily stand-ups to resolve blockers quickly and reviewing a product backlog to decide what to build next.
Study "Software development life cycle" first (topic 45 of 104 in Software & Computing). It covers the groundwork this topic builds on.
User stories. Velocity. Continuous improvement.
A two-week sprint delivers a small, tested feature increment.
The next topic is "Requirements engineering", which builds directly on this one.
It is classed as Intermediate in Software & Computing (topic 46 of 104). It is an intermediate topic. Work through the beginner topics in Software & Computing first.
Want to practise? Open the interactive course for quick checks, quizzes, simulations and progress tracking.