Estimating, planning and managing Agile Web development projects under a value-based perspective

Context: The processes of estimating, planning and managing are crucial for software development projects, since the results must be related to several business strategies. The broad expansion of the Internet and the global and interconnected economy make Web development projects be often characterized by expressions like delivering as soon as possible, reducing time to market and adapting to undefined requirements. In this kind of environment, traditional methodologies based on predictive techniques sometimes do not offer very satisfactory results. The rise of Agile methodologies and practices has provided some useful tools that, combined with Web Engineering techniques, can help to establish a framework to estimate, manage and plan Web development projects. Objective: This paper presents a proposal for estimating, planning and managing Web projects, by combining some existing Agile techniques with Web Engineering principles, presenting them as an unified framework which uses the business value to guide the delivery of features. Method: The proposal is analyzed by means of a case study, including a real-life project, in order to obtain relevant conclusions. Results: The results achieved after using the framework in a development project are presented, including interesting results on project planning and estimation, as well as on team productivity throughout the project. Conclusion: It is concluded that the framework can be useful in order to better manage Web-based projects, through a continuous value-based estimation and management process.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

Analyzing the Trade-Off between Traditional and Agile Software Development - A Cost/Risk Perspective

Digitalization heralds a new era of enterprise IT. It challenges CIOs to find a balance between renovating legacy IT and seizing the opportunities of digital technologies to keep up with competitors and start-ups. This requires organizations to operate two software development modes simultaneously: the traditional and the agile mode. Despite substantial research on both modes, little is known about whether to implement distinct software development projects traditionally or agile. As a first step to addressing this gap, we propose a quantitative decision model that compares the cost and risk profiles of both modes associated with the implementation of a distinct project. The decision model integrates qualitative and quantitative characteristics of the project in focus and of the traditional and the agile mode. As for evaluation, we implemented the decision model as a software prototype and validated its behavior using sample projects as well as a sensitivity analysis

Examining Organizational Implications of Innovations in Software Development: Agile and Simulation

Software development is a complex process involving stakeholders with divergent perspectives, skills, and responsibilities who must work together to create a software product of high quality. Problems such as miscommunications and misunderstandings among project stakeholders, especially between the IS and business functions, exist in software development. To help address these issues, innovative methods are being increasingly adopted such as the Agile software development methodology and software simulation. These two methods share the same goal of bringing stakeholders together to establish a common understanding so that the system can be built quicker and better than with traditional approaches. This dissertation, which consists of two essays, focuses on these two innovative methods of software development – Agile methodology and software simulation – and examines how they can be best applied and under what conditions they lead to positive outcomes. The first essay studies the introduction of the Agile methodology in a company steeped in the traditional Waterfall software development method. The essay reports on how the Agile methodology was integrated with the traditional software development process including an in-depth analysis of the organizational and project controller-controlee relationships before and after the Agile methodology implementation. We find that outcome control, which was the predominant control mechanism, used in the company’s Waterfall development process, gave way to a hybrid control mechanism that possesses attributes of emergent control while maintaining vestiges of some Waterfall-like outcome control mechanisms. In addition, we find that the IS function must relinquish some influence over software development resources with the introduction of the Agile method. Lessons learned from this case study point to the complexity of designing organizational and project control mechanisms during the transition from the Waterfall to an Agile approach.As much as innovations in software development methods improve the software creation process, the risk of failing to create a quality software product are heightened when requirements are misinterpreted. Recent innovations in requirements simulations provide stakeholders with an opportunity to see realistic simulations of the system before it is built to quickly reach a common understanding of the requirements. Hence, the second essay empirically examines how the use of software simulations with various degrees of realism can help mitigate project requirements risk including project novelty, data interdependence, system interdependence, requirements instability, and requirements diversity, leading to higher software product quality. Results suggest that simulation realism partially mediates the relationship between project requirement risk and software product quality indicating the importance of investing in highly realistic simulations in software project requirement risk mitigation.Overall, this dissertation sheds light on how software development managers can employ innovative methods such as an Agile method and software simulation to bring greater stakeholders unity and produce higher quality software products

Hitting the Bullseye: The Influence of Technical Debt on the Accuracy of Effort Estimation in Agile Projects

As firms rapidly develop solutions in order to increase revenue and market share, software development decisions considered to be temporary shortcuts and/or compromises may be implemented. These shortcuts represent “technical debt,” a metaphor which succinctly describes a software solution that should be “paid in full” or remediated in the future. Software architects and developers intend to resolve the “debt” in future product releases, but practitioners recognize that the challenge of always innovating may indefinitely postpone this remediation effort. Further, the accumulation of technical debt may have long term impact on the product’s maintainability by the software development teams and, consequently, impact the effort estimate delivered to management for forecasting product delivery timelines and product revenue expectations. While there are multiple publications that have studied effort estimation in traditional and agile software development strategies, there is limited research which considers technical debt during the estimation effort. As a result, the purpose of this dissertation is to design and propose a research model intended to determine whether or not the consideration of technical debt during the effort estimation process will improve the accuracy of the effort estimate in an agile project

Performance requirements verification during software systems development

Requirements verification refers to the assurance that the implemented system reflects the specified requirements. Requirement verification is a process that continues through the life cycle of the software system. When the software crisis hit in 1960, a great deal of attention was placed on the verification of functional requirements, which were considered to be of crucial importance. Over the last decade, researchers have addressed the importance of integrating non-functional requirement in the verification process. An important non-functional requirement for software is performance. Performance requirement verification is known as Software Performance Evaluation. This thesis will look at performance evaluation of software systems. The performance evaluation of software systems is a hugely valuable task, especially in the early stages of a software project development. Many methods for integrating performance analysis into the software development process have been proposed. These methodologies work by utilising the software architectural models known in the software engineering field by transforming these into performance models, which can be analysed to gain the expected performance characteristics of the projected system. This thesis aims to bridge the knowledge gap between performance and software engineering domains by introducing semi-automated transformation methodologies. These are designed to be generic in order for them to be integrated into any software engineering development process. The goal of these methodologies is to provide performance related design guidance during the system development. This thesis introduces two model transformation methodologies. These are the improved state marking methodology and the UML-EQN methodology. It will also introduce the UML-JMT tool which was built to realise the UML-EQN methodology. With the help of automatic design models to performance model algorithms introduced in the UML-EQN methodology, a software engineer with basic knowledge of performance modelling paradigm can conduct a performance study on a software system design. This was proved in a qualitative study where the methodology and the tool deploying this methodology were tested by software engineers with varying levels of background, experience and from different sectors of the software development industry. The study results showed an acceptance for this methodology and the UML-JMT tool. As performance verification is a part of any software engineering methodology, we have to define frame works that would deploy performance requirements validation in the context of software engineering. Agile development paradigm was the result of changes in the overall environment of the IT and business worlds. These techniques are based on iterative development, where requirements, designs and developed programmes evolve continually. At present, the majority of literature discussing the role of requirements engineering in agile development processes seems to indicate that non-functional requirements verification is an unchartered territory. CPASA (Continuous Performance Assessment of Software Architecture) was designed to work in software projects where the performance can be affected by changes in the requirements and matches the main practices of agile modelling and development. The UML-JMT tool was designed to deploy the CPASA Performance evaluation tests

Rapid Software Development Life Cycle in Small Projects

Small software projects are becoming more usual nowadays. Whether a small project is conducted privately or professionally, the management of the project and its phases is much easier with proper tools and frameworks. The research target of this thesis is to find out a proper life cycle model for small software projects. This thesis is conducted for Softwarehouse, a professional division of IT services in the University of Turku. The official guide for Scrum framework is adhered in software development but when it comes to formally managing various phases of a software project (planning, design, implementation, testing, reviewing etc.) there is room for improvement. Managing software projects with a proper set of tools and procedures would be beneficial as Softwarehouse works on many projects concurrently. The intended life cycle model has to be formal and heavy enough so that the benefits of agile project management can be received. However too rigid a model can be too arduous and exhausting to use, which could result in the decrease of Softwarehouse’s production volume. Therefore the model has to be light enough to maintain rapid software development and creative atmosphere within the Softwarehouse. This thesis begins by giving outline of existing software development life cycle models and followed by relevant literary exploration. After this the research case is explained in greater detail. These give the foundation and rationale to propose a suitable model. The model is experimented empirically and reviewed by partaking personnel. The results are reviewed and discussed. Finally topics for future research are suggested

CHARTING PROGRESS IN THE SOFTWARE ACQUISITION PATHWAY

The Department of the Navy (DON) recently implemented the Department of Defense (DOD) Software Acquisition Pathway (SWP), a software acquisition strategy for custom application and embedded software. The purpose of the SWP is to enable rapid and iterative delivery of high-priority software capability to the intended user. But while the SWP uses an agile software development approach, neither the DOD nor the DON have yet provided comprehensive governance tools and methods for SWP programs to iteratively plan, track, and assess acquisition outcomes in agile environments. To close this gap, the author systematically researched commercial software engineering management and digital product development practices as well as prior DOD software acquisition reform studies. Based on the results, the author showed that Earned Value Management is incompatible with the SWP and recommended alternative techniques to measure cost and schedule performance. Additionally, the author recommended a phased approach to manage DON SWP custom application programs, whereby a minimal, unitless work breakdown structure is used to track progress until demonstrating the minimum viable product to the user in a testing environment; product-based metrics are then tracked until initial release of the custom application software; and then outcome-based goals are iteratively set, tracked, and assessed using the Objectives and Key Results framework for as long as the custom application software is in use.Captain, United States Air ForceApproved for public release. Distribution is unlimited

Agent Oriented Software Engineering (AOSE) Approach to Game Development Methodology

This thesis investigates existing game development methodologies, through the process of researching game and system development models. The results indicate that these methodologies are engineered to solve specific problems, and most are suitable only for specific game genres. Different approaches to building games have been proposed in recent years. However, most of these methodologies focus on the design and implementation phase. This research aims to enhance game development methodologies by proposing a novel game development methodology, with the ability to function in generic game genres, thereby guiding game developers and designers from the start of the game development phase to the end of the implementation and testing phase. On a positive note, aligning development practice with universal standards makes it far easier to incorporate extra team members at short notice. This increased the confidence when working in the same environment as super developers. In the gaming industry, most game development proceeds directly from game design to the implementation phase, and the researcher observes that this is the only industry in which this occurs. It is a consequence of the game industry’s failure to integrate with modern development techniques. The ultimate aim of this research to apply a new game development methodology using most game elements to enhance success. This development model will align with different game genres, and resolve the gap between industry and research area, so that game developers can focus on the important business of creating games. The primary aim of Agent Oriented Agile Base (AOAB) game development methodology is to present game development techniques in sequential steps to facilitate game creation and close the gap in the existing game development methodologies. Agent technology is used in complex domains such as e-commerce, health, manufacturing, games, etc. In this thesis we are interested in the game domain, which comprises a unique set of characteristics such as automata, collaboration etc. Our AOAB will be based on a predictive approach after adaptation of MaSE methodology, and an adaptive approach using Agile methodology. To ensure proof of concept, AOAB game development methodology will be evaluated against industry principles, providing an industry case study to create a driving test game, which was the problem motivating this research. Furthermore, we conducted two workshops to introduce our methodology to both academic and industry participants. Finally, we prepared an academic experiment to use AOAB in the academic sector. We have analyzed the feedbacks and comments and concluded the strengths and weakness of the AOAB methodology. The research achievements are summarized and proposals for future work outlined

Proceedings, MSVSCC 2011

Proceedings of the 5th Annual Modeling, Simulation & Visualization Student Capstone Conference held on April 14, 2011 at VMASC in Suffolk, Virginia. 186 pp

Task 10: Research an Alternative Instructional Design Model

Under authority of the Federal Aviation Administration (FAA), the Center of Excellence (COE) Technical Training Human Performance (TTHP) Task 10 research team has prepared a comprehensive technical report and an executive summary for the Air Traffic Organization (ATO) concerning the instructional development (ID) of occupational education and training for Air Traffic (AT) controllers and Technical Operations (TO) technicians. Research included: • Front-end analysis of available FAA courses and government furnished information (GFI), including course-development documentation and associated guidance, policies, and regulations. • Structured and semi-structured data-gathering techniques in cooperation with Instructional Systems Specialists (ISS), ISS Managers, and Requirements personnel. • Informal observations of validation events for Air Traffic training. • Analysis of the relevant literature from academic, government, and industry domains. The executive summary describes the findings and observations of issues directly related to the ID process and potential solutions based on findings from this comparative analysis. The comprehensive report that follows includes these and additional observations and recommendations as well as the project overview, an introduction to best practice research, the research methodology, presentation and analysis of the results, and discussion of the findings and conclusions