Kiedy warto stosować metodyki zwinne (agile methodologies) w zarządzaniu projektami wytwarzania oprogramowania?

• Authors: Mirosława Lasek , Aleksandra Adamus

Title variants

EN

When is it worth to use agile methodologies in software development project management practice?

• Languages of publication: PL EN

Abstracts

EN

The article presents increasingly popular agile methodologies that are more and more often used for projects management of software development. The aim of this article is to analyze the concept of agility and agile methodologies, as well as to find an answer to the question when it is worth to use such methodologies which require organizational effort associated with their use, acquisition of the necessary skills and covering the necessary costs. We consider agile methodologies as the specific project management methodologies in software development. Therefore the article describes their role in the development of agile IT infrastructure, agile organizational culture, and issues related to the possibility of assessing the level of methodologies' agility, as well as the possibility of evaluation the purposefulness and benefits of using them in software development practice.

Keywords

EN

project management; software development; agile methodologies; evaluation of software design methodologies; evaluation of IT projects

• Publisher: Wydawnictwo Uniwersytetu Ekonomicznego we Wrocławiu
• Journal: Informatyka Ekonomiczna
• Year: 2014
• Issue: 1(31)
• Pages: 157-172

Contributors

author

Mirosława Lasek

author

Aleksandra Adamus

References

• Abrahamsson P., Salo O., Ronkainen J., Warsta J., 2002, Agile software development methods.
• Review and analysis, VTT Electronics, University of Oulu.
• Adamus A., 2013, Zastosowanie metodyk zwinnych w produkcji oprogramowania przez firmy „software’owe”, praca magisterska, Wydział Nauk Ekonomicznych, Uniwersytet Warszawski, Warszawa.
• Arbogast T., Larman C., Vodde B., Agile contracts primer, Online, http://www.agilecontracts.org (10.07.2013).
• Arell R., Coldewey J., Gat I., Hesselberg J., 2012, Characteristics of Agile Organizations, Agile Alliance.
• Calo K., Estevez E., Fillottrani P., 2010, A Quantitative Framework for the Evaluation of Agile Methodologies, JCS&T, vol. 10.
• Cobb C., 2012, Zrozumieć Agile Project Management. Równowaga kontroli i elastyczności, APN Promise, Warszawa.
• Cockburn A., 2008, Agile Software Development. Gra zespołowa, Wydawnictwo Helion, Gliwice.
• Grabska A., Klimczuk-Kochańska M., 2011, Analiza gospodarczych obszarów wzrostu i innowacji województwa podlaskiego. Sektor produkcji oprogramowania komputerowego, Wojewódzki Urząd Pracy w Białymstoku, Białystok.
• Highsmith J., 2005, APM: Agile Project Management. Jak tworzyć innowacyjne produkty, MIKOM, Warszawa.
• Iterative and incremental development, Mera 2013, http://www.meranetworks.com/services/processes/iterative (21.05.2013).
• Kasunic M., 2008, A Data Specification for Software Project Performance Measures: Results of a Collaboration on Performance Measurement, Report prepared for the SEI Administrative Agent, July.
• Larman C., Basili V., 2003, Iterative and Incremental Development, A Brief History, June.
• Manifest Zwinnego Wytwarzania Oprogramowania 2001, http://agilemanifesto.org/iso/pl (6.04.2013).
• Miłosz M., Borys M., Plechawska-Wójcik M., 2011, Metodyki zwinne wytwarzania oprogramowania, Politechnika Lubelska, Lublin.
• Sacha K., Inżynieria oprogramowania, Wydawnictwo Naukowe PWN, Warszawa 2010.
• Sahota M., 2012, An Agile Adoption and Transformation Survival Guide, Working with Organizational Culture.
• Schwaber K., Sutherland J., 2011, The Scrum Guide. Przewodnik po Scrumie: Reguły gry, Scrum.org.
• Stepanek G., 2005, Software Project Secrets: Why Software Projects Fail, Apress, New York.
• Tomasini A., Kearns M., 2012, Agile Transition. What you Need to Know Before Starting, INFO Q Enterprise Software Development Series.