Agile transformation model for large software development organizations

Author(s):  
Maarit Laanti
2019 ◽  
Vol 15 (29) ◽  
pp. 1-29
Author(s):  
Kapil Jaiswal ◽  
Minakshi Garg

Introduction: This publication is the product of research, carried out in the field of management in year 2018-19, which supports the work of a PhD in Business Management at Chandigarh University.  The purpose of this research is to explore the relation between Total Quality Management (TQM) constructs and productivity in the IT industry. This study has been conducted for organizations operating in the Tricity (Chandigarh, Panchkula and Mohali) and NCR (Noida, Gurgaon and Delhi) regions. Problem: The control of rising operational costs in any organization has become a challenge and is a major aspect in the sustainability of an organization. Implementation of TQM may reduce these costs by improving productivity in the software development process. Objective: The objective of the research is to explore if there any relationship exists between TQM and productivity in software development organization and whether TQM positively impacts productivity. Methodology: The study is based on a descriptive research design. A total of 206 respondents were selected using convenient sampling while 90 responded back on the survey. Exploratory factor Analysis and Multiple Linear Regression techniques were applied to obtain the results. Results: Out of 4 elements of TQM considered in this study, Customer Focus and Continuous improvement were found to be positively related to productivity while Total Management Commitment was found to not be related to productivity.  The hypothesis related to People Management was abandoned because it was highly correlated to other TQM elements. Conclusion: TQM positively impacts productivity in software development organizations. Originality: This study tried to create a causal mathematical model between TQM variables and productivity. Limitations: Sample size and TQM elements were limited based on availability of time and resources.


Author(s):  
Tosin Daniel Oyetoyan ◽  
Martin Gilje Gilje Jaatun ◽  
Daniela Soares Cruzes

Software security does not emerge fully formed by divine intervention in deserving software development organizations; it requires that developers have the required theoretical background and practical skills to enable them to write secure software, and that the software security activities are actually performed, not just documented procedures that sit gathering dust on a shelf. In this chapter, the authors present a survey instrument that can be used to investigate software security usage, competence, and training needs in agile organizations. They present results of using this instrument in two organizations. They find that regardless of cost or benefit, skill drives the kind of activities that are performed, and secure design may be the most important training need.


Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.


Author(s):  
Mirna Muñoz

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.


Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.


2009 ◽  
pp. 2359-2378
Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.


Sign in / Sign up

Export Citation Format

Share Document