| Common features of agile working |
| The time for doing the work is fixed, the scope of work completed is not fixed. Therefore the outcome at the end is uncertain. A minimum viable product is not guaranteed after the first, second or third releases. |
| Requirements that are not delivered are reprioritised into the next batch of work (often called a sprint). |
| Customer advocates are part of the teams, so that requirements can be rapidly changed as lessons are learnt about previous releases. |
| Teams are small and work closely together. |
| The way the team works is continuously reviewed and improved. |
| Documentation is kept to a minimum because the team constantly talk to each other . |
| It’s all about attitude, not process or method |
| Because releases are never far apart it is easy to keep up with customer experience and expectation. |
| The team is ‘self-organising’ where everybody has a leadership role – there is not an overall boss. |
| It has been conceived for delivering software in small but rapid batches. |
| Agile development is a great way of delivering continuously improving levels of software or undertaking a rapid prototype. It should not be seen as a faster way of delivering projects whose scope is fixed. |
