FIGURE 7 - uploaded by Naveed Ahmad
Content may be subject to copyright.
Source publication
Flexible nature of scope definition in agile makes it difficult or impossible to measure its quality and completeness. The aim of this paper is to highlight the important ingredients of scope definition for agile projects and to present a method in order to measure the quality and completeness of their scope definitions. The proposed method conside...
Context in source publication
Context 1
... assumptions are tested using different methods. The data is checked for outliers using regression; the results indi- cate that there is one outlier in data. This is participant 2 iteration 1 where this participant took 18 minutes to identify 18 problems in evaluation of a user story. Linearity is tested using scatter matrix (see 7). Fig. 7 shows that a linear rela- tionship exists between both the dependent variables for two groups of independent variable. Shapiro Wilk is used to test normality and results indicate that dependent variables have a normal distribution; Collinearity -it is tested using correla- tion, and results indicate that dependent variables do not have ...
Similar publications
Video game development is a complex endeavor, often involving complex software, large organizations, and aggressive release deadlines. Several studies have reported that periods of "crunch time" are prevalent in the video game industry, but there are few studies on the effects of time pressure. We conducted a survey with participants of the Global...
Digital innovations often follow a more fluid innovation process and therefore require different ways of managing the front end of innovation. Agile as alternative to established front end management practices is often suggested, potentially combined with Stage‐Gate®, in what is called a hybrid Agile‐Stage‐Gate® model, to reap the benefits from bot...
Proposing and implementing software systems, especially web applications for e-commerce using the traditional monolithic approach has been the norm, however, as new user requirements force organisations and developers to add more functionalities to their systems, and as user demands increases, the performance of monolith applications decreases, and...
Commonly, the instruction of Software Engineering implements processes that are inherent to the theory and practice of software development. Traditional and Agile methods lay the foundation for building "functional software products" that meet the requirements of a system of a larger scope. However, if we consider software as a product that frequen...
The current stage of technology development is characterized by an increase in the complexity of the created anthropogenic systems, a constant expansion of the scope of information technologies, an increase in the intelligence level of the created systems, and the appearance of new paradigms for building information-oriented systems such as cyber-p...
Citations
... The formal specification of IRDSS using the Z language adds rigor to the approach. Through an experiment involving fifteen web projects, the proposed system demonstrates improved estimation accuracy compared to traditional methods like Delphi and Planning Poker, offering potential directions for more effective software project development in the Scrum community.In reference [6], the authors express concern about the inherent flexibility of the agile methodology, which makes it challenging to accurately predict initial phase timelines and costs. To address this, a method is proposed that assesses project scope by focusing solely on critical elements. ...
Effort estimation is a critical aspect of every software creation project, irrespective of its development discipline, is it traditional or agile. Despite the initial limited project knowledge, accurate estimation of workload and effort holds immense significance for project success. This study addresses the challenges surrounding precise effort estimation and introduces the poker planning method utilizing a modified Fibonacci sequence as a potential solution. The aim of this paper is to examine the behavior and effectiveness of the modified Fibonacci sequence in the context of cost estimation within the agile methodology. By leveraging historical data, expert opinions, and an iterative approach, the proposed technique is evaluated and compared against traditional methods. The results provide insights into the performance of the modified Fibonacci sequence, offering a valuable contribution to enhancing accuracy in cost estimation for agile software development projects.
... One element that might directly affect the budget and schedule is the project's scope. However, it seems to be among the most disregarded areas in both agile and traditional approaches [15]. Agile is known for its speed of progress and readiness to embrace change [16]. ...
... These are used to decide the project scope [18]. Despite having those five levels, Agile's nature was flexible and dynamic [15], since the customer is involved in the process at the revisit in each iteration planning phase when establishing the scope and definition of done; and keeps confirming the required features to be developed [18]. The first features to be created and released should be those with the highest market impact. ...
... The first features to be created and released should be those with the highest market impact. These procedures lead to up to 30% final scope modifications in agile during each iteration [15]. It might lead to the project to be delayed and the product's cost to rise. ...
The strategy of Financial Services in Libyan pioneer companies has begun to achieve a transformation from providing ordinary services to electronic services through financial services technologies, which necessitates the qualification of employees in Libyan software companies. To facilitate this, recent agile software agile project management strategies and their possible advantages, disadvantages, and possible limitations will be discussed. In the context of improving software development for changing work conditions or requirements, he current state of agile project management (APM) will be studied and enhancement with best APM practices will be implemented within Masarat IT & Financial Services, a pioneer Libyan company. Our findings demonstrate that the application of agile project management best practices has a positive impact on project success. The benefits of agility were immediately apparent, and the advantages of adopting APM methodologies were a crucial factor in successfully completing the project.
... The estimation technique starts during the SDLC planning phase and continues through all phases of the SDLC. The time goal of Cost estimate in scrum project with the decision-based effort estimation technique the project and the cost of the project are the two main components of product development (Amjad et al. 2017). The cost of a product is an extremely important aspect of its development. ...
... This may be the cause of the poor relationship between the company and its customers because the client has a genuine motive in this phase of development. The fundamental cause of the venture's cost increase is a request for modification from the user's side (Amjad et al. 2017). The price of the product exceeds the pre-determined price of the product due to progress requests from the user's side. ...
Due to their expanded methods, agile methodologies are now the accepted standard for software development. Collaboration, addressing changing requirements with workable software, and simple design are just a few aspects of typical techniques. By employing the aforementioned approaches, these methods handle the issue of variable requirements. As a result, these methods lower the cost of changes at a later point in the software development process. Due to the unpredictability of requirements, such methodologies do not hold up well for an early estimate of size, cost, and timeframe. Agile techniques, it has been noticed, rely on expert analysis and prior project information to estimate cost, complexity, and time. Such approaches, it has been discovered, do not take into account the critical aspects affecting the project's cost, complexity, and timeframe when estimating. Based on predefined estimation methods including analogy and planning, poker becomes unexpected in the lack of historical data and professionals. As a result, there is a pressing need to develop a simple computational solution that takes into account the factors that influence the project budget, complexity, and timeframe. It also serves as a foundation for unskilled practitioners to make better estimates. The research of both traditional and agile estimation techniques with a comparability of concepts and variations is presented in this work. We looked into a few key elements that influence the estimation of an agile project with lower, moderate, and higher scalability factors. Integrating critical aspects is also recommended using the Constructive Agile Estimation Algorithm (CAEA).
... Digital transformation is the subject of the study "Future software organizationsagile goals and roles" where the author explores the way in which systems are developed and the alignment with business processes [43]. Scope management and prioritization of backlog items are addressed in the authors' article "Calculating Completeness of Agile Scope in Scaled Agile Development" [44]. Adding to the subject of digital transformation, another subject of equal importance, industry 4.0, is the focus of the article "The Demands of Industry 4.0 on Project Teams" which deals with the profile of the professionals involved in this journey with great capacity for innovation, integration of technologies, project management and great ability to solve complex problems [45]. ...
As a challenge of Digital Transformation in companies, projects are a source of significant changes in processes, products, systems and business models. In this context, portfolio management plays a significant role in coordinating and prioritizing initiatives that need to overcome traditional practices. Another significant pillar for Digital Transformation to be sustainable is the need for effective Knowledge Management in the process of digitizing organizations. The objective of this study is to carry out a systematic review of the literature on agile portfolio management in Digital Transformation, in order to identify which frameworks or practices are adopted in companies and how Knowledge Management impacts them. Preferred reporting guidelines for systematic reviews (PRISMA) in Scopus, Web Of Science and IEEE databases were used. The methodology was prepared considering the following steps: (1) research design, (2) data collection, (3) data analysis and (4) review. The research resulted in 34 articles mapped and analyzed and little explored gaps were identified, such as themes related to financial structure, relationship with suppliers, performance indicators related to the subject of agile portfolio management. It was also identified that there are few scientific studies addressing how Knowledge Management can be used in portfolio management.
... Agile is the most used model for software development, but still has some is-sues that directly impact its proficient productivity. The main issues with the development are due to methods used in agile software development [14]. One of the most valuable features is a change request from the client because the client is the owner of the product backlog [15]. ...
... For the completion of the study, we have followed an agile development score rating methodology. It contributes to evaluating the depth and accuracy of agile project management specifications, as well as providing a roadmap for experts in identifying flaws in agile development [14]. ...
... A search query is used to do systematic searches across the digital libraries including Google Scholar, IEEE, Science Direct, ACM, Springer, Hindawi, MDPI, Sage, and Hindawi [14,16]. All reputed data search bases are used for the collection of related works ...
Software engineering has many software development life cycle (SDLC) models to develop a software application and the latest SDLC models have been provided by agile methods. The agile methodology has been introduced due to some existing lacks in software development. Now agile methodology is used to overcome these deficiencies and improve software development. The use of the agile methodology is increased within software industries due to its distinctive features such as enabling change requests from the client at any stage of a project, client satisfaction, iterative development, and client-developer interaction. Another reason for agile adoption is the methods that are being used for agile software development. These methods include Scrum, Feature drive development, Extreme programming, and Dynamic system development methods. However, the agile methodology has some issues for project development and management. In this study, we discuss all these issues which are related to agile methods and individuals (i.e. team and developer). Further, we suggest the possible improvements that need to be introduced in the agile methodology. We believe such improvements is to make the agile methodology more productive for development environments.
... A typical scenario for large software development organizations in the early 2000s was the implementation of defined development processes, including systems to ensure quality through all the processes, which place constraints on the development team, limiting development practices and affecting how quickly they can develop software [67]. More recently, cases of software developments in larger projects or multiple projects demonstrate the companies' interest in applying methodologies that provide better results, greater flexibility, and faster customer response [3,7,82]. ...
Organizations have increasingly applied agile project management; however, they face challenges in scaling up this approach to large projects. Thus, this study investigates the key barriers and benefits of scaling agile methods to large projects. The research approach is a literature review, applying bibliometrics and content analysis with Bibliometrix and UCINET software. We conducted a sampling process in the Web of Science and Scopus databases and surveyed 76 articles in depth. The results identified 53 barriers clustered into six main categories: organizational issues, managerial issues, agile method-specific barriers, product/process issues, customer issues, and team issues. Thirty-two benefits were coded and clustered into three categories: business, project, and team. Requirement management appears as a core topic, impacting both barriers and benefits for scaling agile project management. We identified a strong relationship between the barriers and benefits. These results can be used to create questionnaires to explore these barriers and benefits in practice.
... al, 2014), and the requirements volatility (Kawamoto and De Almeida, 2017). Particularly when the changes occur at 30% inevery single iterationof agile development (Amjad,et al., 2017). ...
... There are some efforts to adhere quality assurance in agile. For example, Amjad and colleagues (Amjad, et al., 2017) proposed a method, called A-SPSRI, that able to measure the quality and completeness of scope definition of the user stories. While, there are also tools and techniques to ensure effective collaboration and the successful development of the product (Hess, Diebold, and Seyff, 2019). ...
In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.
... Agile Software Development (ASD) is an iterative approach to delivering software products. The term "agility" implies adaptability [1], flexibility [2], and close collaboration with the customer [3]. An Agile approach assumes sensible values such as trust [4], responsibility [5] and loyalty [6]. ...
Agile Software Development methods have become a widespread approach used by the software industry. Non-functional requirements (NFRs) are often reported to be a problematic issue for such methods. We aimed to identify (within the context of Agile projects): (1) the issues (challenges and problems) reported as affecting the implementation of NFRs; and (2) practices that facilitate the successful implementation of NFRs. We conducted a systematic literature review and processed its results to obtain a comprehensive summary. We were able to present two lists, dedicated to issues and practices, respectively. Most items from both lists, but not all, are related to the requirements engineering area. We found out that the issues reported are mostly related to the common themes of: NFR documentation techniques, NFR traceability, elicitation and communication activities. The facilitating practices mostly cover similar topics and the recommendation is to start focusing on NFRs early in the project.
... Alami (2016) found that many software projects lack a well-developed set of itemised requirements and require subsequent SOW modifications after vendor proposals are received. Amjad et al. (2017) highlighted the importance of SOW definition in software projects to help proposing software vendors account all SOW and project goals when preparing their proposal responses. Arcidiacono (2017) indicated that software project failure occurs due mainly to poor project management (54% of failures captured in this study cited this cause), lack of defined project delivery activities (21%), project teams that lack necessary skills (8%), inefficient implementation approaches (3%), and project funding issues (14%). ...
The request for proposal (RFP) process is essential to the subsequent success of software project implementations. The RFP seeks to identify an appropriate software solution to best meet the client organisation’s scope and contractually establishes the project’s baseline cost and schedule expectations. However, there is a lack of RFP-research related to the current state of practice in software projects. The objective of this study was to address this gap via a content analysis of 250 recent software RFPs across commonly implemented software categories. Results identified the most frequently used evaluation criteria and corresponding weights, procurement schedule durations, anticipated length of contract terms, quantity of itemised requirements documented in the owner’s scope, and other pertinent information. Inferential testing found several differences among the different software categories. The findings may be helpful to owner project managers who are tasked with leading their project teams through the early stages of scope development and vendor selection.
... This would lead to a better consumption in the whole developing process. Meanwhile, it should be mentioned that the flexible nature of scope definition in agile makes it difficult or impossible to measure its completeness and quality [6]. ...
User stories play an important role in agile development systems. In this study, a method of summarising user stories is proposed to reuse them in the future. To enhance the results, quality improvement should be made on user stories. It would help developers build better results, and it may also lead to omitting some essential information. To avoid such issues, user stories are duplicated in two exact similar groups, and quality improvement is made on one set while the other set remains unattained. With the help of a modified bag of words and a verb parser, a collection of keywords and key verbs are extracted for both groups. Afterwards, automatic user stories are made, and then an expert improves them. Next, some experts choose between the results and select the better ones. The result is evaluated by applying different experiments on the framework and prototype implementation on 14 data sets of a user story from industry and a fake data set from Duke University. The result showed 97% of micro F ‐measure and 93% of macro F ‐measure, which are promising. These new user stories can be used as the base user stories in future similar projects.
