Abstract
The topic of critical success factors draws high attention of both academia and practitioners working in the software industry. Literature review shows that existing models of critical success factors for software projects are more concentrated on specific categories of success factors, neglecting the interaction that exists within these models between different groups of factors. The purpose of this paper is to present a new concept of interaction-based model for identification and evaluation of critical success factors for software projects. The approach is based on conjoint use of graph theory and Design Structure Matrices to highlight important interactions of a project system. The key result of the paper is the tool for evaluation of the interaction between critical success factors through quantification and the analysis of the possible propagation of specific factor within project success factor network, which will make possible the identification of the critical factors with the highest influence on the entire project system.
Highlights
The key result of the paper is the tool for evaluation of the interaction between critical success factors through quantification and the analysis of the possible propagation of specific factor within project success factor network, which will make possible the identification of the critical factors with the highest influence on the entire project system
The purpose of this paper is to present a new concept of interaction-based model for identification and evaluation of critical success factors for software projects
The approach is based on conjoint use of graph theory and Design Structure Matrices to highlight important interactions of a project system
Summary
U teoriji konvencionalnog upravljanja projektima, uspeh projekta je posmatran kao binarna funkcija, odnosno projekat se može smatrati uspešnim ili neuspešnim [14]. Većina studija definiše uspeh kroz kriterijume/ograničenja vezana za budžet, rokove i funkcionalnosti, odnosno neuspeh kao prekoračenja ograničenja u vezi sa budžetom i rokovima ili dogovorenim funkcionalnostima [20]. Takva definicija uspeha sugeriše da se projekat ne može smatrati uspešnim ukoliko bilo koji od navedenih kriterijuma nije ispunjen [21]. Posledično, uspeh projekta se meri na različite načine [23] [24], usled velike divergencije u definicijama uspeha softverskih projekata [7] [16] [25] kao i potrebe da se koriste različiti kriterijumi uspeha za ocenu projekata sa različitim karakteristikama [13]. Na ovaj način je barem jednim delom dat odgovor na problem binarnog posmatranja uspeha projekta i omogućava posmatranja uspeha kao složenog koncepta koji uzima u obzir različite dimenzije uspeha i omogućava balans između ovih dimenzija [14]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
