scholarly journals Enhancing research informatics core user satisfaction through agile practices

JAMIA Open ◽  
2021 ◽  
Vol 4 (4) ◽  
Author(s):  
Andrew R Post ◽  
Jared Luther ◽  
J Maxwell Loveless ◽  
Melanie Ward ◽  
Shirleen Hewitt
Keyword(s):  
Best Practices ◽  
Software Development ◽  
User Satisfaction ◽  
Best Practice ◽  
Turnaround Time ◽  
Agile Software Development ◽  
User Engagement ◽  
Full Time ◽  
Agile Practices ◽  
Agile Software

Abstract Objective The Huntsman Cancer Institute Research Informatics Shared Resource (RISR), a software and database development core facility, sought to address a lack of published operational best practices for research informatics cores. It aimed to use those insights to enhance effectiveness after an increase in team size from 20 to 31 full-time equivalents coincided with a reduction in user satisfaction. Materials and Methods RISR migrated from a water-scrum-fall model of software development to agile software development practices, which emphasize iteration and collaboration. RISR’s agile implementation emphasizes the product owner role, which is responsible for user engagement and may be particularly valuable in software development that requires close engagement with users like in science. Results All RISR’s software development teams implemented agile practices in early 2020. All project teams are led by a product owner who serves as the voice of the user on the development team. Annual user survey scores for service quality and turnaround time recorded 9 months after implementation increased by 17% and 11%, respectively. Discussion RISR is illustrative of the increasing size of research informatics cores and the need to identify best practices for maintaining high effectiveness. Agile practices may address concerns about the fit of software engineering practices in science. The study had one time point after implementing agile practices and one site, limiting its generalizability. Conclusions Agile software development may substantially increase a research informatics core facility’s effectiveness and should be studied further as a potential best practice for how such cores are operated.

Quality Assurance in Agile Software Development

2014 ◽  
pp. 155-176 ◽  
Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Best Practices ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Software Life Cycle ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Agile Software

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.

Usability Integration in Agile Development Processes: A Practice-Oriented Best Practice Approach

i-com ◽  
2015 ◽  
Vol 14 (2) ◽  
Author(s):  
Hartmut Schmitt ◽  
Dominik Magin ◽  
Andreas Maier ◽  
Richard Wacker ◽  
Josh Wang
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Best Practice ◽  
Agile Software Development ◽  
Agile Development ◽  
Ministry Of Education ◽  
Team Members ◽  
Ui Design ◽  
Practice Approach ◽  
Agile Software

AbstractSmall and medium-sized enterprises (SMEs) increasingly rely on agile software development. However, the majority of established usability methods have been developed with traditional software engineering principles in mind. So, one might assume that these methods and tools might not be applicable to agile development projects. In this paper, a possible approach to systematically adapting traditional usability methods to application in agile projects is introduced and documented as best practices. These best practices can be quickly and dynamically employed by agile development team members and can thus contribute to higher quality of software development outputs. The approach described in this paper was developed in the context of a German research project funded by the German Federal Ministry of Education and Research (BMBF) and conducted by one research institute and three software-developing enterprises and will be evaluated throughout the further course of the project. For this purpose, a number of best practices have been adapted to the context of agile software development and described in detail in order to allow inexperienced software developers of small and medium-sized enterprises to successfully apply these best practices. As two examples of these best practices, we illustrate the best practices ‘Contextual Inquiry’ and ‘Template-Based UI Design’ in this paper.

Quality Assurance in Agile Software Development

2018 ◽  
pp. 837-859
Author(s):  
Iwona Dubielewicz ◽  
Bogumiła Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Best Practices ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Software Life Cycle ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Agile Software

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.

Conceptualizing open agile software development life cycle (OASDLC) model

2015 ◽  
Vol 32 (3) ◽  
pp. 214-235 ◽  
Author(s):  
Subhas C. Misra ◽  
Virender Singh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Conceptual Model ◽  
Best Practice ◽  
Agile Software Development ◽  
Software Project ◽  
Content Type ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Agile Software

Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

scholarly journals Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective

Electronics ◽  
2021 ◽  
Vol 10 (19) ◽  
pp. 2341
Author(s):  
Rashid Ali Khan ◽  
Muhammad Faisal Abrar ◽  
Samad Baseer ◽  
Muhammad Faran Majeed ◽  
Muhammad Usman ◽  
...  
Keyword(s):  
Scale Development ◽  
Software Development ◽  
User Satisfaction ◽  
Large Scale ◽  
Low Cost ◽  
Rapid Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Small Scale ◽  
Agile Software

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

Under Pressure

2018 ◽  
Vol 49 (6) ◽  
pp. 78-102 ◽  
Author(s):  
Kim E. van Oorschot ◽  
Kishore Sengupta ◽  
Luk N. Van Wassenhove
Keyword(s):  
Software Development ◽  
System Dynamics ◽  
Poor Performance ◽  
Agile Software Development ◽  
Project Teams ◽  
Dynamics Simulation ◽  
Software Projects ◽  
Sequential Development ◽  
Agile Practices ◽  
Agile Software

The iterative cycles used in agile software development create a series of deadlines for project teams. We investigate the optimal iteration length under behavioral conditions for agile software projects. Based on system dynamics simulation, we argue that both very long (as in sequential development) and very short (monthly) iterative cycles create huge and disruptive fluctuations in schedule pressure experienced by the team. These lead to poor performance in terms of quality, as well as costs and time compared with optimal iterative cycles of two to three months. The monthly cycles used in many agile practices might be too short to ensure optimal performance.

scholarly journals Projetando a Usabilidade e a Experiência do Usuário com a Técnica UXUG-AP: um Estudo Exploratório

2020 ◽  
Author(s):  
Aline Sousa ◽  
Natasha Valentim
Keyword(s):  
Software Development ◽  
Qualitative Analysis ◽  
User Experience ◽  
User Satisfaction ◽  
Exploratory Study ◽  
Development Process ◽  
Agile Software Development ◽  
User Perception ◽  
Agile Software ◽  
Perception Analysis

Be different and distinguish itself among the technologies is intrinsic to the current agile software development. However, we still found usability and user experience (UX) defects generated by the development process, making the quality and user satisfaction unsatisfactory. Therefore, this paper presents a technique that supports the usability and UX design in agile projects, called User Experience and Usability Guidelines for Agile Project (UXUG-AP). Besides, this paper presents a qualitative analysis and user perception analysis obtained through an exploratory study about the UXUG-AP technique. The results show that the technique is considered easy to use and useful.

Coordination artifacts in Agile Software Development

2020 ◽  
Vol 30 (2) ◽  
pp. 100288 ◽  
Author(s):  
Anna Zaitsev ◽  
Uri Gal ◽  
Barney Tan
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Software
Sign in / Sign up

Export Citation Format

Share Document