SECTION 13 / 14
Agile approaches and practices
On this page 2 headings
The course introduces three Agile approaches.
| Approach | Simple meaning |
|---|---|
| Extreme Programming (XP) | One of the earliest agile approaches; key practices include Behavior Driven Design, test driven development and pair programming |
| Scrum | The product is built in a series of iterations called sprints, roughly 1–2 weeks long, breaking a big complex project into smaller bite-sized pieces |
| Kanban | The work is divided into small work items represented on a Kanban board, so team members can see the state of every piece of work at any given time |
Agile practices
| Practice | Meaning in easy English |
|---|---|
| User stories | A short statement of a user’s need |
| Sprints | Iterations in which the team builds the product |
| Scrum stand-up meetings | Short team meetings to coordinate work |
| Test-driven development | Write a test for desired behavior before writing code to make it pass |
In this course, practices from XP and Scrum — behavior driven design, test driven development, sprints — are used for the group projects.
Kanban: see work moving across a board
A Kanban board shows the state of every work item at any given time.
Agile philosophy: Rather than just following approaches and practices, Agile is about adhering to the broad philosophy — the 4 key principles — and using them to figure out the right things to do in your particular context.