What the iteration chapters will look like

In the interest of showing what an Agile process might look like as a system is developed under it, the development of hms_sys will be broken down into several iterations. Each iteration, with a single, high-level goal, covers one or more chapters, and is concerned with a common set of Stories. Of the agile methodologies discussed in Chapter 4, Methodologies, Paradigms, and Practices, these chapters are closer to being a Kanban approach than anything else, since the number and total sizes of stories being completed in each iteration vary significantly between iterations. In a Scrum setting, these iterations would be time-constrained, broken out into time-limited chunks – that is, each iteration would be planned to last for some specific length of time. The following chapters and their corresponding iterations are goal-oriented instead, with each intended to achieve some milestone of system functionality. In that respect, they are also close to following a Feature-Driven Development model.

Each iteration will address the same five items:

• Iteration goals
• Assembly of stories and tasks:
  • Requirement analysis and definition activities from the SDLC model, as/if needed
  • System architecture and design activities, also from the SDLC model, as/if needed
• Writing and testing the code.
• System integration, testing, and acceptance.
• Post-development considerations and impact:
  • Implementation/installation/distribution
  • Operations/use and maintenance
  • Decommissioning