Agile approaches are not new; they have been around since 2001. This was the year in which the agile manifesto (which included the four values and the twelve principles), was founded by seventeen prominent software developers. However, it still took a while before agile approaches were fully embraced by IT organizations. Only during the last five years did it substantially increase as such. In 2010, the use of Agile approaches amounted to less than 20%, while in 2014 it increased to nearly 80% (see figure 1).
About 70% of the organizations, which use an agile approach work with Scrum. Less than 15% of the organizations use a different approach, such as Kanban, Feature Driven Development, Agile Unified Process, DSDM/Atern, Lean or Extreme Programming.
Another interesting trend is the reduction of agile approaches in outsourcing trajectories. Five years ago this amounted to nearly 80% while now this amounts to less than 40% (see figure 2).
If an organization is requested to provide feedback in respect to the satisfaction of the result of an agile project then more than 50% responds satisfactorily. This is quantified through an assumed productivity increase of 0 to 50% with an average of 20%, a cost reduction of 0 to 50% with an average of 30% and a quicker time-to-market of 10 to 60% with an average of 30%.
In the subsequent parts of this series, we will bring you the five agile misconceptions, five agile pitfalls, five agile benefits, and five agile success factors. All of these are based on five years of experience as an agile consultant and agile trainer for more than 300 agile projects within the Netherlands and abroad. Notwithstanding the fact that these are mostly 300 subjective opinions, it does in the end provide an objective image of the current situation in respect to agile projects. Stay tuned for more!
About Leo van der Aalst
Leo van der Aalst is Dutch and studied chemistry, mathematics, physics and biology. However, he switched over to IT almost thirty years ago. After having gone through the classic IT path - from programmer to program manager - he became a specialist in the testing area, in which he held functions such as test manager, test advisor, research & development manager, line manager and agile coach. Leo applied his knowledge and experience in the project- and test management field during a number of international projects and consultancy trajectories (in USA, Germany, Denmark and Austria). He also likes to share his knowledge with other people by writing books and articles, and giving presentations en workshops. Leo is co-author of TMap NEXT® for result-driven testing, TMap NEXT® Business Driven Test Management, TMap® Human Driven and TMap NEXT® in scrum books. He has written many articles (e.g. ‘Software Testing as a Service - STaaS’), which can be found through his website (http://leovanderaalst.nl). Leo is past professor Software Quality at Fontys University Eindhoven in the Netherlands, a much sought-after teacher of test training and a regular speaker at national and international conferences. Leo is an accredited trainer for courses as Certified Agile Tester (CAT), ISTQB Agile-Tester and TMap Suite Test Engineer and Test Master. Besides all this, Leo is development lead of the ISTQB Foundation and Advanced Agile-Tester Syllabi - which are chaired by Rex -, member of the programme committee of the (Dutch) National Software Quality Conference, fellow of SogetiLabs and member of Capgemini Expert Connect.
More on Leo van der Aalst.