Wpływ świadomości dotyczącej długu technicznego i wiedzy o nim na powodzenie projektów informatycznych

• Authors: Bagiński Przemysław , Labus Krzysztof , Werewka Jan

Title variants

EN

Impact of knowledge and awareness of technical debt in software developing teams on IT projects success

• Languages of publication: PL EN

Abstracts

EN

The aim of the study was to analyze the impact of technical debt on projects goals achievement, considered from the perspective of software developing teams. The investigations are addressed to technical debt accumulation, difficulties related to its service and repaying. The most important stakeholders are identified on which the dechnical debt has an impact or which influence the technical debt accumulation. An interesting issue was to look at the debt from the inside in order to obtain views of members of the software developing teams. In order to obtain all the necessary information, a survey is conducted referred to the members of the software developing teams. The responses obtained from the survey concerns types of technical debt encountered, attitude, knowledge and approach to the debt. The article also shows that the lack of knowledge and awareness related to technical debt in teams affects the technical debt growth. The paper provides, based on SWOT analysis, solutions proposals that are designed to prevent dangerous situations resulting from technical debt.

Keywords

EN

technical debt; IT project management; software developing teams; agile methodologies; risk management

• Publisher: Wydawnictwo Uniwersytetu Ekonomicznego we Wrocławiu
• Journal: Informatyka Ekonomiczna
• Year: 2015
• Issue: 3(37)
• Pages: 9-29

Contributors

author

Bagiński Przemysław

author

Labus Krzysztof

author

Werewka Jan

References

• Alves N.S.R., Ribeiro L.F., Caires V., MendesT.S., Spinola R.O., 2014, Towards an ontology of terms on technical debt, 2014 Sixth International Workshop on Managing Technical Debt (MTD), s. 1-7, http://doi.org/10.1109/MTD.2014.9.
• Code refactoring, hasło [w:] Wikipedia, the free encyclopedia, https://en.wikipedia.org/w/index.php?title=Code_refactoring&oldid=682022427 (21.09.2015).
• Cunningham W., 1992, The WyCash Portfolio Management System, http://c2.com/doc/oopsla92.html(6.01.2016).
• Czym jest dług technologiczny? Jarosław Żeliński IT-Consulting, 2014, http://it-consulting.pl/autoinstalator/wordpress/2014/05/12/czym-jest-dlug-technologiczny/.
• Da S Maldonado E., Shihab E., 2015, Detecting and quantifying different types of self-admitted technical debt, 2015 IEEE 7th International Workshop on Managing Technical Debt (MTD), s. 9-15,http://doi.org/10.1109/MTD.2015.7332619.
• Fontana F.A., Ferme V., Zanoni M., Roveda R., 2015, Towards a prioritization of code debt: A code smell intensity index, 2015 IEEE 7th International Workshop on Managing Technical Debt (MTD), s. 16-24, http://doi.org/10.1109/MTD.2015.7332620.
• Holvitie J., Leppanen V., Hyrynsalmi S., 2014, Technical debt and the effect of agile software development practices on it − an industry practitioner survey, 2014 Sixth International Workshop on Managing Technical Debt (MTD), s. 35-42, http://doi.org/10.1109/MTD.2014.8.
• Kieruzel M., 2014, Metoda oceny ryzyka realizacji oprogramowania do wspomagania działalności przedsiębiorstwa na przykładzie oprogramowania typu open source, Informatyka Ekonomiczna, 1, http://doi.org/10.15611/ie.2014.1.20.
• Li Z., Avgeriou P., Liang P., 2015, A systematic mapping study on technical debt and its management, Journal of Systems and Software, 101, s. 193-220, http://doi.org/10.1016/j.jss.2014.12.027.
• Li Z., Liang P., Avgeriou P., 2015, Architectural technical debt identification based on architecture decisions and change scenarios, 2015 12th Working IEEE/IFIP Conference on Software Architecture (WICSA), s. 65-74, http://doi.org/10.1109/WICSA.2015.19.
• Łucki Z., 2015, Proszę... nie mówmy „technologia” na technikę!, http://www.uci.agh.edu.pl/bip/63/11_63.htm (25.08.2015).
• Managing Technical Debt, 2015, http://www.infoq.com/articles/managing-technical-debt (15.08.2015).
• Martini A., Bosch J., 2015, The danger of architectural technical debt: contagious debt and vicious circles, 2015 12th Working IEEE/IFIP Conference on Software Architecture (WICSA), s. 1-10, http://doi.org/10.1109/WICSA.2015.31.
• PMI, 2013, A Guide to the Project Management Body of Knowledge: PMBOK(R) Guide (5 edition), Newtown Square, Project Management Institute, Pennsylvania.
• Rubin K.S., 2012, Essential Scrum: A Practical Guide to the Most Popular Agile Process (1 edition), Upper Saddle River, Addison-Wesley Professional.
• Siarka P., 2015, System informacyjny banku – integracja procesów zarządzania ryzykiem kredytowym, Informatyka Ekonomiczna, 1, http://doi.org/10.15611/ie.2015.1.05.
• Steve Garnett − Technical Debt: Strategies & Tactics for Avoiding & Removing It., 2013, http://blogs.ripple-rock.com/SteveGarnett/2013/03/05/TechnicalDebtStrategiesTacticsForAvoidingRemovingIt.aspx (15.08.2015).
• SWOT TOWS, 2015, http://swottows.com/ (6.01.2016).
• Technical debt, 2015, hasło [w:] Wikipedia, the free encyclopedia, https://en.wikipedia.org/w/index.php?title=Technical_debt&oldid=694276930 (8.12.2015).
• Werewka J., Lewicka D., Zakrzewska-Bielawska A.F., 2012, Zarządzanie projektami w przedsiębiorstwie informatycznym: Metodologia i strategia zarządzania, t. 1, Wydawnictwa AGH, Kraków.
• Zazworka N., Izurieta C., Wong S., Cai Y., Seaman C., Shull F. i in., 2014, Comparing four approaches for technical debt identification, Software Quality Journal, 22(3), s. 403-426.