Measuring Software Development Project Performance

Adopting agile methodologies to software development processes helps software companies to sustain their growth through efficiency for long term. In the digital transformation era, Industry 4.0 as part of High-Tech Strategy 2020 for Germany involves agile principles and brings the latest technological trends in production process. The purpose of this chapter is to design a proper agile project management performance measurement model for start-up software companies. First, all key performance indicators related to agile development in the literature have been listed. Then KPIs that are provided from literature review with content analysis have been reviewed and categorized by expert opinions that were collected through in-depth interviews. Seven strategic KPIs and their data collection systems are defined and designed. Lastly, process and data collection improvements are recommended in order to sustain agile development measurement model.

Expert Group Knowledge Triggers

Specialised knowledge is a key component of success in an organisational context that resides in the expertise of the organisation's personnel. To explore this situation, an ethnographic case study was chosen in which data was collected from a software development project. Extempore verbal exchanges occur through the interplay of project team members in weekly meetings, as the software was tested, analyzed, and altered in accordance with the customer's needs. Utilizing tacit knowledge from the project members as well as the group, new tacit knowledge surfaces and spirals, which allows it to build over time. Five extempore triggers surfaced during the research generated through explicit stimuli, allowing project members to share and create new knowledge. Through the use of ideas developed by Husserl and Heidegger, this study has cast some light on verbal exchanges that, through their interjection, allow significant learning to take place. The theoretical development places these learning triggers in an interpretive framework, which can add value to other software development projects.

Knowledge Management and Quality Control in Software Outsourcing Projects

This article describes how entrepreneurs face critical risks in terms of quality control and knowledge management while outsourcing software development to independent service providers. First, it is recommended that lump-sum payment contracts should be avoided since software development project involves uncertainty. Instead, a variable payment contingent on observed quality can induce the service provider to exert optimal effort on the project. Second, entrepreneurs must not overlook the importance of providing economic incentives. They can protect their intellectual property by withholding critical knowledge and paying information rents in terms of higher than market wages to the service providers. Third, a startling result is that a low wage nation is not necessarily the optimal location to outsource software development projects. Thus, high wage-strong IPR nations might be chosen instead of low wage-weak IPR nations. Finally, the article explains the apparent paradox that software projects are often outsourced to locations that are characterized by weak intellectual property rights regime and high propensity of imitation.

Towards a Conceptual Framework for Security Requirements Work in Agile Software Development

Security requirement work plays a key role in achieving cost-effective and adequate security in a software development project. Knowledge about software companies' experiences of security requirement work is important in order to bridge the observed gap between software security practices and security risks in many projects today. Particularly, such knowledge can help researchers improve on available practices and recommendations. This article uses the results of published empirical studies on security requirement work to create a conceptual framework that shows key concepts related to work context, this work itself and the effects of this work. The resulting framework points to the following research challenges: 1) Identifying and understanding factors important for the effect of security requirements work; 2) Understanding what is the importance of the chosen requirements approach itself, and; 3) Properly taking into account contextual factors, especially factors related to individuals and interactions, in planning and analysis of empirical studies on security requirements work.

Ten simple rules on writing clean and reliable open-source scientific software

Functional, usable, and maintainable open-source software is increasingly essential to scientific research, but there is a large variation in formal training for software development and maintainability. Here, we propose 10 “rules” centered on 2 best practice components: clean code and testing. These 2 areas are relatively straightforward and provide substantial utility relative to the learning investment. Adopting clean code practices helps to standardize and organize software code in order to enhance readability and reduce cognitive load for both the initial developer and subsequent contributors; this allows developers to concentrate on core functionality and reduce errors. Clean coding styles make software code more amenable to testing, including unit tests that work best with modular and consistent software code. Unit tests interrogate specific and isolated coding behavior to reduce coding errors and ensure intended functionality, especially as code increases in complexity; unit tests also implicitly provide example usages of code. Other forms of testing are geared to discover erroneous behavior arising from unexpected inputs or emerging from the interaction of complex codebases. Although conforming to coding styles and designing tests can add time to the software development project in the short term, these foundational tools can help to improve the correctness, quality, usability, and maintainability of open-source scientific software code. They also advance the principal point of scientific research: producing accurate results in a reproducible way. In addition to suggesting several tips for getting started with clean code and testing practices, we recommend numerous tools for the popular open-source scientific software languages Python, R, and Julia.

The Role of Customers in Extreme Programming Projects

<p>eXtreme programming (XP) is one of a new breed of methods, collectively known as the agile methods, that are challenging conventional wisdom regarding systems development processes and practices. Practitioners specifically designed the agile methods to meet the business problems and challenges we face building software today. As such, these methods are receiving significant attention in practitioner literature. In order to operate effectively in the world of vague and changing requirements, XP moves the emphasis away from document-centric processes into practices that enable people. The Customer is the primary organisational facing role in eXtreme Programming (XP). The Customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing). Unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. This thesis presents a grounded theory of XP software development requirements elicitation, communication, and acceptance, which was guided by three major research questions. What is the experience of being an XP Customer? We found that teams agree that the on-site customer practice is a drastic improvement to the traditional document-centric approaches. Our results indicate, however, that the customers are consistently under pressure and commit long hours to the project in order to fulfil the customer role. So while this approach to requirements is achieving excellent results, it also appears to be unsustainable and thus constitutes a great risk to XP projects. Who is the XP Customer? The initial definition of XP resulted in many people interpreting the onsite customer to be a single person. This research has highlighted that a customer team always exists, and goes further to outline the ten different roles that were covered on the team, which range from the recognised "Acceptance Tester" role to the less recognised roles of "Political Advisor" and "Super-Secretary". What are the practices that support an XP Customer to perform their role effectively on a software development project? An additional eight customer-focused practices have been uncovered to supplement the existing XP practices. These customer-focused practices together enable customers to sustainably drive XP projects to successful completion. The practices range from those that specifically focus on interaction (both with the programmer team and the larger organisation) e.g. "Programmer On-site" and "Roadshows" to those that specifically look to the well-being and effectiveness of the customer (e.g. "Pair Customering") to those that highlight the key steps or activities that need to occur along the way (e.g. "Big Picture Up-Front" and "Recalibration").</p>

The Role of Customers in Extreme Programming Projects

<p>eXtreme programming (XP) is one of a new breed of methods, collectively known as the agile methods, that are challenging conventional wisdom regarding systems development processes and practices. Practitioners specifically designed the agile methods to meet the business problems and challenges we face building software today. As such, these methods are receiving significant attention in practitioner literature. In order to operate effectively in the world of vague and changing requirements, XP moves the emphasis away from document-centric processes into practices that enable people. The Customer is the primary organisational facing role in eXtreme Programming (XP). The Customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing). Unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. This thesis presents a grounded theory of XP software development requirements elicitation, communication, and acceptance, which was guided by three major research questions. What is the experience of being an XP Customer? We found that teams agree that the on-site customer practice is a drastic improvement to the traditional document-centric approaches. Our results indicate, however, that the customers are consistently under pressure and commit long hours to the project in order to fulfil the customer role. So while this approach to requirements is achieving excellent results, it also appears to be unsustainable and thus constitutes a great risk to XP projects. Who is the XP Customer? The initial definition of XP resulted in many people interpreting the onsite customer to be a single person. This research has highlighted that a customer team always exists, and goes further to outline the ten different roles that were covered on the team, which range from the recognised "Acceptance Tester" role to the less recognised roles of "Political Advisor" and "Super-Secretary". What are the practices that support an XP Customer to perform their role effectively on a software development project? An additional eight customer-focused practices have been uncovered to supplement the existing XP practices. These customer-focused practices together enable customers to sustainably drive XP projects to successful completion. The practices range from those that specifically focus on interaction (both with the programmer team and the larger organisation) e.g. "Programmer On-site" and "Roadshows" to those that specifically look to the well-being and effectiveness of the customer (e.g. "Pair Customering") to those that highlight the key steps or activities that need to occur along the way (e.g. "Big Picture Up-Front" and "Recalibration").</p>

A Study on Requirement Specifications and Modifications During the Software Development Life Cycle in M/S Kakunje Software Private Limited

Background/Purpose: In order to face the challenge of optimization and allocation of necessary requirements to complete a project with in the allocated time period, the project manager must be efficient in applying different technical skills and managerial strategies to the project management process. In order to develop a software and mobile application product, a company schedules different process as per the specified order and unique requirements. As the history of project management reminds that most of the industries started to implement this concept by observing the success of mega engineering projects because of the effective utilization of project management concept. Objective: This work is carried to understand the concepts of project management in software firms. To investigate the implementation and importance of these concepts and to know the role of project manager in managing the process in software development. Design/Methodology/Approach: Kakunje Software Private Limited, Mangalore, provides excellent and state-of-the-art customized software and hardware solutions as per the necessities of customers. In order to manage the project activities CEO, CFO and CTO all together acts as project manager. The software development project management process starts by identifying needs and recommending solutions, which can be delivered to value its stakeholders. At the second phase the actual development will begin and the developed software will be tested according to customer requirements. Findings/Results: Budgeting, cost management, finance planning etc., represented by CPM and PERT charts by using Microsoft Project and Atlassian JIRA project management software. The project resources, which are used to manage the project and allocation of technical staff are represented by histogram. With the help of Gantt Chart software development project schedule of 5 month are shown. Conclusion: To manage Kakunje business in an effective and gainful manner, the company managed overall internal and external risks of the project. By using the project management software, the company condensed the project manager’s efforts and human errors to manage multiple projects. Paper Type: Case study-based Research Analysis

Translation of Activities in a Global Virtual Teams Software Development

. This study explores Global Virtual Software Teams’ development practices and try to demystify some of the misconceptions about global software development practices based on findings from the global virtual software teams’ experiment that was carried out at DePaul University from 2011 – 2018. The moments of translation from the perspective of actor-network theory (ANT) was employed in the data analysis, to examine how development approach was selected by the global virtual teams. One of the key findings from our research is that the success of a global software development project does not have a strong dependency on the development approach. While we agree that it is one of the key influencing factors, there are other equally strong factors for global virtual software team’s success.