DOCSLIB.ORG

Issues and Challenges of Agile Software Development with Scrum

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Issues and Challenges of Agile Software Development with Scrum https://doi.org/10.48009/2_iis_2008_188-195 ISSUES AND CHALLENGES OF AGILE SOFTWARE DEVELOPMENT WITH SCRUM Juyun Cho, Colorado State University-Pueblo, [email protected] ABSTRACT (ASDMs) including Scrum, eXtreme Programming (XP), Crystal, and Adaptive Software Development Agile software development methods have been (ASD), have been developed and evolved since developed and evolved since early 1990s. Due to the 1990s to embrace, rather than reject, high rates of short development life cycle through an iterative and change [24]. Such new approaches focus on iterative incremental process, the agile methods have been and incremental development, customer used widely in business sectors where requirements collaboration, and frequent delivery [18] through a are relatively unstable. This paper explains the light and fast development life cycle. Although many differences between traditional software development positive benefits of agile approaches including methods and agile software development methods, shorter development cycle, higher customer and introduces the characteristics of one of the satisfaction, lower bug rate, and quicker adaptation to popular agile methods, Scrum. Finally, the paper changing business requirements have been reported illustrates issues and challenges discovered through [3], there have been few empirical field studies on an in-depth case study in a company which has issues and challenges of ASDMs. Therefore, the aim employed Scrum for many projects. The insights of this research paper was to discover the issues and presented in the paper can be used in organizations challenges of one particular agile method in practice, that are in the process of agile software development Scrum, through an in-depth case study in a mid-sized, using Scrum. web-based development projects for government. Keywords: Scrum methodology, traditional software The remainder of this paper discusses the differences development, agile software development, empirical between traditional methods and agile methods, and process. then presents a brief history, framework, and empirical process of the Scrum methodology. Finally, INTRODUCTION the paper discusses issues and challenges of the Scrum methodology discovered through an in-depth Traditional Software Development Methods case study. (TSDMs) including waterfall and spiral models, utilize extensive planning, codified process, rigorous TRADITIONAL SOFTWARE DEVELOPMENT reuse, heavy documentation and big design up front METHODS (TSDMs) [2]. Due to these characteristics, TSDMs are often called heavyweight development methods. The One of well-known traditional software development TSDMs are still widely used in industry because of methods is the waterfall model. The waterfall model their straightforward, methodical, and structured utilizes a structured progression between defined nature [6], as well as their predictability, stability, phases: planning, analysis, design, implementation, and high assurance [3]. and maintenance. The planning phase which occupies typically about 15% of total Systems Development Though many TSDMs have been developed since the Life Cycle (SDLC) is the fundamental process to waterfall model to provide significant productivity identify the scope of the new system, understand why improvements, none of them are free from major a system should be built, and how the project team problems including blown budgets, missed schedules, will go about building it through technical, and flawed products [3, 4], and they have failed to economical, and organizational feasibility analysis. provide dramatic improvements in productivity, in The analysis phase, which occupies about 15% of reliability, and in simplicity [4]. Due to constant SDLC, analyzes the current system, its problems, and changes in the technology and business then identifies ways to design the new system environments, it is a challenge for TSDMs to create a through requirements gathering. The design phase complete set of requirements up front. (35%) decides how the system will operate in terms of hardware, software, and network infrastructure. As a remedy for the shortcomings of TSDMs, a The implementation phase (30%) is the actual number of Agile Software Development Methods programming. The maintenance phase (5%) focuses VOL IX, No. 2, 2008 188 Issues in Information Systems Issues and Challenges of Agile Software Development with Scrum on go-live, training, installation, support plan, percentage of projects (16.2%) that used traditional documentation, and debugging [5]. Figure 1 and methods were completed on-time and on-budget with table 1 below show a typical waterfall lifecycle and all features and functions specified. However, 52.7% deliverables respectively. As we can see in the figure of the projects were completed either over-budget, and the table, each phase must be accomplished over the time estimate and/or offering less features before the following phase can begin and each phase and functions; 31.1% of projects were canceled at cannot go back to the previous phase like water in the some point during the development cycle [17] (see waterfall cannot climb up once it reaches to lower Figure 2). position. Planning (15%) Analysis (15%) Design (35%) Implementation (30%) Maintenance (5%) Figure 2 Project resolution (Source: The Standish Group [17]) To overcome these shortcomings, several Figure 1 Waterfall model lifecycle practitioners developed agile software development methods including Scrum, eXtreme Programming (XP), Crystal, and Adaptive Software Development Phases Deliverables (ASD). The next section explains the characteristics Planning Phase Planning Specifications and principles of agile software development Analysis Phase Analysis Specifications methods. Design Phase Design Specifications AGILE SOFTWARE DEVELOPMENT METHODS (ASDMs) Implementation Phase Completed Product Table 1 Waterfall model deliverables The manifesto for agile software development which was created by seventeen practitioners in 2001 Over the past four decades, traditional waterfall-style (http://www.agilemanifesto.org), reveals which items software development methods have been widely are considered valuable by ASDMs. As shown in used for large-scale projects in the software industry Table 2, ASDMs concentrate more on 1) individuals and in the government sector due to their and interactions than processes and tools, 2) working predictability, stability, and high assurance. As software than comprehensive documentation, 3) mentioned earlier, however, TSDMs have a number customer collaboration than contract negotiation, and of key shortcomings, including slow adaptation to 4) responding to change than following a plan. constantly changing business requirements, and a tendency to be over budget and behind schedule with More Valuable Items Less Valuable Items fewer features and functions than specified [2, 6, 16, Individuals and Processes and tools 19, 21]. Boehm and Phillip [22], and Jones [23] both interactions reported that during their project development Working software Comprehesive experience, requirements often changed by 25% or documentation more. Williams and Cockburn [24] also mentioned Customer Contract negotiation that one of problems of TSDMs is the inability to collaboration respond to change that often determines the success Responding to change Following a plan or failure of a software product. Table 2 Manifesto for agile software development One interesting research study conducted by the Standish Group of 365 respondents and regarding The twelve principles behind the agile manifesto also 8,380 projects representing companies across major present the characteristics of ASDMs industry segments, shows that only a small (http://www.agilemanifesto.org/principles.html). As VOL IX, No. 2, 2008 189 Issues in Information Systems Issues and Challenges of Agile Software Development with Scrum shown in Table 3, ASDMs 1) satisfy the customer There are many different characteristics between through early and continuous delivery of software, 2) ASDMs and TSDMs. Boehm [2], for example, embrace changing requirements, even in late reports nine agile and heavyweight discriminators development cycle, 3) deliver working software (See Table 4). He believes the primary objective of frequently, 4) work daily with business people, 5) ASDMs is on rapid value whereas the primary facilitate motivated people, provide them with good objective of TSDMs is on high assurance. He also environment and support, and trust them, 6) assist believes that ASDMs should be used for small teams face-to-face conversation within a development team, and projects. If the size of the team and projects are 7) use working software as a primary measure of large he suggests TSDMs. progress, 8) promote sustainable development and keep sponsors, developers, and users moving at a Project Agile Heavyweight constant pace, 9) pay attention to technical excellence Characteristics discriminator Discriminator and good design, 10) maintain simplicity, 11) promote self-organizing teams, and 12) foster Primary Rapid Value High inspections and adaptations. objective Assurance # Principles Requirements Largely Knowable 1 Our highest priority is to satisfy the customer emergent, rapid early, largely through early and continuous delivery of change, stable valuable software. unknown 2 Welcome changing requiremts, even late in development. Agile processes harness change Size Smaller teams Larger teams for the customer’s competitive advantage. and projects and projects
Load more

Recommended publications
  • Software Company Edition
    Data Sheet Software Company Edition NetSuite Software Company Edition offers the industry’s first and only: NetSuite—The One Integrated Application To Manage Your Software Business • Integrated revenue recognition and advanced billing With NetSuite, your software company can manage its entire front-office and back-office • Role-based, customizable dashboards operations with a single, flexible, powerful business application — integrating customer relation- • Integrated CRM, Accounting/ERP, ecommerce ship management, customer service, financials, inventory management, ecommerce, and more. NetSuite Software Company Edition Hundreds of software companies run their business on NetSuite — and we do too. Here’s why features include: NetSuite is the best application for software companies. • Customer Relationship Management - Sales Force Automation Advanced Financials with Revenue Management and Revenue Recognition - Marketing Automation Financials are complex in any industry, and they are arguably the most complex in the software - Customer Support and Service industry. The stumbling block for most software companies is managing revenue recognition - Incentive Management* - Offline Sales Client* and billing schedules—and ensuring compliance. Few financial packages provide these tools, - Issue Management* forcing companies to manage these complexities offline in spreadsheets or in third party stand- - Partner Relationship Management alone packages. With NetSuite you have one financial system that manages accounting, complex billing and revenue recognition—so there’s no more double entry. • Accounting/ERP - Revenue Recognition NetSuite supports AICPA, FASB and SEC regulations (including SOP 81-1, SAB 101, and EITF - Advanced Billing 00-21). NetSuite also accommodates the requirements specified in SOP 97-2 & 98-9 relating - General Ledger to Vendor Specific Objective Evidence or VSOE, including the accommodation of the Residual - Accounts Receivable, Accounts Payable Method and a separate VSOE price for every item.
    [Show full text]
  • Software Developers Working from Home During the COVID-19 Pandemic
    A Tale of Two Cities: Software Developers Working from Home During the COVID-19 Pandemic DENAE FORD, Microsoft Research MARGARET-ANNE STOREY, University of Victoria, Canada THOMAS ZIMMERMANN, Microsoft Research CHRISTIAN BIRD, Microsoft Research SONIA JAFFE, Microsoft Corp. CHANDRA MADDILA, Microsoft Research JENNA L. BUTLER, Microsoft Research BRIAN HOUCK, Microsoft Corp. NACHIAPPAN NAGAPPAN, Facebook The COVID-19 pandemic has shaken the world to its core and has provoked an overnight exodus of developers that normally worked in an office setting to working from home. The magnitude of this shift and the factors that have accompanied this new unplanned work setting go beyond what the software engineering community has previously understood to be remote work. To find out how developers and their productivity were affected, we distributed two surveys (with a combined total of 3,634 responses that answered all required questions) —weeks apart to understand the presence and prevalence of the benefits, challenges, and opportunities to improve this special circumstance of remote work. From our thematic qualitative analysis and statistical quantitative analysis, we find that there isa dichotomy of developer experiences influenced by many different factors (that for some are a benefit, while for others a challenge). For example, a benefit for some wasbeing close to family members but for others having family members share their working space and interrupting their focus, was a challenge. Our surveys led to powerful narratives from respondents
    [Show full text]
  • Critical Review of Extended Waterfall Model
    International Journal of Scientific & Engineering Research, Volume 6, Issue 11, November-2015 425 ISSN 2229-5518 Critical Review of Extended Waterfall Model Rajesh H. Kulkarni, P.Padmanabham, K.K.Baseer Abstract—Software product quality improvement is a desired attribute and a strenuous effort is required to achieve that.Usability is also a desired attribute as it helps in identifying how effectively user achieves product goals.Concrete efforts to integrate Software Engineering and Human Computer Interaction exist in the form of models by many researchers. Better user experience is an oft expressed and desired quality of the products designed nowadays.Many efforts in this regard lead to various proposals of smooth integration of SE (software engineering) processes with HCI (human computer integration) for product development. One such effort is extended waterfall process model. This paper presents a critical review of extended waterfall model. It also suggests means to bring nearer the two diverse communities of SE and HCI. Index Terms— Usability, SE, HCI, Extended Waterfall Process Model. —————————— —————————— 1 INTRODUCTION He model of waterfall process refer Figure 1 in the field of T software engineering [1] has been playing a chief role Waterfall model is classic SDLC model. This model is also from the past. This model was put forth in 1950s and later, called as a heavyweight process. The lifecycle is long say six it has turned out to be a renowned model in 1970s. Its struc- months. This classic model consists of the phases: Require- ture takes the form of a cascade involving phases and it can be ment, Design, Analyze, Code, Test,and Maintain.
    [Show full text]
  • Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution
    Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution A Consynity white paper Principal, Terry Theisen www.consynity.com Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Introduction 3 Challenges and Opportunities in Application Development and Deployment 4 The Borland ALM Solution 5 Borland ALM Value Proposition 5 Application Lifecycle Quantified Benefits 5 Define Design Develop Test Deploy Manage Borland ALM Customer Results 8 Case Study #1: Deployment Across Large Enterprise 8 Implementation Details Case Study Findings ROI Analysis Case Study #2: Standardizing on Common Solution 10 Implementation Details Case Study Findings Case Study #3: Migration to Borland ALM Solution 11 Implementation Details Case Study Findings ROI Analysis Benefits of an Integrated Suite of Solutions 12 Conclusion: Dramatic ROI with Borland ALM 14 2 2003 Consynity All Rights Reserved Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Introduction In an extremely competitive global economy where advantage is short-lived, companies in all industries continually strive for an edge over the competition. One way for companies to achieve that edge is to deliver better software, faster – software applications that strengthen customer relationships, software that increases operational efficiency, software that creates market leaders. Increasingly companies develop new applications on Java™ systems and Microsoft® .NET platforms, requiring development environments that support both as well as other platforms. Gartner’s “Leading Programming Languages for IT Portfolio Planning” report of September 2002 forecasts that by 2005, over 4.5 million programmers will use Java and .NET languages to build software applications.
    [Show full text]
  • Emerging Trends in Management, IT and Education ISBN No.: 978-87-941751-2-4
    Emerging Trends in Management, IT and Education ISBN No.: 978-87-941751-2-4 Paper 12 IMPLEMENTING PRODUCT DIVERSIFICATION STRATEGIES FOR THE SUSTAINABILITY OF A TECHNOLOGY COMPANY - A CASE OF MICROSOFT CORPORATION Vinayachandra1 & Krishna Prasad K2 1Research Scholar, College of Computer Science and Information Science, Srinivas University, Mangalore, India 2 College of Computer Science and Information Science, Srinivas University, Mangalore, India E-mail : [email protected] Abstract Started in 1975, with a view to develop and vend BASIC interpreter, today, Microsoft develop, produce, license, support and sell worldwide software, user-level electronics, personal computers, and allied services. The company is world-famous because of its best software products Windows operating systems, Office suits, IE and Edge. The company’s notable hardware pieces are Xbox and Microsoft Surface family touch-screen computers. The company is listed as the top software company by Forbes Global for many years. From its inception to date, the company is maintaining top ranking technology-wise, product-wise, service-wise, revenue-wise, and growth-wise. It is possible for the company to sustain growth because of the integration and implementation of product diversification strategy. Over the years the company transformed from just a developer and seller of interpreter to producer & marketer of wide variety of software-hardware products. This paper analyses the strategies the company adopted and incorporated in diversifying product and services lineup to sustain growth and maintain market stability. It also analyses the relevance and acceptability of different Microsoft products, its customer base, and software market share and near future strategies. Keywords: Microsoft, strategies, product diversification, Windows, generic, intensive.
    [Show full text]
  • Agile Software Development Processes
    Agile Software Development Jinjin Li Technische Universitt Berlin Berlin, Germany E-mail:[email protected] Abstract—With the further development of computer technol- customer requirements in the process, in the process people ogy, the software development process has some new goals and will invest resources and then convert it to outputs of project. requirements. In order to adapt to these changes, people has Before the 1960s, computers had just put into practical use, optimized and improved the previous method. At the same time, some of the traditional software development methods have been the software design was often only for a particular application unable to adapt to the requirements of people. Therefore, in re- in the specified design and preparation. The scale of software cent years there have been some new lightweight software process was relative small and usually didn’t have documentation, development methods, That is agile software development, which rarely use a systematic metohd to development. Design and is widely used and promoted. In this paper the author will firstly programming was often equated. introduces the background and development about agile software development, as well as comparison to the traditional software In mid-1960s, large capacity, high speed computers have development. Then the second chapter gives the definition of agile enabled the rapid expansion of computer applications, the software development and characteristics, principles and values. quantity of software development has increased dramatically. In the third chapter the author will highlight several different The Appearance of High-level programming language and agile software development methods, and characteristics of each operating system, causing of changes in the way of computer method.
    [Show full text]
  • How to Become a Programmer Everything (Non-Technical) You Need to Know to Start Making Money Writing Code Rob Walling V1.0
    How to Become a Programmer Everything (Non-Technical) You Need to Know to Start Making Money Writing Code www.SoftwareByRob.com Rob Walling v1.0 Contents Introduction .................................................................................................................................... 4 What is Computer Programming? .................................................................................................. 5 Why Should I Become a Programmer? ........................................................................................... 7 What Are Some Reasons Not to Become a Programmer? ........................................................... 10 What are the Different “Worlds” of Programming? ..................................................................... 11 What Programming Language Should I Learn? ............................................................................ 13 Where Do I Start?.......................................................................................................................... 16 I’ve Built a Project and Decided I Like Programming, What Next? .............................................. 18 I Just Graduated from School, How Can I Get Experience? .......................................................... 20 How Can I Become a Programmer Without Going to College? .................................................... 22 What About Offshoring – Will I have a Job in 5 years? ................................................................ 23 Do I Have to Know Math to be a Programmer?
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • Interviewing Software Testing Job Candidates
    KANER.COM Cem Kaner, Ph.D., J.D. [email protected] P.O. Box 1200 408-244-7000 (Voice) Santa Clara, CA 95052 www.kaner.com 408-244-2181 (FAX) RECRUITING SOFTWARE TESTERS INTERNATIONAL QUALITY WEEK SAN JOSE, CA, JUNE, 1999 This paper is a work in progress. Eventually, it will become a chapter in the 3rd Edition of Testing Computer Software (under development by Cem Kaner, Bob Johnson, Brian Lawrence, Jack Falk, & Hung Quoc Nguyen. This is a multi-year project. Please don't ask me when it will be done. It certainly won't be done in 1999.) I'd appreciate comments and suggestions. (Send them to [email protected].) I don't claim to be an expert on recruiting, but I have been reasonably successful at recruiting testers (and other software workers) over the last 15 years, have made a lot of mistakes, and learned a few lessons. This paper collects some of those lessons. Managers get work done through other people. The people that a manager chooses are the people who will achieve, or fail to achieve, the mission of the group and the tasks assigned by the manager. Recruiting staff is one of the hardest jobs for any manager. Hiring the wrong staff is, I believe, the worst mistake that a manager can make. A good treatment of recruiting would consider the following issues: . A behavioral approach to gathering information . Legal issues . Consensus-driven hiring . A strategy for gathering information . Characteristics of the person you're seeking . Defining the position and characteristics needed for it .
    [Show full text]
  • Why Software Firms Build Hardware – and What Microsoft Is Doing About It
    Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer B.S. Electrical Engineering Grove City College, 2008 M.S. Computer Science Boston University, 2011 SUBMITTED TO THE SYSTEM DESIGN AND MANAGEMENT PROGRAM IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ENGINEERING AND MANAGEMENT AT THE MASSACHUSETTS INSTITUTE OF TECHNOLOGY FEBRUARY 2015 © Ryan M. Shaffer. All rights reserved. The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author: _____________________________________________________ System Design and Management Program January 9, 2015 Certified by: ____________________________________________________________ Michael Cusumano Sloan Management Review Professor in Management Thesis Supervisor Accepted by: ___________________________________________________________ Patrick Hale Director, System Design and Management Fellows Program Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer Submitted to the System Design and Management Program on January 9, 2015 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Engineering and Management ABSTRACT Many software companies build first-party hardware products due to the trend toward smaller, more highly-integrated devices, along with the fast pace of innovation in the technology industry. Building hardware products does not always lead to success and actually creates a financial risk for the company by significantly reducing profit margins as compared to the traditional profit margins to which large software companies are accustomed. Three specific strategies are observed which firms have used successfully in this area.
    [Show full text]
  • Agile Software Development: a Case Study in a Software Company
    Agile Software Development: A Case Study in a Software Company L. Ashkenazi*, A. Shmilovici**, I. Ben-Gal* *Dept. of Industrial Engineering, Tel-Aviv University **Dept. of Information Systems Engineering, Ben-Gurion University In this case study we accompanied a software development project which was performed using the Agile SCRUM method for software development. Subjective parameters of the design and code quality were collected and analyzed and a comparison was performed to an equivalent non-Agile project. We analyzed the software development process from the following aspects: Initial Effort Estimation process compared to the Effort Estimation given for the project by the COCOMO-II model; Control and management process compared to the one suggested by the PERT/CPM and Critical Chain methods. Results and conclusions: The COCOMO II model showed the smallest deviation in its effort estimation from the real required effort; The PERT/CPM method is not recommended as in most cases the real result was out of the PERT/ CPM allowed variance. 1. Introduction and Goals Software development is though from a project management point of view: too many software development projects overrun their schedules, their budgets, and deliver a low quality product. Scrum is an iterative incremental process of software development that focuses on a subset of project management and requirements management. It is one of the new Agile methods for software development [1, 2]. In this case study we accompanied a software development project which was performed using the Scrum method. Subjective and objective parameters of the design and code quality were collected and analyzed and a comparison was performed to an equivalent non-agile project.
    [Show full text]
  • Assessing Application Lifecycle Management Potentials: an Exploratory Industrial Case Study
    ASSESSING APPLICATION LIFECYCLE MANAGEMENT POTENTIALS: AN EXPLORATORY INDUSTRIAL CASE STUDY A THESIS SUBMITTED TO THE GRADUATE SCHOOL OF NATURAL AND APPLIED SCIENCES OF ÇANKAYA UNIVERSITY BY ZÜLEYHA AKGÜN IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN THE DEPARTMENT OF COMPUTER ENGINEERING JANUARY 2019 iii ABSTRACT ASSESSING APPLICATION LIFECYCLE MANAGEMENT POTENTIALS: AN EXPLORATORY INDUSTRIAL CASE STUDY AKGÜN, Züleyha M.Sc., Department of Computer Engineering Supervisor: Dr. Instructor Murat YILMAZ January 2019 Software projects require a good management system to achieve a successful result because they are risky and often spread over a long period. The most important element of a good management is controlled planning. Within the scope of the project, all necessary stages of the software development life cycle need to be accurately and consistently planned and documented to complete the requirements, analysis, design, development process, estimations, risk and change control methods, test and maintenance processes in a complete and accurate manner. The notion of software lifecycle management requires the incorporation of effective software engineering processes that encompass not only development but also deployment and maintenance. Although new methodologies for software engineering continue to emerge, still software development continues to experience a significant amount of failure rates. To overcome the complexities of modern software development, agile development philosophy suggests that software developers should remain involved with the application and working continuously with stakeholders to make required changes incrementally by tracking application changes. Application Lifecycle Management (ALM) is an emerging trend that reflects a novel attitude towards software development also expressed as the DevOps, which blends the tasks performed by a firm’s software development and systems operations teams, monitor software artifacts from inception to completion while changes are noted.
    [Show full text]