scholarly journals The Visualization of ISO/IEC29110 on SCRUM under EPF Composer

Information ◽  
2021 ◽  
Vol 12 (5) ◽  
pp. 190
Author(s):  
Kittitouch Suteeca ◽  
Sakgasit Ramingwong
Keyword(s):  
Software Development ◽  
User Requirements ◽  
Software Companies ◽  
Agile Methodologies ◽  
Process Framework ◽  
User Expectations ◽  
Agile Approach ◽  
Rapid Deployment ◽  
External Consultant

In the midst of an increasingly competitive software industry, very small entities (VSEs) have inevitably faced many challenges. High user expectations, frequent changes of user requirements, and the need for rapid deployment are classic examples of these challenges. Many software companies attempt to implement measures for preventing or solving the aforementioned problems. The use of agile methodologies and the implementation of software development standards are usually perceived to be promising solutions to improve the quality of the software development process. Nevertheless, there are several strong incompatibilities between standards and the Agile approach to software development. For example, the need identified in the standards to create many quality artifacts does not conform to agility philosophies. Since Agile focuses on the working software over the documentation, the use of the Agile with standards can be difficult to implement. Additionally, there has been none guidelines for VSE therefore, an external consultant is usually required. This research analyzes various cases of implementing ISO/IEC29110, a software development standard developed especially for VSEs in Scrum environments. The results of this study provide an Eclipse Process Framework (EPF) for effectively and conveniently implementing this standard in Scrum software development.

Agile Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Software Development Process Standards for Very Small Companies

2019 ◽  
pp. 681-694 ◽  
Author(s):  
Rory V. O'Connor
Keyword(s):  
Software Development ◽  
Pilot Project ◽  
Small Companies ◽  
Small Organizations ◽  
Software Products ◽  
Software Companies ◽  
Project Scheme ◽  
Engineering Standards ◽  
Standards Adoption

For very small software development companies, the quality of their software products is a key to competitive advantage. However, the usage of software engineering standards is extremely low amongst such very small software companies. A primary reason cited by many such companies for this lack of quality standards adoption is the perception that they have been developed for large multi-national software companies and not with small and very small organizations in mind and are therefore not suitable for their specific needs. This chapter describes the design and development of the software process lifecycle standard for very small entities. This chapter presents a unique insight from the perspective of some of the standards authors on the development of the ISO/IEC 29110 standard, including the rationale behind its development and the innovative design of implementation guides to assist very small companies in adopting the standards, as well outlining a pilot project scheme for usage in early trials of this standard.

Software Development Process Standards for Very Small Companies

2018 ◽  
pp. 6927-6938
Author(s):  
Rory V. O'Connor
Keyword(s):  
Software Development ◽  
Pilot Project ◽  
Small Companies ◽  
Small Organizations ◽  
Software Products ◽  
Software Companies ◽  
Project Scheme ◽  
Engineering Standards ◽  
Standards Adoption

For very small software development companies, the quality of their software products is a key to competitive advantage. However, the usage of Software Engineering standards is extremely low amongst such very small software companies. A primary reason cited by many such companies for this lack of quality standards adoption is the perception that they have been developed for large multi-national software companies and not with small and very small organizations in mind and are therefore not suitable for their specific needs. This chapter describes the design and development of the software process lifecycle standard for very small entities ISO/IEC 29110. This chapter presents a unique insight from the perspective of some of the standards authors on the development of the ISO/IEC 29110 standard, including the rationale behind its development and the innovative design of implementation guides to assist very small companies in adopting the standards, as well outlining a pilot project scheme for usage in early trials of this standard.

scholarly journals Effects of Agile adoption on Trust, Knowledge Sharing and Collaboration in IT Organizations

2019 ◽  
Vol 8 (12) ◽  
pp. 2652-2655
Keyword(s):  
Software Development ◽  
Knowledge Sharing ◽  
Positive Impact ◽  
Project Control ◽  
Deep Impact ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
It Organizations ◽  
Reduced Risk

Adoption of Agile methodologies in IT organizations has revolutionized software development. It has improved speed of development, quality of final product, customer satisfaction, project control and reduced risk and wastage. Agile methodology is however not just a process but it is a philosophy that has a deep impact on the behavior and mindset of employees. Current paper attempts to study this impact and deduce whether it has a positive impact on Trust, Knowledge Sharing and Collaboration.

scholarly journals Agile Project Management Tools: A Brief Comprative View

2019 ◽  
Vol 19 (4) ◽  
pp. 17-25
Author(s):  
Deniz Özkan ◽  
Alok Mishra
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Tools ◽  
Efficient Manner ◽  
Team Members ◽  
Agile Methodologies ◽  
Agile Project Management ◽  
Start Up ◽  
Agile Practices

Abstract Agile methodologies are becoming popular in software development. Managers are required to understand project’s progress and product quality without development documents. During Agile practices of the teams and organizations, Agile project management tools are frequently used. The use of such tools leads to achieving speed and efficiency, affects the quality of the software. The quality of final product is mostly related with to project management. Accordingly, the paper provides brief comparative perspective about the popular project management tools for agile projects. 16 popular Agile project management tools have been presented helping agile developers to plan and manage their tasks in an efficient manner. Taiga, Axosoft, Agielan, Planbox are more appropriate for start-up projects. The most twitted and most appreciated tools are reported as Jira, Trello, and VersionOne. SpiraTeam by Inflectra and Pivotal Tracker are other pricing and popular agile tools, providing flexibility to Agile developers and increase collaboration among team members.

Comparative Study on Software Development Methods: Agile vs Scrum

2018 ◽  
Vol 6 (6) ◽  
pp. 165
Author(s):  
Ankita Sharma ◽  
Manav Bali
Keyword(s):  
Software Development ◽  
Comparative Study ◽  
Advantages And Disadvantages ◽  
Software Companies ◽  
Agile Methodologies ◽  
Short Span ◽  
Development Methods ◽  
Minimum Costs ◽  
Software Development Methods

Now a days most of the software companies are able to produce valuable software in a very short span of time with minimum costs and with adjustable environments. For this purpose Agile Methodologies were thus introduced to meet all the requirements of a software development company. In this paper we will discuss the agile technique and SCRUM there advantages and disadvantages. Also we discuss about the dissimilarities and similarities between the new requirements of the software development companies.

Some Method Fragments for Agile Software Development

2009 ◽  
pp. 223-242
Author(s):  
Q. N.N. Tran ◽  
B. Henderson-Sellers ◽  
I. Hawryszkiewycz
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Method Engineering ◽  
Additional Method ◽  
Engineering Approach ◽  
Agile Methodologies ◽  
Process Framework ◽  
Australian Standard ◽  
Agile Software

The use of a situational method engineering approach to create agile methodologies is demonstrated. Although existing method bases are shown to be deficient, we take one of these (that of the OPEN Process Framework) and propose additional method fragments specific to agile methodologies. These are derived from a study of several of the existing agile methods, each fragment being created from the relevant powertype pattern as standardized in the Australian Standard methodology metamodel of AS 4651.

Requirements Specification using User Stories

2011 ◽  
pp. 71-89 ◽  
Author(s):  
V. Monochristou ◽  
M. Vlachopoulou
Keyword(s):  
Software Development ◽  
Interaction Design ◽  
System Development ◽  
Requirements Specification ◽  
Software Requirements ◽  
User Requirements ◽  
Agile Methodologies ◽  
User Stories ◽  
Software Requirements Specification ◽  
Waterfall Model

Collecting and analyzing user requirements is undoubtedly a really complicated and often problematic process in software development projects. There are several approaches, which suggest ways of managing user’s requirements; some of the most well-known are IEEE 830 software requirements specification (SRS), use cases, interaction design scenarios, etc. Many software experts believe the real user requirements emerge during the development phase. By constantly viewing functional sub-systems of the whole system and participating, in fact, in all phases of system development, customers/users can revise their requirements by adding, deleting, or modifying them. However, in order for this to become possible, it is important to adopt a totally different approach than the traditional one (waterfall model approach), concerning not only the management of user’s requirements, but also the entire software development process in general. Agile methodologies represent this different approach since the iterative and incremental way of development they propose includes user requirements revision mechanisms and user active participation throughout the development of the system. The most famous approach concerning requirements specification among the supporters of the agile methodologies is probably user stories. User stories and their main characteristics are thoroughly demonstrated in this chapter. After reading this chapter, the authors hope that the reader may have gained all the basic understanding regarding the use of user stories.

scholarly journals An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

2017 ◽  
Vol 10 (1) ◽  
pp. 75-106 ◽  
Author(s):  
Sergio Galvan-Cruz ◽  
Manuel Mora ◽  
Rory V. O'Connor ◽  
Francisco Acosta ◽  
Francisco Álvarez
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Software Process Improvement ◽  
Agile Methodologies ◽  
Development Processes ◽  
Software Development Methodologies ◽  
Agile Software ◽  
Initial Results

Software Process Improvement efforts (SPI) are pursued by organizations for improving the overall quality of their software development processes. However, very small entities (VSEs) avoid them by the lack of required financial and other organizational resources. In contrast, VSEs use agile software development methodologies (ASDMs), but these ASDMs do not foster adherence to best scholastic practices promoted by SPI. Furthermore, while a new ISO/IEC standard (29110) has been recently released for VSEs, it was not designed taking account the ASDM approaches. Thus, we investigate the extent of adherence of main ASDMs (two industrial and one academic type) with this new standard. Initial results provide evidence on the strong need to enhance the two industrial ASDMs (XP and SCRUM). In contrast, the academic ASDM (UPEDU) fits the standard very well but it is scarcely used by VSEs. Hence, it is concluded that there is a knowledge gap between the praxis with ASDMs and the recommended scholastic software processes like the ISO/IEC 29110 standard for VSEs.

scholarly journals An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

2021 ◽  
pp. 1227-1261
Author(s):  
Sergio Galvan-Cruz ◽  
Manuel Mora ◽  
Rory V. O'Connor ◽  
Francisco Acosta ◽  
Francisco Álvarez
Keyword(s):  
Software Development ◽  
Software Process ◽  
Software Process Improvement ◽  
Management Process ◽  
Agile Methodologies ◽  
Development Processes ◽  
Software Development Methodologies ◽  
Agile Software ◽  
Initial Results

Software Process Improvement efforts (SPI) are pursued by organizations for improving the overall quality of their software development processes. However, very small entities (VSEs) avoid them by the lack of required financial and other organizational resources. In contrast, VSEs use agile software development methodologies (ASDMs), but these ASDMs do not foster adherence to best scholastic practices promoted by SPI. Furthermore, while a new ISO/IEC standard (29110) has been recently released for VSEs, it was not designed taking account the ASDM approaches. Thus, we investigate the extent of adherence of main ASDMs (two industrial and one academic type) with this new standard. Initial results provide evidence on the strong need to enhance the two industrial ASDMs (XP and SCRUM). In contrast, the academic ASDM (UPEDU) fits the standard very well but it is scarcely used by VSEs. Hence, it is concluded that there is a knowledge gap between the praxis with ASDMs and the recommended scholastic software processes like the ISO/IEC 29110 standard for VSEs.

Sign in / Sign up

Export Citation Format

Share Document