An Evaluation of Software Measurement Processes in Pakistani Software Industry

Implementing a successful measurement process is a challenging task. Most measurement studies report measurement models, experiences, and lessons learned based on pilot projects or case studies in a limited scope to overcome specific challenges. This paper identifies 14 basic measurement practices and proposes a model of 18 success factors for implementing measurement processes with respect to the identified measurement theories in our systematic literature review (SLR), i.e., A systematic literature review on software measurement programs, by Tahir et al. , 2016. In addition, a survey is conducted to evaluate the state of measurement practices and to validate the proposed model based on the feedback from 200 software professionals working in Pakistani software industry. The state of measurement practices in the industry is mostly not according to the identified measurement theories in the SLR. For instance, more than 50 measurement models reported in the literature but only 10% software organizations follow any measurement model. 75% of organizations do not follow any measurement standard. 80% software organizations do not use any measurement tool. The proposed model is validated by applying structural equation modeling on the survey data. Furthermore, among 18 success factors, it is statistically significant that Pakistani software professionals strongly believe in necessity of three factors for successful implementation of a measurement process, i.e., synchronization between measurement process and software process improvement, use of measurement standards, and use of measurement models. In addition, they also believe that a successful measurement process will improve prediction, monitoring and management of software projects, and support in achievement of individual and organization-wide objectives. Software organizations might consider this paper in planning and improving their measurement processes

The Contribution of a Model to Estimate Activities in Software Projects Based on Lessons Learned

Purpose – The main objective of this article is to propose the use of a model developed by Matturo and Silva (2010) to capture knowledge in software projects based on the lessons learned.Design/methodology/approach – We carried out a qualitative research from a descriptive perspective through a single case study applied to an Enterprise Information Technology company. The company is a leader in market solutions to support customer experience management. For the data collection process, we used systematic literature review, document analysis and semi-structured interviews.Findings – The results supported project managers to better understand the storage and use of information from lessons learned in dimensioning the use of human resources and to support the estimation of new project activities. In addition, the results showed the organization's disregard for not giving due importance to the information and knowledge generated during the life cycle of a project.Research, Practical & Social implications – The model allows companies to obtain new knowledge or consult existing knowledge throughout the life cycle of projects and to support project managers in the process of estimating activities and preparing budgets with greater precision, using the information from lessons learned as a support. acquired in the completed projects.Originality/value – The lack of information in the initial scope of the project and in the definition of activities in the human resource allocation process hinder the duration of the project's development activities, directly resulting in inaccurate estimates. As a result, this scenario contributes to the increased risk of deviations in terms and / or costs of software projects.

Measuring and improving Agile Processes in a small-size software development company

Context: Agile software development has become commonplace in software development companies due to the numerous benefits it provides. However, conducting Agile projects is demanding in Small and Medium Enterprises (SMEs), because projects start and end quickly, but still have to fulfil customers' quality requirements. Objective: This paper aims at reporting a practical experience on the use of metrics related to the software development process as a means supporting SMEs in the development of software following an Agile methodology. Method: We followed Action-Research principles in a Polish small-size software development company. We developed and executed a study protocol suited to the needs of the company, using a pilot case. Results: A catalogue of Agile development process metrics practically validated in the context of a small-size software development company, adopted by the company in their Agile projects. Conclusions: Practitioners may adopt these metrics in their Agile projects, especially if working in an SME, and customise them to their own needs and tools. Academics may use the findings as a baseline for new research work, including new empirical studies.The authors would like to thank all the members of the QRapids H2020 project consortium.Peer ReviewedPostprint (published version