Agile Development in Data Warehousing

2012 ◽  
pp. 286-300 ◽  
Author(s):  
Nayem Rahman ◽  
Dale Rutz ◽  
Shameem Akhter
Keyword(s):  
Business Intelligence ◽  
Data Warehousing ◽  
Agile Development ◽  
Successful Implementation ◽  
Design Development ◽  
Frequent Change ◽  
Development Teams ◽  
Agile Approach ◽  
Waterfall Model ◽  
Business Requirements

Traditional data warehouse projects follow a waterfall development model in which the project goes through distinct phases such as requirements gathering, design, development, testing, deployment, and stabilization. However, both business requirements and technology are complex in nature and the waterfall model can take six to nine months to fully implement a solution; by then business as well as technology has often changed considerably. The result is disappointed stakeholders and frustrated development teams. Agile development implements projects in an iterative fashion. Also known as the sixty percent solution, the agile approach seeks to deliver more than half of the user requirements in the initial release, with refinements coming in a series of subsequent releases which are scheduled at regular intervals. An agile data warehousing approach greatly increases the likelihood of successful implementation on time and within budget. This article discusses agile development methodologies in data warehousing and business intelligence, implications of the agile methodology, managing changes in data warehouses given frequent change in business intelligence (BI) requirements, and demonstrates the impact of agility on the business.

Agile Development in Data Warehousing

2011 ◽  
Vol 2 (3) ◽  
pp. 64-77 ◽  
Author(s):  
Nayem Rahman ◽  
Dale Rutz ◽  
Shameem Akhter
Keyword(s):  
Business Intelligence ◽  
Data Warehousing ◽  
Agile Development ◽  
Successful Implementation ◽  
Design Development ◽  
Frequent Change ◽  
Development Teams ◽  
Waterfall Model ◽  
Business Requirements ◽  
The Impact

Traditional data warehouse projects follow a waterfall development model in which the project goes through distinct phases such as requirements gathering, design, development, testing, deployment, and stabilization. However, both business requirements and technology are complex in nature and the waterfall model can take six to nine months to fully implement a solution; by then business as well as technology has often changed considerably. The result is disappointed stakeholders and frustrated development teams. Agile development implements projects in an iterative fashion. Also known as the sixty percent solution, the agile approach seeks to deliver more than half of the user requirements in the initial release, with refinements coming in a series of subsequent releases which are scheduled at regular intervals. An agile data warehousing approach greatly increases the likelihood of successful implementation on time and within budget. This article discusses agile development methodologies in data warehousing and business intelligence, implications of the agile methodology, managing changes in data warehouses given frequent change in business intelligence (BI) requirements, and demonstrates the impact of agility on the business.

Adapting Agile Practices for Data Warehousing, Business Intelligence, and Analytics

2017 ◽  
Vol 28 (4) ◽  
pp. 1-23 ◽  
Author(s):  
Dinesh Batra
Keyword(s):  
Project Management ◽  
Business Intelligence ◽  
Management Practices ◽  
Data Warehousing ◽  
Agile Methods ◽  
Agile Development ◽  
Theory Approach ◽  
Structured Interviews ◽  
Agile Practices ◽  
Top Management Commitment

Business surveys indicate that fewer than 30% of data warehousing and business intelligence (DW/BI) projects meet the stated goals of the budget, schedule, and quality. Agile methods have been suggested as a possible solution, but because of the large size of the typical DW/BI project, it may be difficult to apply the agile values and principles. In this article, the following research questions are raised: Can agile practices be adapted for DW/BI development? What factors influence agile DW/BI development? Six semi-structured interviews were conducted using a questionnaire. The interview transcripts were coded using the grounded theory approach. Eight categories emerged from the analysis: business value, project management, agile development, shared understanding, technological capability, top management commitment, complexity, and organizational culture. Based on the categories, a research framework is proposed. The findings reveal that agile methods are suited for only certain aspects of DW/BI projects and need to be augmented with project management practices.

scholarly journals Scrum: An Agile Software Development Process and Metrics

2019 ◽  
Vol 7 (1) ◽  
Author(s):  
Rajani Dixit ◽  
Brij Bhushan
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Development ◽  
Software Development Process ◽  
Team Members ◽  
Development Team ◽  
Agile Approach ◽  
Waterfall Model ◽  
Agile Software

In a traditional software development process such as the Waterfall Model, works best in a stable environment. But, it is not flexible when it comes to change. There is a gap in the interaction between the users and the development team which leads to incomplete and misunderstood specification. Because of this, the end product is sometimes a surprise to users and this gap accelerates incorrect development of the software product. Once requirements are frozen there is no scope of accepting changes. There is a need for a framework which holds the solution for all these situations. With this premise, the agile development methodology came into existence. Scrum, an agile approach supports continuous collaboration among the customer, team members, and other stakeholders. Its time-boxed approach and continuous feedback from the product owner ensures the development of working product with essential features at all the time. This paper explains the agile software development approach, its proclamation and different frameworks of agile approach. Further illustrate most widely used framework: Scrum. This research paper covers the implementation and application of Scrum. It focuses on why Scrum is preferred over the Waterfall Model with the help of some survey results and later a discussion on some Scrum Metrics which will be helpful and accounting for the best Scrum Practices in achieving goals set by the software development team, the product owner and the customers. The outcome of this study shows that Scrum Metrics is critical and highly valuable for successful product development. The quantitative insight that these metrics provide for the Scrum Team, Product Owner and Stakeholders is necessary for achieving strong project dynamics and optimal results.

Managing User-Centered Design Activities in Distributed Agile Development

2021 ◽  
Author(s):  
Sultan Alyahya ◽  
Ohoud Almughram
Keyword(s):  
Participatory Design ◽  
Agile Development ◽  
Design Teams ◽  
User Centered Design ◽  
Management Tools ◽  
Daily Work ◽  
Development Teams ◽  
Design Activities ◽  
Computer Based ◽  
User Centered

Abstract The integration of user-centered design (UCD) activities into agile information systems development has become more popular recently. Despite the fact that there are many ways the merging of UCD activities into agile development can be carried out, it has been widely recognized that coordinating design activities with development activities is one of the most common problems, especially in distributed environments where designers, developers and users are spread over several sites. The main approach to coordinate UCD activities with distributed agile development is the use of informal methods (e.g. communication through using video conference tools). In addition to the temporal, geographical and socio-cultural barriers associated with this type of methods, a major limitation is a lack of awareness of how UCD activities and development activities affect each other. Furthermore, some agile project management tools are integrated with design platforms but fail to provide the necessary coordination that helps team members understand how the design and development activities affect their daily work. This research aims to support the effective management of integrating UCD activities into distributed agile development by (i) identifying the key activity dependencies between UX design teams and development teams during distributed UCD/agile development and (ii) designing a computer-based system to provide coordination support through managing these activity dependencies. In order to achieve these objectives, two case studies are carried out. Our findings revealed 10 main dependencies between UCD design teams and development teams as shown by six types of activity. In addition, the participatory design approach shows that developing a computer-based system to manage seven of these selected dependencies is achievable.

scholarly journals ZonaTIC: Sitio web para la divulgación de la ciencia de las TIC en pro de la inclusión digital

2019 ◽  
pp. 14-18
Author(s):  
Apolinar Trejo-Cuevas ◽  
Gerardo Parra-Rodríguez ◽  
María Teresa Díaz-Robledo ◽  
Javier Jesús Torres-Yáñez
Keyword(s):  
Information And Communication Technologies ◽  
Web Applications ◽  
Teaching Strategy ◽  
Project Based Learning ◽  
Design Development ◽  
Digital Inclusion ◽  
Analysis And Design ◽  
Information And Communication ◽  
Waterfall Model ◽  
The University

Objective. Implement a website that allows the outreach of the science of Information and Communication Technologies to the staff of the university community of the UTNG to facilitate digital inclusion, taking advantage of the current infrastructure that the university has, as well as its human capital. Methodology. The adopted development model was a concurrent model: For the Frontend development the spiral model was used, which facilitates its design through the stages of prototyping, analysis and design. On the other hand, for the development of the Backend, the waterfall model was used, given the nature of the project, where the requirements are pre-established and with few changes. The phases of this model are: (Requirements. Survey of requirements, Design. Development of the database and class diagrams, Implementation Coding, Check. Tests, Maintenance. Correct errors in functionality) Contribution. Implementation of project-based learning (PBL) as a motivational teaching strategy in the development of web applications. Use of robust development tools used today by software factories, such as: Java, Spring, HTML5, CSS3, and Apache Maven; all this under a Model View Controller architecture.

scholarly journals FEATURES AND PROSPECTS OF AGILE APPLICATION IN THE ACTIVITY OF PUBLIC AUTHORITIES IN TERMS OF UKRAINE’S PUBLIC ADMINISTRATION TRANSFORMATIONS

2020 ◽  
pp. 139-151
Author(s):  
H. Mishenina ◽  
D. Pavlenko
Keyword(s):  
Public Administration ◽  
Public Management ◽  
Agile Development ◽  
Electronic Interaction ◽  
Public Authorities ◽  
Economic Relations ◽  
The Public ◽  
Agile Approach ◽  
The Public Sphere ◽  
Conceptual Foundations

The article is devoted to the study of conceptual foundations of the Agile management, the need and prospects for implementing its methods in the sphere of public authorities. Systemic shortcomings of traditional governance in public authorities hinder the effective, prompt solution of important tasks of local socio-economic development and the country as a whole, and do not respond quickly to changes in the external environment. Now, during the period of active transformation of social, economic, political systems caused by the COVID 19 pandemic, the speed and quality of digitalization of all processes play a significant role. In the future, such changes will only deepen, covering all areas of socio-economic relations. Emphasis is placed on the processes of reforming the sphere of public administration and local self-government, in particular in terms of digitalization of public administration elements. The analysis of preconditions of active use of flexible methods of management in the public sphere is carried out. The introduction of the Agile technologies to project-oriented structures of public authorities is argued. The essence and practical aspects of effective application of Scrum methodology are considered, and the scheme of its introduction to work of bodies of regional management and local government is offered. The article analyzes the experience of practical application of the Agile approach in the public sector in some countries of the world (such as Great Britain, USA, Australia) and defines the basis for further «State Agile» development in Ukraine. The relevance of further the Agile approach popularization in public administration is confirmed by the need for changes in public-management relations, and prospects for the public digitalization in the following areas such as: development and implementation of a strategy for digital transformation of regions; implementations of digital solutions for increasing the public authorities' efficiency; ensuring electronic interaction between national, regional and local registries; digital democracy development, and so on.

Towards Private-Public Research Partnerships Combining Rigor and Relevance in DWH/BI Research

2012 ◽  
pp. 163-175
Author(s):  
Anne Cleven ◽  
Robert Winter ◽  
Felix Wortmann
Keyword(s):  
Information Systems ◽  
Business Intelligence ◽  
Data Warehousing ◽  
Academic Discipline ◽  
Public Research ◽  
Research Partnerships ◽  
Close Link ◽  
Research And Practice ◽  
Two Sides

Business intelligence (BI) and data warehousing (DWH) research represent two increasingly popular, but still emerging fields in the information systems (IS) academic discipline. As such, they raise two substantial questions: Firstly, “how rigorous, i.e., fundamental, constituent, and explanatory, is DWH BI research?” and, secondly, “how relevant, i.e., useful and purposeful, is this research to practitioners?” In this article, the authors uphold the position that relevance and rigor are by no means dichotomous, but two sides of the same coin. Naturally, this requires well-defined approaches and guidelines—for scholarship in general and DWH/BI research in particular. Therefore, this paper proposes the competence center (CC) approach—a private-public partnership between academia and practice. The authors illustrate how the CC approach can be applied within the field of DWH/BI and suggest that a close link between research and practice supports both enhancing relevance to practice and strengthening rigor of research.

Sign in / Sign up

Export Citation Format

Share Document