Governance of Software Development

Author(s):  
Yael Dubinsky ◽  
Avi Yaeli ◽  
Yishai Feldman ◽  
Emmanuel Zarpas ◽  
Gil Nechushtai

Governance is the exercise of control and direction over a subject such as a society, an organization, processes, or artifacts, by using laws and policies that are defined, deployed, and executed. In this chapter we develop this definition into a formal conceptual model that can be applied to a variety of governance domains. At the heart of this model lies the concept of the governance solution and its lifecycle. The governance solution embodies the set of mechanisms—decision rights, policies, controls, and measurements—applied to a governance scope in order to achieve some governance goals. As part of the lifecycle, the effectiveness of the governance solution is measured, and corrections and alignments are made as necessary. We demonstrate how this model can be applied to multiple governance domains by providing examples from IT governance as well as software-development governance. We conclude by providing a detailed scenario in the software-development governance space, which looks at large software organizations undergoing transition to agile development methodology. We further demonstrate how the governance model is instantiated and evolved in the context of this scenario.

2009 ◽  
pp. 309-327
Author(s):  
Yael Dubinsky ◽  
Avi Yaeli ◽  
Yishai Feldman ◽  
Emmanuel Zarpas ◽  
Gil Nechushtai

Governance is the exercise of control and direction over a subject such as a society, an organization, processes, or artifacts, by using laws and policies that are defined, deployed, and executed. In this chapter we develop this definition into a formal conceptual model that can be applied to a variety of governance domains. At the heart of this model lies the concept of the governance solution and its lifecycle. The governance solution embodies the set of mechanisms—decision rights, policies, controls, and measurements—applied to a governance scope in order to achieve some governance goals. As part of the lifecycle, the effectiveness of the governance solution is measured, and corrections and alignments are made as necessary. We demonstrate how this model can be applied to multiple governance domains by providing examples from IT governance as well as software-development governance. We conclude by providing a detailed scenario in the software-development governance space, which looks at large software organizations undergoing transition to agile development methodology. We further demonstrate how the governance model is instantiated and evolved in the context of this scenario.


Author(s):  
Chitrak Vimalbhai Dave

Abstract: Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms ofestimation. Keywords: Cost Estimation, Effort Estimation, Scrum, Machine Learning, Agile Software Development


The paper proposes a modern scientific and practical approach to improving the performance of enterprises through the use of Agile management. The purpose of the article is to improve the process of managing web projects through the use of agile management mechanisms in the planning and development phase of an IT project. One of the possible promising methods for solving modern management problems is the application of the principles of flexible development methodology. (Agile development). The prerequisites for the emergence of the Agile management concept were identified and a comparative analysis of project management approaches was conducted. The peculiarities of application of different project management methodologies in IT companies are investigated. The characteristics of the positive and negative aspects of the application of alternative approaches to software development are given. The main difference between traditional software development methodology and flexible development methodology is outlined. The basic characteristics of the most used model of agile management - the Scrum model are given. It is determined that within the framework of the Scrum model, the factors of minimizing the risk of failure of individual projects and the entire project portfolio of an organization are: ensuring the balance of the portfolio in its formation; regular monitoring of the portfolio implementation and preventive measures; agreed decision-making on changes to projects, taking into account the interrelation of content, timing and resources with other projects. Changes were recorded in the functional responsibilities of investors, executives, and customers of the software when implementing the flexible methodology. The factors of increase of efficiency of realization of IT-projects are revealed and advantages of correct use of flexible methodology for projects in the field of IT are stated. A further area of research in the field of lean / agile management methodology will be to apply the benefits of these methodological approaches to other areas of the economy.


Author(s):  
Roy Morien

Massive failures of software development projects have been recorded in the literature, and particularly in the popular press, over the years. Yet, rarely if ever have we seen any objective, detailed analysis of the causes of these failures. Indeed, we usually can only surmise how the projects were managed or what the development methodology or approach was. This chapter analyses some aspects of software development projects and development methodologies in terms of the success or failure potential of these methodologies. The conclusion arrived at is that the system development methodologies handed down since the late 1970s as the preferred development approach, generally known as Structured Methodologies, based on the Structured Design Life Cycle methodology (SDLC), bear the seeds of their own failure. It is asserted that they cannot succeed because of the inherent nature and assumptions embedded in those methodologies. After some analysis of these assumptions, considered to be highly flawed and unworkable, the now not so recently published Agile Development methodologies are discussed and proffered as a workable and inherently successful approach to software system development.


Author(s):  
Chhabi Rani Panigrahi ◽  
Rajib Mall ◽  
Bibudhendu Pati

This chapter emphasizes mainly on the software development methodology basically agile methods of software development in cloud computing platforms and its impact on software development processes. This chapter also covers the benefits of agile development methodology in cloud computing platform. Along with this all traditional software development phases are analyzed to discuss the differences between the traditional software development processes and software development in cloud computing environment. This chapter also includes a brief description of programming models such as MapReduce, BSPCloud, and Dryad etc. available in the literature to handle big data in SaaS cloud. Finally, we highlight the challenges and future scope of software development process in cloud computing environment.


2015 ◽  
Vol 3 (2) ◽  
pp. 30-33
Author(s):  
Иванов ◽  
A. Ivanov ◽  
Иванова ◽  
O. Ivanova

The paper considers issues related to the choice of more cost-effective methodologies of developing software needed for implementation of ITprojects. Also described are the most conventional methodologies of IT-projects development, along with their main features, specifics and terms of use. Factors, allowing to opt for the “waterfall” software development methodology or for the agile development methodology are identified.


Author(s):  
Ruth Guthrie

Scrum is a software development methodology that is growing in popularity. It is an agile development technique that allows user requirements to change throughout the development of the project. Scrum is often described as appropriate for small development programs with high uncertainty of requirements. This article describes scrum methodology at a high level. The advantages and disadvantages of adopting scrum methodology are reviewed. Impediments to adopting scrum and remedies are also discussed.


Author(s):  
Rosnani Shuib Et.al

In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product.  However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology.  Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.


Author(s):  
Chhabi Rani Panigrahi ◽  
Rajib Mall ◽  
Bibudhendu Pati

This chapter emphasizes mainly on the software development methodology basically agile methods of software development in cloud computing platforms and its impact on software development processes. This chapter also covers the benefits of agile development methodology in cloud computing platform. Along with this all traditional software development phases are analyzed to discuss the differences between the traditional software development processes and software development in cloud computing environment. This chapter also includes a brief description of programming models such as MapReduce, BSPCloud, and Dryad etc. available in the literature to handle big data in SaaS cloud. Finally, we highlight the challenges and future scope of software development process in cloud computing environment.


2013 ◽  
Vol 321-324 ◽  
pp. 2938-2941 ◽  
Author(s):  
Ida Aryanie Bahrudin ◽  
Rafizah Mohd Hanifa ◽  
Mohd Ezree Abdullah ◽  
Muhammad Firdaus Kamarudin

eXtreme Programming (XP) is one of new discipline of software development methodology on values of simplicity, communication, feedback and also courage. XP is an explorative and agile development method that seeks to satisfy the customer through early and continuous delivery of valuable software. XP software development process starts with planning, and all iterations consist of four basic phases in its life cycle: designing, coding, testing, and listening. This paper tends to report the experience in adapting XP in developing electronic document online system for the use of Centre for Diploma Studies, Universiti Tun Hussein Onn Malaysia (eDoc). The project under study is a system that is use to store office documents such as letter in an online database. The objective of this paper is to discuss the XP practices that had been choosed and also the lesson learnt by practising XP in developing eDoc.


Sign in / Sign up

Export Citation Format

Share Document