| Fortune and White (2006) | Realistic and clear objectives; commercial and sound basis for the project; effective monitoring and control; planning, review and acceptance of possible failure; senior management support; competent project manager; detailed/updated plan; realistic schedule; good leadership; good choice/correct experience of the methodology/project management tools qualified/adequately qualified/sufficient team/team good communication/feedback; political stability; environmental influences; past experiences (learning from); organizational adaptation/culture/structure; project size/level of complexity/number of people involved/duration; adequate budget; sufficient resources/well allocated; provision of training; proven/familiar technology; good performance by suppliers/contractors/consultants; risks addressed/assessed/managed; user/customer involvement; different points of view (appreciation); sponsor/senior project management; effective change management |
| Chow and Cao (2008) | Management commitment; organizational environment; team environment; team capacity; customer involvement; process management; process definition; agile software techniques; delivery strategy; nature of the project; project type; project schedule |
| Nasir and Sahibuddin (2011) | Clear requirements and specifications; clear objectives and goals; realistic timeline; effective project management skills/methodologies; top management support; user/customer engagement; effective communication and feedback; realistic budget; sufficient and qualified staff; frozen requirements; familiarity with technology/development methodology; proper planning; appropriate development processes/methodologies (process); updated progress reports; effective monitoring and control; adequate resources; good leadership; risk management; complexity, project size, duration, number of organizations involved; effective change and configuration management; support tools and good infrastructure; committed and motivated staff; good quality management; clear assignment of roles and responsibilities; good performance by suppliers/contractors/consultants; provision of end-user training |
| Sudhakar (2012) | Communication in the project; leadership; relationship between users and IT team; reduction of ambiguity; maximization of stability; technical tasks; problem-solving; technical uncertainties; technical implementation problems; system integration; top management support; realistic expectations; organizational policy; financial support; strength; user engagement; customer engagement; partnership with suppliers; events in the external environment; customer acceptance; output accuracy; output reliability; output opportunity; quality control; system documentation and procedures; team capacity/skills; teamwork; correct selection of the project team; team coordination; task orientation; project plan; control mechanisms; project schedule; management skills; clear goals for the project |
| Imtiaz et al. (2013) | Top management support; leadership; work team; clear goals; team capacity; financial support/budget; effective communication; process quality; training; monitoring project progress; customer/user involvement; risk management; effective monitoring and control; proper requirements; correct team selection |
| Ahimbisibwe et al. (2015) | Higher level management support; organizational culture; project planning level; leadership; vision and mission; monitoring and controlling; change management skills; team commitment; internal project communication; team training; team composition; the project team’s experience with the tasks; general knowledge of the project team; lack of development team’s skill; the project team’s experience with software development methodologies; user participation; user support; training and customer education; customer experience; lack of end-user experience; technological uncertainty; development methodologies; project complexity; urgency; relative project size; changes in specifications; criticality of the project |
| Martins Muller and Dal Forno (2017) | Capacity and competence of the team; experience of the team; commitment and motivation of the team; experience and competence of the project manager; relationship team/user; specification of requirements; definition of objectives and goals; schedule planning; project planning; risk management (prior analysis and treatment); training and learning of users/clients; development methodology; team size; team composition; team experience with the methodology used; appropriate process and methodology; infrastructure and support tools; support from higher management; commitment of higher management; project leadership; adequate resources (human, financial and material); organizational culture (of the client); user/customer participation; user/customer commitment; variable factors; realistic expectations of the user/client; internal communication of the project; estimates of previous realized costs; realistic budget; project complexity; project size; monitoring and effective control of the project; quality control; process tests |
| Stevenson and Starkweather (2017) | Ability to communicate at multiple levels; define the project appropriately; customer acceptance; ability to coordinate; stakeholders have a common understanding of success criteria before the project starts; clearly articulation of what should be done; competence of the PM; communication and collaboration between PM and project owners; listening; commitment; meeting user requirements; top/senior management support; meeting stated objectives; ability to deal with ambiguity and changes; keeping the team moving toward a common goal |