Over the years, organizations have seen fit to adopt the use of agile systems development methodologies (ASDMs) because of the benefits that they offer, such as flexibility and the ability to deliver products faster, in constantly changing environments. When ASDMs are used in projects, they are made to fit or be suitable for a project‟s unique aspects, such as its size, requirements, scope and outcomes. This is known as the contingent use of ASDMs. Little is known about the contingent use of ASDMs in South African organizations. It is not known whether it is happening, its procedure and its success. It is important to know this because quality and control need to be maintained in systems produced. There is always a danger that the benefits of using a system development methodology (SDM) would be lost if ASDMs are highly adapted. This led to an investigation of three organizations in South Africa that use contingent ASDMs. With the help of semi-structured interviews, focus groups and documents, data was collected that was analysed, using the tool ATLAS.ti, and the analysis methods content and cross-case analysis. It was found that some South African organizations in the telecommunications, consulting, technological, outsourcing and agricultural sectors use ASDMs in combination with the still popular waterfall SDM. Compatibility between the SDM and the project is a factor in some organizations. Scrum was cited to be the ASDM that was used in some of the organizations interviewed due to its maturity. They make ASDMs contingent by using aspects in the methods, such as Scrum, that are useful for their unique projects. These aspects are in some cases combined with other SDMs to form hybrid methodologies. Some organizations use criteria, such as project needs, outcomes, size and complexity to make ASDMs contingent. Some organizations have measures and facilities in place to manage, monitor, control and document the process used to make ASDMs contingent. They make use of contingent ASDMs as they have experienced more success with them and they will continue to do so. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

Over the years, organizations have seen fit to adopt the use of agile systems development methodologies (ASDMs) because of the benefits that they offer, such as flexibility and the ability to deliver products faster, in constantly changing environments. When ASDMs are used in projects, they are made to fit or be suitable for a project‟s unique aspects, such as its size, requirements, scope and outcomes. This is known as the contingent use of ASDMs. Little is known about the contingent use of ASDMs in South African organizations. It is not known whether it is happening, its procedure and its success. It is important to know this because quality and control need to be maintained in systems produced. There is always a danger that the benefits of using a system development methodology (SDM) would be lost if ASDMs are highly adapted. This led to an investigation of three organizations in South Africa that use contingent ASDMs. With the help of semi-structured interviews, focus groups and documents, data was collected that was analysed, using the tool ATLAS.ti, and the analysis methods content and cross-case analysis. It was found that some South African organizations in the telecommunications, consulting, technological, outsourcing and agricultural sectors use ASDMs in combination with the still popular waterfall SDM. Compatibility between the SDM and the project is a factor in some organizations. Scrum was cited to be the ASDM that was used in some of the organizations interviewed due to its maturity. They make ASDMs contingent by using aspects in the methods, such as Scrum, that are useful for their unique projects. These aspects are in some cases combined with other SDMs to form hybrid methodologies. Some organizations use criteria, such as project needs, outcomes, size and complexity to make ASDMs contingent. Some organizations have measures and facilities in place to manage, monitor, control and document the process used to make ASDMs contingent. They make use of contingent ASDMs as they have experienced more success with them and they will continue to do so. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

Problem statement: There seem to be perceptual incongruence between systems development managers and developers. Research shows that while managers are more positive towards systems development methodologies, developers on the other hand seem to resist and not to use systems development methodologies in their entirety but instead adapt, tailor, modify and change them depending on the project at hand (contingent use). Systems development managers can exert power through a variety of influence bases. However, these power influences may be perceived differently by developers. While some might feel constrained, others might actually feel liberated by the existence of the same influence base. Main findings: IS managers are using systems development methodologies to gain control over team members. However, there was no clear perception on whether systems development methodologies were enslaving systems developers. This was indicated by the majority of the respondents neither agreeing nor disagreeing to that effect. The research showed that most organisations are adapting the use of systems development methodologies on a project to project basis, which is referred to as the contingent use of systems development methodologies. Research method followed: The positivistic research paradigm was used as it allowed the researcher to find out patterns and regularities between power, systems development methodologies’ use and success. A survey was conducted and a questionnaire was used for data collection purposes. Questionnaire data was analysed using IBM SPSS Statistics Version 21, Release 20.0.0 software package tools. Principal conclusion: Power is interpreted in terms of the type of power that can be exercised by IT professionals specifically IS developers and their respective managers at the workplace. The roles assumed and the different power types that may be exercised in organisations provide a link as to who has the final say when it comes to the use and success rate of systems development methodologies. The contingent use of systems development methodologies provides a form of “freedom” to systems developers. Based on the research findings, the research proposes an answer to the question – are systems development methodologies enslaving systems developers and empowering IS managers? / MSc (Computer Science), North-West University, Potchefstroom Campus, 2014

Problem statement: There seem to be perceptual incongruence between systems development managers and developers. Research shows that while managers are more positive towards systems development methodologies, developers on the other hand seem to resist and not to use systems development methodologies in their entirety but instead adapt, tailor, modify and change them depending on the project at hand (contingent use). Systems development managers can exert power through a variety of influence bases. However, these power influences may be perceived differently by developers. While some might feel constrained, others might actually feel liberated by the existence of the same influence base. Main findings: IS managers are using systems development methodologies to gain control over team members. However, there was no clear perception on whether systems development methodologies were enslaving systems developers. This was indicated by the majority of the respondents neither agreeing nor disagreeing to that effect. The research showed that most organisations are adapting the use of systems development methodologies on a project to project basis, which is referred to as the contingent use of systems development methodologies. Research method followed: The positivistic research paradigm was used as it allowed the researcher to find out patterns and regularities between power, systems development methodologies’ use and success. A survey was conducted and a questionnaire was used for data collection purposes. Questionnaire data was analysed using IBM SPSS Statistics Version 21, Release 20.0.0 software package tools. Principal conclusion: Power is interpreted in terms of the type of power that can be exercised by IT professionals specifically IS developers and their respective managers at the workplace. The roles assumed and the different power types that may be exercised in organisations provide a link as to who has the final say when it comes to the use and success rate of systems development methodologies. The contingent use of systems development methodologies provides a form of “freedom” to systems developers. Based on the research findings, the research proposes an answer to the question – are systems development methodologies enslaving systems developers and empowering IS managers? / MSc (Computer Science), North-West University, Potchefstroom Campus, 2014