scholarly journals Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

2015 ◽  
Vol 3 (1) ◽  
Author(s):  
Adriana Iglesias ◽  
Acellys Messino ◽  
Patty Pedroza ◽  
Ricardo Llanos
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Process Management ◽  
Model Development ◽  
Agile Development ◽  
Total Quality ◽  
Model Quality ◽  
Development And Management ◽  
Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

Total quality approach to PACS software development and management

1994 ◽  
Author(s):  
Daniel J. Valentino ◽  
Ricky K. Taira ◽  
Lu J. Huang ◽  
Donna M. Marciano ◽  
William A. Manzo ◽  
...  
Keyword(s):  
Software Development ◽  
Total Quality ◽  
Development And Management ◽  
Quality Approach

Agility in Software Development and Project Value

2022 ◽  
pp. 356-376
Author(s):  
VenuGopal Balijepally ◽  
Gerald DeHondt ◽  
Vijayan Sugumaran ◽  
Sridhar Nerur
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Survey Data ◽  
Theoretical Perspective ◽  
Agile Development ◽  
Software Teams ◽  
What Works ◽  
The Individual ◽  
Development Methods ◽  
Over Time

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

scholarly journals Best Practices In Operations Executive Information Systems Software Development And Implementation

2005 ◽  
Vol 9 (2) ◽  
pp. 13-22
Author(s):  
Tom Bramorski
Keyword(s):  
Information Systems ◽  
Best Practices ◽  
Software Development ◽  
Executive Information Systems ◽  
Software Products ◽  
Software Companies ◽  
Current Trends ◽  
Operational Capabilities ◽  
Systems Software ◽  
Development And Management

In this paper we identify best industry practices and current trends in the development and management of software products. We discuss the strategic importance of developing appropriate operational capabilities that are prerequisites for achieving marketing success. We illustrate these concepts with examples from software companies to highlight how they achieved the desired balance between market demands and operational resources. Finally, we highlight the benefits these companies had derived from such an alignment.

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.

Best Practices on Software Development and Management Process for the Republic of Korea Army Information System

2020 ◽  
Vol 47 (10) ◽  
pp. 911-925
Author(s):  
Bo Kyung Park ◽  
Chae Yun Seo ◽  
Ki Du Kim ◽  
Jong Hoon Lee ◽  
R.Young Chul Kim
Keyword(s):  
Information System ◽  
Best Practices ◽  
Software Development ◽  
Republic Of Korea ◽  
Management Process ◽  
The Republic ◽  
Development And Management

Equipment Reliability: When Utility Meets Manufacturing

2008 ◽  
Author(s):  
John Eglin ◽  
Joel Woodcock
Keyword(s):  
Best Practices ◽  
Continuous Improvement ◽  
Management Strategy ◽  
Nuclear Power ◽  
Lessons Learned ◽  
Nuclear Industry ◽  
Plant Management ◽  
Equipment Management ◽  
Total Quality ◽  
Equipment Reliability

In a world striving for continuous improvement, the utility and manufacturing industries appear to have taken different paths to success. But are they the same and can we learn from them to take a revolutionary step towards manufacturing excellence for Westinghouse Nuclear Fuel? The safety critical environment that is the hallmark of the nuclear industry has led the Institute of Nuclear Power Operations (INPO) to develop a rigorous and disciplined approach to equipment reliability that is repeated across the nuclear generation industry. This is manifested in well documented processes and procedures in response to the heavily audited power generation segment. INPO’s Equipment Reliability guideline, AP-913, is a top down methodology that captures equipment history and best practices to tie together activities throughout a station to improve reliability. Manufacturing however is breeding a culture of continuous improvement, or “kaizens”, where “Lean” and “Total Productive Maintenance” (TPM) tools and techniques drive a multiplicity of incremental improvements. The manufacturing concepts and approaches of Lean and TPM were developed originally in Japan by such companies as Toyota and Motorola and formalized by the Japan Institute of Plant Management as an equipment management strategy, which was designed to support the Total Quality Management strategy. Lean and TPM are fostered by professional societies and are well described in a body of literature with decades of experience. Since this paper provides a cross-discipline comparison in a primarily nuclear applications conference, introductory material for the TPM methodology is referenced, while only overview concepts are described herein. It is hoped that this will spur the reader to develop a more complete understanding of TPM, to further integrate these applications in both industries. This paper provides an initial overview of how Westinghouse Fuel Manufacturing is developing an equipment reliability programme that is exploiting the best practices of the AP-913 integrated processes with the strong continuous improvement tool set of manufacturing. We have just begun to roll-out the new processes and guidelines. In future papers, more detailed comparisons and lessons learned from implementation will be described.

In Pursuit of Continuous Improvement

2016 ◽  
Vol 5 (1) ◽  
pp. 34-56
Author(s):  
Marco Liberato
Keyword(s):  
Information Technology ◽  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Quality Standards ◽  
High Quality ◽  
Software Company ◽  
Information Technology Services ◽  
Technology Services ◽  
Development Processes

Companies focus on software development in order to survive in a highly competitive world. They not only need to keep up to date with the changes that are occurring in their environment, but they also need to assure the effectiveness of their processes. One way to do that is pursuing high quality standards by continuously improving the development processes. This article describes the decision of a software company specialized in information technology services for banking to pursue the improvement of its software development processes through CMMI ML3 certification and LEAN implementation. Throughout the article is shown the reasons why it was decided to take this enhancement step, the tools used to support the implementation, and the obtained results. The intent is to show that continuous improvement is not an immediate result of a certification or best practices implementation but the decision to make improvement as company's DNA.

scholarly journals IGSTK: Development Process and Project Management Best Practices for an Open Source Software Toolkit for Image-Guided Surgery Applications

2005 ◽  
Author(s):  
Kevin Gary ◽  
Brian Blake ◽  
Stephen Aylward ◽  
Julien Jomier ◽  
David Gobbi ◽  
...  
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Open Source ◽  
Development Process ◽  
Development Project ◽  
Agile Development ◽  
Image Guided Surgery ◽  
Guided Surgery ◽  
Image Guided ◽  
Concurrent Development

Open source technologies are increasing in popularity for software development. Many open source projects rely on skilled development teams whose members are distributed throughout the world. Often, agile development methods are employed by these teams, as the focus is on concurrent development and fast production over requirements management and quality assurance. The image-guided surgery toolkit (IGSTK) is an open source development project that relies on the collaboration of a skilled and distributed development team, yet addresses a domain that demands managing requirements as well as implementing a high degree of robustness and addressing safety concerns. Due to this unique cross-section of open source technology and the surgical domain, the IGSTK team has developed a set of best practices and requirements techniques to augment commonly applied agile methods. This paper presents the lessons we have learned as we have engaged in the software development process.

Agility in Software Development and Project Value

2017 ◽  
Vol 28 (4) ◽  
pp. 40-59 ◽  
Author(s):  
VenuGopal Balijepally ◽  
Gerald DeHondt ◽  
Vijayan Sugumaran ◽  
Sridhar Nerur
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Survey Data ◽  
Theoretical Perspective ◽  
Agile Development ◽  
Software Teams ◽  
What Works ◽  
The Individual ◽  
Development Methods ◽  
Over Time

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

scholarly journals Análise sobre os conceitos e práticas de Gestão por Processos: revisão sistemática e bibliometria

2015 ◽  
Vol 22 (1) ◽  
pp. 164-180 ◽  
Author(s):  
Diego Rodrigues Iritani ◽  
Sandra Naomi Morioka ◽  
Marly Monteiro de Carvalho ◽  
Aldo Roberto Ometto
Keyword(s):  
Quality Management ◽  
Total Quality Management ◽  
Business Process ◽  
Business Process Management ◽  
Process Management ◽  
Total Quality ◽  
Business Excellence

Este artigo tem como objetivo analisar a teoria sobre Gestão por Processos de Negócio (BPM - Business Process Management). Para isso foi realizada uma revisão bibliográfica sistemática e foram utilizadas técnicas de análise de publicações, citações e de bibliometria. Os resultados mostram a multidisciplinaridade de BPM, como as diferentes áreas de pesquisa compreendem o tema e como praticam essa abordagem. Dentre os periódicos relevantes para o tema, destacaram-se o Business Process Managament Journal, Knowlegde and Process Managemente Total Quality Management & Business Excellence. Dentre as abordagens de aplicação foi possível verificar que existem três tipos adotados pelo estudo e ao todo foram identificadas oito práticas de BPM. As redes de bibliometria mostraram a existência de agrupamentos bibliométricos que pouco interagem, e a relação de BPM com as abordagens de gestão da qualidade e reengenharia. Apesar do aumento de publicações na área, o que mostra a relevância do tema, as publicações tendem a seguir escolas distintas e que ainda atuam de forma isolada na área de BPM.

Sign in / Sign up

Export Citation Format

Share Document