program selection system

Delivering value early and often is a well established agile practice. But rushing directly into Iteration 0 development can lead to tunnel vision (thereby building the wrong product) or unnecessary (thereby wasteful) refactoring. This tutorial describes what needs to happen between when a project is conceived by a customer and when software development can start in earnest. It identifies the artifacts (beyond story cards) that may need to be produced, whether and when they should be produced, which activities can be used to produce them and who should be involved.

At the beginning of a project your stakeholders will invariably ask how much is it going to cost, what are you going to build, how long is it going to take, and how are you going to build it. To answer these questions you’re going to have to do some initial, high-level modeling of the requirements and of the architecture of the system during the initiation effort of your project. Agile Model Driven Development (AMDD) provides strategies to gain the benefits of modeling without the pain of needless documentation.