A Survey of DevOps in the South African Software Context

2021 | HICSS | Citations: 11

Authors: Rowse, Morgan; Cohen, Jason

Abstract: This study investigated DevOps practices and experiences in the South African so ... Expand

Abstract: This study investigated DevOps practices and experiences in the South African software development context, along with associated perceptions of benefits and challenges. Survey data collected from a sample of 80 software development professionals showed that more frequent builds, earlier detection of bugs and reduced project lead times were the top three benefits, while getting DevOps capable members into a team, finding experienced professionals to support DevOps practice and changing deep-seated company culture to support DevOps were the top three challenges. DevOps practices are still emerging. Although 85% of respondents report continuous integration as a frequent practice, only 54% report using continuous deployment frequently. The biggest reported impacts of DevOps on software development culture were in making development team members aware of operational faults, responsible for quality assurance, and responsible for deployments. Realisation of benefits from DevOps depends largely on a culture change. Results are useful for guiding organisations considering DevOps adoption. Collapse

Topics: devops systems development missing data information system use software developer

Methods: survey qualitative interview self reported survey scale reliability case study

Methodology Mashups: An Exploration of Processes Used to Maintain Software

2012 | Journal of Management Information Systems | Citations: 23

Authors: Edberg, Dana; Ivanova, Polina; Kuechler, William

Abstract: The majority of studies of software development processes explore initial develo ... Expand

Abstract: The majority of studies of software development processes explore initial development rather than ongoing software maintenance, yet the majority of the systems development budget in many organizations is devoted to maintenance. Software maintenance projects differ significantly from original development projects, indicating a need for more research specifically concerning maintenance processes. This study uses a grounded theory research method to explore how information technology professionals define and select a methodology to maintain existing software. We found that in-use maintenance methodologies are composed of components from multiple formal methodologies. We developed a factor model describing how these components are chosen. The findings contribute to a better understanding of how standard methodologies are applied in software practice and the critical factors used by professionals when choosing an appropriate methodology for software maintenance activities. This research underscores the need for incorporating the full software life cycle in information systems development research and education. Collapse

Topics: system maintenance systems development IT workforce agile software development embedded system

Methods: qualitative interview personal interview grounded theory survey experiment

Toward an ‘IT Conflict-Resistance Theory’: action research during IT pre-implementation

2010 | European Journal of Information Systems | Citations: 0

Authors: Meissonier, Régis; Houzé, Emmanuel

Abstract: Most empirical research on users’ resistance toward Information Technology (IT) ... Expand

Abstract: Most empirical research on users’ resistance toward Information Technology (IT) has been conducted after implementation of IT in organisations. Little research has been done on the way individual and group resistance emerges and evolves during prior stages of projects. This focus on pre-implementation phases is important since Information Systems (IS) managers need to anticipate potential conflicts and users’ resistance that can involve project failure. While IS literature has separately developed theories on resistance and conflicts, we conceptualise a whole theoretic-system we call ‘IT Conflict-Resistance Theory’ (IT-CRT). This theory is used as driver for a 2-year action research project conducted at Netia Corporation (a worldwide leader in video and audio broadcasting) during preliminary phases of its Enterprise Resource Planning (ERP) implementation project. According to our findings, while conflicts toward IT implementation are often considered to have negative effects and require being actively managed by top managers, the case study delivers an alternative observation: a passive-like attitude of managers during the IT pre-implantation phase does not prevent the resolution of a socio-political oriented conflict between two groups of employees. Our observations illustrate how the avoidance management style invites team members to cope with conflict situations and to express tacit causes of resistance. While most Management Information System methods tend naturally to maximise users’ satisfaction and to reduce potential resistance, the IT-CRT theory developed in this article supports an alternative approach: enhancing resistance in order to anticipate and resolve latent conflicts that are directly or indirectly related to the project. The underlying message of this article for researchers and practitioners is to consider users’ resistance toward IT as a key process embedded into IT choices and IS design. Collapse

Topics: enterprise resource planning systems implementation enterprise resource planning implementation brainstorming user resistance

Methods: action research qualitative interview case study literature study design methodology

Theories: IT conflict-resistance theory attribution theory theory of reasoned action

Quality management in systems development: an organizational system perspective

2000 | Management Information Systems Quarterly | Citations: 89

Authors: Ravichandran, Thiagarajan; Rai, Arun

Abstract: test the model using a Partial Least Squares analysis methodology. Our results ... Expand

Abstract: test the model using a Partial Least Squares analysis methodology. Our results suggest that software quality goals are best attained when top management creates a management infrastructure that promotes improvements in process design and encourages stakeholders to evolve the design of the development processes. Our results also suggest that all elements of the organizational system need to be developed in order to attain quality goals and that piecemeal adoption of select quality management practices are unlikely to be effective. Implications of this research for IS theory and practice are discussed. Collapse

Topics: quality management systems development business process management system quality IT manager

Methods: survey design methodology partial least squares regression theory development data transformation

Theories: information systems theory

Software Process Improvement: Toward a Comprehensive Framework for Research

1996 | Americas Conference on Information Systems | Citations: 0

Authors: Nerur, Sirdhar; Raghupathi, Wullianallur

Abstract: ... Expand

Abstract: Collapse

Topics: software process improvement systems development end user computing

Methods: co-citation analysis data transformation factor analysis design methodology survey

Software Processes and Project Performance

1995 | Journal of Management Information Systems | Citations: 12

Authors: Deephouse, Christopher; Mukhopadhyay, Tridas; Goldenson, Dennis R.; Kellner, Marc I.

Abstract: Firms developing software face increasing pressures to improve project outcomes ... Expand

Abstract: Firms developing software face increasing pressures to improve project outcomes in terms of product quality, productivity, time to market, and customer satisfaction. As projects expand in size and complexity, and competition grows, firms are reengineering their software processes. They are adopting more intensive procedures for requirements management, project planning, defect tracking, configuration management, design and code inspections, and so forth. To assess the effectiveness of these efforts, we conducted a survey of senior practitioners at the 1993 Software Engineering Process Group National Meeting. The survey asked participants about the processes followed on, and the outcome of, a specific software project. Certain practices--notably project planning and cross-functional teams--were consistently associated with favorable outcomes. Based on the survey results, other practices may have little impact on project outcomes. Collapse

Topics: IT project systems development software process improvement IS effectiveness customer satisfaction

Methods: survey generalized least square design methodology design artifact F-test