scholarly journals Product Owner’s Journey to SAFe®—Role Changes in Scaled Agile Framework®

Information ◽  
2021 ◽  
Vol 12 (3) ◽  
pp. 107
Author(s):  
Daniel Remta ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Hierarchical Structures ◽  
Agile Methods ◽  
Original Design ◽  
Top Down ◽  
Registered Trademark ◽  
Role Changes ◽  
Role Description ◽  
Agile Software ◽  
Development Methods

As agile software development methods are spreading through the industry, they are no longer sufficient in their original design. With the increasing adoption by various types and sizes of organizations, these methods are scaled and tailored. The most popular framework for scaling Agile is the Scaled Agile Framework®, registered trademark of Scaled Agile, Inc. Boulder, USA. Some roles originating from the agile methods, such as Product Owner, are part of the framework and are impacted by scaling and tailoring. A Product Owner role is critical to the success of projects in agile environments. This paper aims to describe and discuss the evolution of and changes in Product Owner activities since Agile started to spread in the industry until the current concept of the Product Owner role in the Scaled Agile Framework. By identifying the activities typical of Product Owners outside of the Scaled Agile Framework context and mapping these activities to the Product Owner role description in Scaled Agile Framework, the changes in Product Owner role with respect to time and role specifics in the Scaled Agile Framework are revealed. It was identified that some of the activities previously described for Product Owner are distributed between various roles in the Scaled Agile Framework. In fact, the Product Owner loses the real product ownership in Scaled Agile Framework. The loss of ownership seems connected with the fact that, in the large environments that the Scaled Agile Framework is designed for, it is impossible to cover all required activities by one role using the hierarchical structures with a top-down approach in the Scaled Agile Framework.

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
Agile Methods ◽  
Two Dimensional ◽  
Dimensional Classification ◽  
Agile Software ◽  
Structural Mechanisms ◽  
Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Security Assurance in Agile Software Development Methods

2022 ◽  
pp. 929-946
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Evaluation Framework ◽  
Agile Methods ◽  
Software Projects ◽  
Security Engineering ◽  
Security Incident ◽  
Security Assurance ◽  
Agile Software ◽  
Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Agile Development Methods and Component-Orientation

2011 ◽  
pp. 1-22
Author(s):  
Zoran Stojanovic ◽  
Ajantha Dahanayake ◽  
Henk Sol
Keyword(s):  
Software Development ◽  
Architectural Design ◽  
Development Process ◽  
System Modeling ◽  
Theory And Practice ◽  
Agile Methods ◽  
Agile Development ◽  
Model Driven ◽  
Agile Software ◽  
Development Methods

Agile software development methods have been proposed as the way to address the problem of delivering high-quality software on time under constantly and rapidly changing requirements in business and IT environments. An agile development process is characterized by extensive coding practice, intensive communication between stakeholders, fast iterative cycles, small and flexible teams, and minimal efforts in system modeling and architectural design. This paper presents the state-of-the-art of agile methods and analyzes them along the selected criteria that highlight different aspects of their theory and practice. Certain limitations of agile methods are identified. The chapter presents the component paradigm as a way of balancing traditional (model-driven or plan-driven) and agile development, depending on the project settings. Service-based component concepts applied at the level of modeling, architectural design and development can ensure and strengthen agile development principles and practices, and at the same time introduce necessary agility to more traditional development. By using components, the software development process can easily scale in size, robustness, and the level of details. This provides an effective balance between the requirements for agility in software development and needs for a disciplined, design-driven way of building complex software.

Security Assurance in Agile Software Development Methods

2019 ◽  
pp. 47-68
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Evaluation Framework ◽  
Agile Methods ◽  
Software Projects ◽  
Security Engineering ◽  
Security Incident ◽  
Security Assurance ◽  
Agile Software ◽  
Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Practices to Improve Risk Management in Agile Projects

2019 ◽  
Vol 29 (03) ◽  
pp. 381-399 ◽  
Author(s):  
Breno Gontijo Tavares ◽  
Carlos Eduardo Sanches da Silva ◽  
Adler Diniz de Souza
Keyword(s):  
Risk Management ◽  
Software Development ◽  
Management Practices ◽  
Agile Methods ◽  
Management Effectiveness ◽  
Software Projects ◽  
The Subject ◽  
Specific Activities ◽  
Agile Software ◽  
Development Methods

Risk management contributes to software projects success, but agile software development methods do not offer specific activities to manage risks. Therefore, this study aims to propose a list of risk management practices for agile projects, aiming to increase their chances of success. We analyzed 129 works on agile methods that afforded 127 risk management practices. We categorized and ranked practices using the AHP multi-criteria method with the participation of experts in the subject. The study presents risk management practices for daily meetings, increment, prototype, product backlog and Sprint planning as the most important for the risk management effectiveness. This study identified specific risk management practices for agile methods, not converging with other studies. Results contribute to the risk management improvement in agile projects and, consequently, increase their chances of success.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Exploring the Role of Project Management in the Development of the Academic Agile Software Discourse: A Bibliometric Analysis

2017 ◽  
Vol 48 (1) ◽  
pp. 3-18 ◽  
Author(s):  
Thomas G. Lechler ◽  
Siwen Yang
Keyword(s):  
Project Management ◽  
Software Development ◽  
Bibliometric Analysis ◽  
Agile Methods ◽  
Management Research ◽  
Practical Applications ◽  
Time Period ◽  
Time Periods ◽  
Agile Software

The practical applications of agile methods and their impact on the productivity and efficiency of software development dominate the agile literature. We analyzed 827 academic articles with bibliometric techniques to explore the role project management research played in the development of the academic agile discourse. Bibliometric analyses over two time periods reveal that project management–related topics form a distinct stream of research in the second time period but not in the first. Furthermore, our results reveal that the academic agile discussion has been mainly unidirectional. This situation offers many opportunities for project management researchers to contribute to the agile discourse.

Sign in / Sign up

Export Citation Format

Share Document