Write some applications of iterative strategy?
Answers
Answer:
Ralph Hughes MA, PMP, CSM, in Agile Data Warehousing for the Enterprise, 2016
Summary
The outline of the several methods in Chapters 2 and 3 reveals that the subject of iterative application development methods represents a tremendous amount of material to learn. Given that this large subject cannot be mastered all at once, EDW team leaders should view their agile transition as an extended journey. A company may adopt a particular agile method with the belief that it will suffice for its programming needs, but if it is like most other organizations, its developers will want to evolve that starter method as they learn more about which iterative techniques work and which ones fail in their particular culture, industry, and time point. Accordingly, an organization’s software development method must start and grow in much the same way that applications must evolve: iteratively with lots of feedback. Not surprisingly, we can apply agile principles creating an agile software development method, namely take baby steps, iterate, work with just-in-time requirements, hold retrospectives, and steadily improve.
This incremental approach to building a method, to be applied to the world of data management and analytics, is the theme of this book. The Scrum/XP hybrid method presented in Chapters 2 and 3 is a fantastic place to start building a method for DW/BI. Once a company has mastered the art of incremental programming, however, the project team or program planners will find themselves challenged by notions involving risk, requirements, data architecture, quality, and scaling. The values and practices of the two additional, incremental delivery methods reviewed in this chapter, namely Kanban and RUP, have answers for these challenges. Their elements can be added into the development approach of new agile teams bit by bit as they are needed, bringing them up to world-class performance levels in a manner consistent with agile’s values of self-organization and minimal wasted effort.
Iterative strategy is a way of breaking down the software development of a large application into smaller chunks.With each iteration, additional features can be designed, developed and tested until there is a fully functional software application ready to be deployed to customers.