What types of projects can Agile be applied to?
Types of projects that may suit Agile?
Many people are understandably asking this question – “what kinds of projects can Agile be applied to”? The single biggest difference between being able to use Agile or a more Waterfall approach is the ability to be able to formally release end product in increments.
Incremental development can be possible (and even be very desirable) on many projects, not just software development. It is also a major way to manage the risk that can be present in a more ‘big-bang’ type of development processes. For example, if a New Product Development project would benefit from this and it is entirely feasible from a commercial and technical perspective, then Agile could work very well. Clearly though, if we have a project such as building a new bridge for example, using Agile won’t work.
Examples of projects where Agile is suitable or may be possible:
- Small to medium sized software developments.
- Product development where multiple variants are required or desirable.
- Where the main deliverable can be broken down and produced (and even potentially released or at least accepted by the end customer) in incremental discrete packages.
Also, anywhere you find very dynamic requirements, which are able or likely to evolve per iteration, could take advantage of a more Agile approach.
Some people argue that Agile should be used when time is critical. I do not buy this as a solid criteria. I do agree that Agile can result in a more fit-for-purpose end product faster than may be possible using traditional approaches. However this is because early release, review and feedback on products, results in far less re-work than might otherwise be the case. It can also produce a far more controlled process. Those are the key pieces that ultimately save time.
Are there Agile Practices that all projects could benefit from?
For all projects though, there are certainly other practices that Agile (did not invent but) has adopted and widely promotes, that any project of any type and size could benefit from. For example:
- Bringing developers and users closer together and interacting more frequently during the whole of the definition and development phases.
- Making reviews (of progress) shorter and more frequent.
- Communication – using two-way communication methods for all key communication on the project. This should always be face-to-face where possible, and where not, should involve two-way forms of communication at least.
- Developing a collaborative development environment, where all parties focus on the way-ahead when there are issues, as opposed to sinking back into their respective contractually bound corners.
Very few projects in the world would not benefit from such practices, if they do not already exist, in a manner that is both successful and productive.
Contact Us Now
Email us today to find out more on how we can help you.