Scrum Framework Implementation for Software Development Projects in IT Companies

The project success needs to be measured to find out whether the implementation method is fit. The assessment criteria used to measure project success vary and depend on several factors, such as scope and complexity. In IT projects, two well-known methods are Traditional and Agile. This study assesses whether the Scrum applied to several ongoing projects in a company is appropriate by finding the criteria used in project measurement and evaluating the project’s success. This study examines an IT company that focuses on providing network and application development for its parent company to choose a suitable method for its projects. Currently, the Agile method (Scrum) is used in several projects as a pilot. We utilize the AHP method to determine the project success measurement and whether the Agile (Scrum) method can be applied throughout all IT projects in the company. The study takes the management point of view; thus, it does not focus on the conformity of the framework implementation. Keywords: Project Management, Project Success, Scrum, Software Development, Success Criteri

Enhancing Software Team Planning and Delivery Performance using Agile Driven Quality Measures: Approach, Results, and Recommendations

Implementing a performance-management program in an agile software-development organization is important to retain sight of software team performance as a whole as well as linking performance-management metrics to business value. The evaluation criteria for software engineers’ performance have been traditionally driven by metrics that don’t fit into agile-development principles. This research implements a measurement metric that aligns with agile-development core values and principles to evaluate engineers in a software engineering firm using the Scrum development method. The research focused on measuring and evaluating the productivity, development efficiency, social skills, team collaboration and breadth of knowledge. Observing the Productivity Index (PI), Actual Productivity for software Engineers (APSE), and Productivity Variance (PV) for individual software engineers and the development team at the end of each sprint helped the development team have a better understanding of its productivity levels in a matter that facilitated planning future sprints. In addition, this productivity measure helped early identification of productivity challenges encountered by several software engineers and productivity identification of productivity challenges encountered by several software engineers. Keywords: Agile development, software teams, process measurement, scrum, productivity, efficiency, software metrics, software project measuremen

Application of Meta-Programming Techniques for Accelerating Software Development and Improving Quality.

Annotation- A contemporary software tool has been devised to evaluate software quality through metric analysis techniques This tool calculates pertinent metrics utilizing quality indicators and establishes a composite quality indicator value for software products The intricacies of software quality assessment processes have been elucidated including the examination of software quality s standardization as well as the presentation level of its model This enables the potential for enhancement through the formulation of suitable criteria for quality assessment refining models for metric analysis and quantitatively measuring quality across all phases of project implementation Notably the use of metric analysis to gauge software quality reveals a lack of standardized metrics resulting in varying assessment methods and metrics from different measurement system providers Interpreting metric values also proves challenging for most software users due to a lack of clarity and informativeness Furthermore it has been discovered that while decisions based on cost development duration and designer company reputation influence software implementation choices they do not always guarantee optimal software qualit

Records management capacity and compliance toolkits : a critical assessment.

This article seeks to present the results of a project that critically evaluated a series of toolkits for assessing records management capacity and/or compliance. These toolkits have been developed in different countries and sectors within the context of the e-environment and provide evidence of good corporate and information governance. Design/methodology/approach - A desk-based investigation of the tools was followed by an electronic Delphi with toolkit developers and performance measurement experts to develop a set of evaluation criteria. Different stakeholders then evaluated the toolkits against the criteria using cognitive walkthroughs and expert heuristic reviews. The results and the research process were reviewed via electronic discussion. Findings - Developed by recognised and highly respected organisations, three of the toolkits are software tools, whilst the fourth is a methodology. They are all underpinned by relevant national/international records management legislation, standards and good practice including, either implicitly or explicitly, ISO 15489. They all have strengths, complementing rather than competing with one another. They enable the involvement of other staff, thereby providing an opportunity for raising awareness of the importance of effective records management. Practical implications - These toolkits are potentially very powerful, flexible and of real value to organisations in managing their records. They can be used for a "quick and dirty" assessment of records management capacity or compliance as well as in-depth analysis. The most important criterion for selecting the appropriate one is to match the toolkit with the scenario. Originality/value - This paper aims to raise awareness of the range and nature of records management toolkits and their potential for varied use in practice to support more effective management of records

A Discrimination of Software Implementation Success Criteria

Software implementation projects struggle with the delicate balance of low cost, on-time delivery and quality. The methodologies and processes used to create and maintain a quality software system are expensive to deploy and result in long development cycle-time. However, without their deployment into the software implementation life-cycle, a software system will be undependable, unsuccessful. The purpose of this research is to identify a succinct set of software implementation success criteria and assess the key independent constructs, activities, carried out to ensure a successful implementation project. The research will assess the success of a software implementation project as the dependent construct of interest and use the software process model (methodology) as the independent construct. This field research involved three phases: (1) criteria development, (2) data collection, and (3) testing of hypotheses and discriminant analysis. The first phase resulted in the development of the measurement instruments for the independent and dependent constructs. The measurement instrument for the independent construct was representative of the criteria from highly regarded software implementation process models and methodologies, e.g., ISO9000, Software Engineering Institute's Capability Maturity Model (SEI CMM). The dependent construct was developed from the categories and criteria from the Delone and McLean (1992) MIS List of Success Measures. The data collection and assessment phase employed a field survey research strategy to 80 companies involved in internal software implementation. Both successful and unsuccessful software implementation projects (identified by the Delone/McLean model) participated. Results from 165 projects were collected, 28 unsuccessful and 137 successful. The third phase used ANOVA to test the first 11 hypotheses and employed discriminant analysis for the 12th hypothesis to identify the "best set" of variables, criteria, that discriminate between successful and unsuccessful software implementation projects. Twelve discriminating variables out of 67 were identified and supported as significant discriminators between successful and unsuccessful projects. Three of the 11 constructs were found not to be significant investments for the successful projects

Integration of Correlation Processes in Design Systems.

The integration of correlation processes in design systems has as a target measurements in 3D directly and according to the users criteria in order to generate the required database for the development of the project. In the phase of photogrammetric works, internal and external orientation parameters are calculated and stereo models are created from standard images. The aforementioned are integrated in the system where the measurement of the selected items is done by applying developed correlation algorithms. The processing period has the tools to carry out the calculations in an easy and automatic way, as well as image measurement techniques to acquire the most correct information. The proposed software development is done on Visual Studio platforms for PC, applying the most apt codes and symbols according to the terms of reference required for the design. The results of generating the data base in an interactive way with the geometric study of the structures, facilitates and improves the quality of the works in the projects

Quality measurement in agile and rapid software development: A systematic mapping

Context: In despite of agile and rapid software development (ARSD) being researched and applied extensively, managing quality requirements (QRs) are still challenging. As ARSD processes produce a large amount of data, measurement has become a strategy to facilitate QR management. Objective: This study aims to survey the literature related to QR management through metrics in ARSD, focusing on: bibliometrics, QR metrics, and quality-related indicators used in quality management. Method: The study design includes the definition of research questions, selection criteria, and snowballing as search strategy. Results: We selected 61 primary studies (2001-2019). Despite a large body of knowledge and standards, there is no consensus regarding QR measurement. Terminology is varying as are the measuring models. However, seemingly different measurement models do contain similarities. Conclusion: The industrial relevance of the primary studies shows that practitioners have a need to improve quality measurement. Our collection of measures and data sources can serve as a starting point for practitioners to include quality measurement into their decision-making processes. Researchers could benefit from the identified similarities to start building a common framework for quality measurement. In addition, this could help researchers identify what quality aspects need more focus, e.g., security and usability with few metrics reported.This work has been funded by the European Union’s Horizon 2020 research and innovation program through the Q-Rapids project (grant no. 732253). This research was also partially supported by the Spanish Ministerio de Economía, Industria y Competitividad through the DOGO4ML project (grant PID2020-117191RB-I00). Silverio Martínez-Fernández worked in Fraunhofer IESE before January 2020.Peer ReviewedPostprint (published version