Status Quo (Scaled) Agile
4th study on Benefits and Success factors of agile methods
The fourth study "Status Quo (Scaled) Agile" has been completed.
We would like to thank more than 800 participants from more than 20 nations.
We are currently working on the final report. If you are interested in the final report, please send an email with the subject "Status Quo (Scaled) Agile" to info
Participants will automatically receive the detailed final report upon completion.
Motivation for the implementation of the fourth international study "Status Quo (Scaled) Agile"
Agile methods such as Scrum, IT-Kanban or Design Thinking gained a lot of importance during recent years. It seems like almost every renowned company switched to the usage of agile methods for their IT development. During the last few years agile methods gained tremendous importance in areas like product development, process optimization, implementation of ERP systems Standard Software System (SSW), etc.
But how successful and widespread are agile methods? Which forms of usage are common?
How does the interaction of several agile teams work - if applicable using methods such as Nexus, SAFe, Spotify or LeSS?
How are agile and classical approaches combined to hybrid methods?
Which factors are decisive for satisfaction and success?
The new edition of ”Status Quo (Scaled) Agile” examines how the usage of agile methods is changing. Special focus will be place on the actual forms of usage, the successes and the interaction with classic project management and scaling of agile methods as well.
The study "Status Quo (Scaled) Agile" examines these and other questions.
How are agile methods like Scrum and IT-Kanban uses in practice?
Which challenges promotes a succesful implementation of agile methods?
How do users combine classic project management with agile methods (hybrid methods)?
How can agile methods be scaled (Nexus, SAFe, Spotify, LeSS, ...)?
How successful are agile methods?
How are agile methods going to be integrated in the project portfolio of the management?
Results of the last study "Status Quo Agile (2016/17)"
A total of over 1,000 people from over 30 countries took part. More details on the structure of the participant survey period, used tools etc are documented in the final report. The Status Quo agile 2016/2017 study is already the third international survey according to previous studies in 2012 and 2014.
Study was carried out in collaboration with the GPM - German Association for project management, IPMA – International Project Management Association and Scrum.org.
You can require the free report here.
The success rate of agile methods is still much more positive than that of classical project management.
Once again consistently agile users had the highest rate of success. - also in comparison to hybrid or selective users.
Agile methods continue to be used primarily in software development, but already 40% and 34% of participants use agile methods for "only" IT-related or non-IT activities. (Several answers were possible)
About 39% stated that he is supported by a traditional project manager or even acts like a traditional project manager.
Only a very small portion (< 5%) of the participants see lower quality or a lack of discipline as a result of agile methods. This assessment is also shared by the users of classic project management (7%).
The evaluation of the success of agile methods is still very positive, but slightly less "enthusiastic" than in previous surveys.
Only 7% of the respondents state that agile methods do not lead to an improvement in results and efficiency.
With 85%, the most used method is Scrum. Kanban, Lean and DevOps follow.
Almost three fifths of the respondents stated, that they use a 2-week Sprint cycle
72% of the users of agile methods stated that change is an integral part of the company policy. Only 50% of the users of classic project management stated the same.
The top 3 reasons to work with agile methods are improving time to market, improving quality and reducing project risk.
The majority of users of agile methods use them selectively or in combination.
91% see the improvements as (very much) higher than the effort needed to introduce agile methods.
A size of 5-9 persons clearly dominates in agile teams.
69% of the Kanban teams have a product owner.
Product Owner Shadow and Scrum Master Shadow are not uncommon. Proxy Product Owners are widespread (> 50%).
Only one third of the participants has substantial reasons to not use agile methods – e.g. effort too high or too expensive. One third is planning to deal with the topic. One third is missing the basic knowledge about agile methods.
Prof. Dr. Ayelt Komus, professor of organization and business informatics at Koblenz University of Applied Sciences, is a coach, management consultant, keynote speaker and author.
Komus refers to over 80 publications, over 170 keynotes and lectures, as well as more than 180 interviews/reports in the specialist media. He is the director of the BPM-Labor for Business Process Management and Organizational Excellence.
He is co-initiator of the Modellfabrik Koblenz (model factory), the Praxisforum - Prozess und IT-Management (www.praxisforum.net).
Komus is a recognized author, keynote speaker, consultant and coach in the fields of process, project and IT-management and agile methods. His highly regarded empirical studies include the studies "agiles PMO“ (Agile PMO), "Erfolgsfaktoren im Projektmanagement“ (Success factors for PM), "Positionsbestimmung S/4HANA", "Status Quo PEP" and “Status Quo Agile" (2012, 2014 and 2016).
For further information please contact the BPM-laboratory info.