10 Key Principles of Agile Software Development
Agile Development is one of the big buzzwords of the software development industry. But what exactly is it? Agile Development is a different way of managing software development projects. The key principles, and how Agile Development fundamentally differs from a more traditional Waterfall approach to software development, are as follows:
- Active user involvement is imperative
- The team must be empowered to make decisions
- Requirements evolve but the timescale is fixed
- Capture requirements at a high level; lightweight & visual
- Develop small, incremental releases and iterate
- Focus on frequent delivery of products
- Complete each feature before moving on to the next
- Apply the 80/20 rule
- Testing is integrated throughout the project lifecycle – test early and often
- A collaborative & cooperative approach between all stakeholders is essential
There are various methodologies and standards that address various aspects of software development, for instance PRINCE2 for Project Management, Use Cases/UML for Analysis and Design, ISEB for Testing. Although these are typically applied to Waterfall development projects, elements of these methods can also be applied in an Agile Development approach.
Methods Specifically Designed Around Agile Development
- DSDM is probably the original Agile Development method. DSDM was around before the term Agile Development was even invented, but is absolutely based on all the principles we’ve come to know as Agile Development.
- SCRUM is also an Agile Development method, which concentrates particularly on how to manage tasks within a team-based development environment.
- XP (eXtreme Programming) is a more radical Agile methodology, focusing on the software development process and addressing the analysis, development and test phases with novel approaches aimed at making a substantial difference to the quality of the end product.
- DSDM is probably the most complete Agile methodology, whereas SCRUM and XP are easier to implement and complementary because they tackle different aspects of development projects and are both founded on the same principles of Agile Development.
In reality, there is no magic bullet for software development. The real trick is to know lots of techniques from various Waterfall and Agile Development methods, and to select a mixture of the best approaches that are most appropriate for any given situation. To do this reliably with any degree of success really requires a lot of experience and skill.
In Agile Development projects, Project Management takes a slightly different form, relying more on the project manager’s skills in communication, facilitation, coordination, and emphasising less on planning and control.
Agile Development can be a very exciting and invigorating approach, although some projects suit Agile Development more than others. The collaboration and visibility can provide a much richer and more rewarding experience for teams to develop great software products. Agile Development can be a lot more enjoyable than the staid Waterfall approach that requires lots more documentation and is less flexible by its nature. And when people enjoy their work, it’s amazing what they can achieve!