Framework Study for Agile Software Development Via Scrum and Kanban

2020 ◽  
Vol 17 (04) ◽  
pp. 2030002
Author(s):  
Wael Zayat ◽  
Ozlem Senvar
Keyword(s):  
Visual Signals ◽  
Agile Methodologies ◽  
Project Environment ◽  
Complex Projects ◽  
Development Teams ◽  
Project Complexity ◽  
Output Factors ◽  
System Improvement ◽  
Agile Software ◽  
Work Size

This paper provides a systematic comparison between two well-known Agile methodologies: Scrum, which is a framework of doing projects by allocating tasks into small stages called sprints, and Kanban, which is a scheduling system to manage the flow of work by means of visual signals. In this regard, both methodologies were reviewed to explore similarities and differences between them. Then, a focus group survey was performed to specify the preferable methodology for product development according to various parameters in the project environment including project complexity, level of uncertainty, and work size with consideration of output factors like quality, productivity, and delivery. Results show the flexibility of both methodologies in approaching Agile objectives, where Scrum emphasizes on the corporation of the customer and development teams with a focus on particular skills such as planning, organization, presentation, and reviewing which makes it ideal for new and complex projects where a regular involvement of the customer is required, whereas Kanban is more operative in continuous-flow environments with a steady approach toward a system improvement.

Empirically validating five propositions regarding 3D visualizations for subsurface utility projects

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Mechiel van Manen ◽  
Léon olde Scholtenhuis ◽  
Hans Voordijk
Keyword(s):  
Construction Projects ◽  
3D Visualization ◽  
Three Dimensional ◽  
Urban Environments ◽  
Content Type ◽  
Complexity Level ◽  
Daily Work ◽  
Complex Projects ◽  
Project Complexity ◽  
Multiple Case

PurposeThis study aims to empirically validate five propositions about the benefits of three-dimensional (3D) visualizations for the management of subsurface utility projects. Specifically, the authors validate whether benefits from 3D in the literature of building construction project management also apply to subsurface utility projects and map them using a taxonomy of project complexity levels.Design/methodology/approachA multiple case study of three utility construction projects was carried out during which the first author was involved in the daily work practices at a utility contractor. 3D visualizations of existing project models were developed, and design and construction meetings were conducted. Practitioners' interactions with and reflections on these 3D visualizations were noted. Observational data from the three project types were matched with the five propositions to determine where benefits of 3D visualizations manifested themselves.FindingsPractitioners found that 3D visualizations had most merit in crowded urban environments when constructing rigid pipelines. All propositions were validated and evaluated as beneficial in subsurface utility projects of complexity level C3. It is shown that in urban projects with rigid pipelines (project with the highest complexity level), 3D visualization prevents misunderstanding or misinterpretations and increases efficiency of coordination. It is recommended to implement 3D visualization approaches in such complex projectsOriginality/valueThere is only limited evidence on the value 3D visualizations in managing utility projects. This study contributes rich empirical evidence on this value based on a six-month observation period at a subsurface contractor. Their merit was assessed by associating 3D approaches with project complexity levels, which may help utility contractors in strategically implementing 3D applications.

Using Wiki for Managing Knowledge in Agile Software Development

2016 ◽  
pp. 397-423
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Software Development ◽  
Software System ◽  
Web Environment ◽  
The Past ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile Software

The movement towards agility is one of the most significant changes in industrial software engineering over the past decade. In the practice of agile methodologies, there are different types of knowledge that is created, communicated, and consumed. For the benefit of the stakeholders involved, there is a pressing need to manage this knowledge, both during development and beyond deployment of a software system. This chapter proposes a framework comprising related conceptual models as means for understanding the use of Wiki for managing knowledge in agile software development. In doing so, Wiki is considered beyond that of a technology or a tool, as a facilitator of knowledge, and placed in a larger context of the Social Web environment. For the sake of practicality, a number of illustrative examples are given, and implications of deploying a Wiki are highlighted.

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.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Agile Software Engineering

2010 ◽  
pp. 28-37
Author(s):  
Ernest Mnkandla
Keyword(s):  
Software Development ◽  
Production Process ◽  
Software Products ◽  
Agile Methodologies ◽  
Software Productivity ◽  
Software Production ◽  
Agile Software Engineering ◽  
Development Approach ◽  
Agile Software ◽  
Traditional Approaches

This chapter aims to reveal agile techniques that have been applied to software development and have resulted in meaningful improvements in software productivity. Available literature generally state some claims on the gains associated with the use of particular agile methodologies in software development. What lacks however, is a comprehensive analysis of how the application of agile techniques as a family will lead to improvement in software productivity. This chapter therefore provides such details. Software productivity techniques provide ways of measuring three things in order to determine the productivity of software; software products, software production processes and structures, and software production setting. Agile methodologies improve software productivity by focusing on the software production process and structures. The fundamental concern of this chapter is to show that agile methodologies measure the production process activities in a different but effective way from the more traditional approaches. For example, time-to-market is reduced by use of an iterative incremental development approach.

Understanding Agile Software, Extreme Programming, and Agile Modeling

2011 ◽  
pp. 33-53
Author(s):  
John Erickson ◽  
Kalle Lyytinen ◽  
Keng Siau
Keyword(s):  
Development Process ◽  
Applied Research ◽  
Systems Development ◽  
Extreme Programming ◽  
Development Projects ◽  
Failure Rates ◽  
Agile Methodologies ◽  
The Many ◽  
Agile Software

Failure rates for systems development projects are estimated to approach 50% (Hirsch, 2002). In such an environment, a growing number of developers propose the use of so-called agile methodologies as one means of improving the systems developed while simultaneously decreasing failure rates. Agile proponents insist that adherence to The Agile Manifesto will improve the entire systems development process. This chapter begins by describing some of the agile methodologies, follows that with an overview of current research in the area, and closes with thoughts on possibilities for future applied research into the agile methodologies that could provide evidence supporting or disputing the many claims for success emerging from the field.

Towards the Development of a Holistic Framework of Project Complexity

2019 ◽  
Vol 8 (2) ◽  
pp. 1-17
Author(s):  
Saleem Gul
Keyword(s):  
Literature Review ◽  
Chaotic Systems ◽  
Review Process ◽  
Schema Theory ◽  
View Point ◽  
Top Down ◽  
Complex Projects ◽  
Project Complexity ◽  
Research Students

Project complexity proves to be a difficult concept to grasp, especially for those new to the topic. This article provides a rapid yet thorough review of the concepts of complexity for those research students, researchers, or project professionals who may be interested in working with or studying complex projects. This article is developed using a traditional literature review process and uses a funneled or top-down approach to present the ontological view point of complexity. The article first discusses complexity in general and then moves on differentiate between simple, complicated, complex, and chaotic systems. The discussion then focuses on complexity in projects, from where the perspective of ‘complexity of' projects and ‘complexity in' projects. The article concludes by presenting an extended and deeper framework of complexity that amalgamates previously known thoughts on project complexity, uncertainty, and schema theory.

Sign in / Sign up

Export Citation Format

Share Document