[1. PMI. Pulseof Profession. 2017, 26 July 2019. https://www.pmi.org/]Search in Google Scholar
[2. Mishra, D., A. Mishra. Complex Software Project Development: Agile Methods Adoption. – Journalof Software Maintenanceand Evolution: Researchand Practice, Vol. 23, 2011, No 8, pp. 549-564.10.1002/smr.528]Search in Google Scholar
[3. Beck, K., etal. Manifestofor Agile Software Development. 2001. https://agilemanifesto.org/]Search in Google Scholar
[4. Matta, M., M. Marchesi. Understanding Approval Ratingof Agile Project Management Tools Using Twitter. – In: Proc. of 10th International Joint Conferenceon Software Technologies (ICSOFT'15), IEEE, 2015.10.5220/0005557201680173]Search in Google Scholar
[5. Versionone. 8th Annual Stateof Agile Survey, 2013. http://www.versionone.com/pdf/2013-state-of-agile-survey.pdf.]Search in Google Scholar
[6. Mishra, A., D. Mishra. Software Project Management Tools: A Brief Comparative View. – ACM SIGSOFT Software Engineering Notes, Vol. 38, 2013, No 3, pp. 1-4.10.1145/2464526.2464537]Search in Google Scholar
[7. Lin, J., etal. Studying Task Allocation Decisionsof Novice Agile Teamswith Datafrom Agile Project Management Tools. – In: Proc. of 29th ACM/IEEE International Conferenceon Automated Software Engineering, ACM, 2014.10.1145/2642937.2642959]Search in Google Scholar
[8. Hanakawa, N., K. Okura. A Project Management Support Tool Using Communicationfor Agile Software Development. – In: 11th Asia-Pacific Software Engineering Conference, IEEE, 2004.]Search in Google Scholar
[9. Versionone I. 8th Annual Stateof Agile Survey. VersionOne. 2014, Inc.]Search in Google Scholar
[10. Raith, F., I. Richter, R. Lindermeier. How Project-Management-Toolsare Usedin Agile Practice: Benefits, Drawbacksand Potentials. – In: Proc. of 21st International Database Engineering & Applications Symposium, ACM, 2017.10.1145/3105831.3105865]Search in Google Scholar
[11. Boehm, B., R. Turner. Management Challengesto Implementing Agile Processesin Traditional Development Organizations. – IEEE Software, Vol. 22, 2005, No 5, pp. 30-39.10.1109/MS.2005.129]Search in Google Scholar
[12. Damian, D. E. H., etal. Using Different Communication Mediain Requirements Negotiation. – IEEE Software, Vol. 17, 2000, No 3, pp. 28-36.10.1109/52.896247]Search in Google Scholar
[13. Babar, M. A., B. Kitchenham, R. Jeffery. Comparing Distributedand Face-to-Face Meetingsfor Software Architecture Evaluation: A Controlled Experiment. – Empirical Software Engineering, Vol. 13, 2008, No 1, pp. 39-62.10.1007/s10664-007-9052-6]Search in Google Scholar
[14. Babar, M. A., etal. An Empirical Studyof Groupware Supportfor Distributed Software Architecture Evaluation Process. – Journalof Systemsand Software, Vol. 79, 2006, No 7, pp. 912-925.10.1016/j.jss.2005.06.043]Search in Google Scholar
[15. Azizyan, G., M. K. Magarian, M. Kajko-Matsson. Surveyof Agile Tool Usageand Needs. – In: 2011 Agile Conference, IEEE, 2011.10.1109/AGILE.2011.30]Search in Google Scholar
[16. Ebert, C. Managing Global Software Projects Software Project Managementina Changing World. G. Ruhe, C. Wohlin, Eds. Springer, 2014.10.1007/978-3-642-55035-5_9]Search in Google Scholar
[17. Highsmith, J. R. Agile Project Management: Creating Innovative Products. Pearson Education, 2009.]Search in Google Scholar
[18. Jira Software. July 26 2019. https://www.atlassian.com/software/jira.]Search in Google Scholar
[19. Rodríguez, J. P., C. Ebert, A. Vizcaino. Technologiesand Toolsfor Distributed Teams. – IEEE Software, Vol. 27, 2010, No 5, pp. 10-14.10.1109/MS.2010.126]Search in Google Scholar
[20. Perez, J. J., S. Guckenheimer. Software Engineeringwith Microsoft Visual Studio Team System. Pearson Education, 2006.]Search in Google Scholar
[21. Dubakov, M., P. Stevens. Agile Tools: The Good, the Badandthe Ugly. Report, Target Process, Inc, 2008.]Search in Google Scholar
[22. Taheri, M., S. M. Sadjadi. A Feature-Based Tool-Selection Classificationfor Agile Software Development. – In: SEKE, 2015.10.18293/SEKE2015-234]Search in Google Scholar