Assessment of Success Measures and Challenges of the Agile Project Management

  • Tatiana KovalevaEmail author
Conference paper
Part of the Lecture Notes in Networks and Systems book series (LNNS, volume 95)


Since every project is unique, there is no ideal project management system suitable for each type of projects. However, during the existence of the project management, many effective approaches, methods and standards have been created. One of these methodologies is the agile one, which was originally created for software development. That is why this methodology is most often used in the IT industry. However, this does not prevent the usage of the agile method (hereinafter Afile) by many non-technical teams. Non-IT companies quickly discovered the benefits of using flexible thinking and some Agile practices that can help businesses achieve better performance. The most important advantage of Agile is its flexibility and adaptability. It can be adapted to almost any conditions and processes of the organization. That is what determines its current popularity and explains why so many systems for different areas have been created on its basis. At the same time, the results of transformation do not always coincide with the expectations. This paper sets out the success measures with the Agile projects. The challenges that companies most often encounter are evaluated and the dependence of the trend in the popularity of Agile techniques on the success of the methodology implementation is studied based on the large-scale surveys of Agile at companies in Russia and worldwide.


Agile method Project management Software engineering 


  1. 1.
    Wysocki, R.K.: Effective Project Management, Traditional, Agile, Extreme, 6th edn. Wiley, Hoboken (2011)Google Scholar
  2. 2.
    Stare, A.: Agile project management. A future approach to the management of projects? Dyn. Relat. Manag. J. 2(1), 21 (2013)Google Scholar
  3. 3.
    Guleria, P.G., Sharma, V., Arora, M.: Development and usage of software as a service for a cloud and non-cloud based environment - an empirical study. Int. J. Cloud Comput. Serv. Sci. (IJ-CLOSER) 2(1), 50–58 (2013)Google Scholar
  4. 4.
    Fowler, M., Highsmith, J.: The Agile manifesto. Softw. Dev. 9(8), 28–35 (2001)Google Scholar
  5. 5.
    13th annual state of Agile report. CollabNet VersionOne (2019)Google Scholar
  6. 6.
    Agile v Rossii 2018: Otchet o ezhegodnov issledovanii. [Adgile in Russia 2018. Annual survey report] ScrumTrek (2018). (Russian)Google Scholar
  7. 7.
    Schwaber, K.: Agile Project Management with Scrum, pp. 8–20. Microsoft Press, Redmond (2004)Google Scholar
  8. 8.
    Kniberg, H., Skarin, M.: Kanban and Scrum - Making the Most of Both, pp. 10–30., Morrisville (2010)Google Scholar
  9. 9.
    12th annual state of Agile report. CollabNet VersionOne (2018)Google Scholar
  10. 10.
    11th annual state of Agile report. CollabNet VersionOne (2017)Google Scholar
  11. 11.
    10th annual state of Agile report. CollabNet VersionOne (2016)Google Scholar
  12. 12.
    9th annual state of Agile report. CollabNet VersionOne (2015)Google Scholar
  13. 13.
    Agile v Rossii 2017: Otchet o ezhegodnov issledovanii. [Adgile in Russia 2017. Annual survey report]. Oтчeт o eжeгoднoм иccлeдoвaнии. ScrumTrek (2017). (Russian)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.Peter the Great St. Petersburg Polytechnic UniversitySt. PetersburgRussia

Personalised recommendations