How does FeaturePlan interact in an Agile / Extreme Programming environment where the development cycles are frequent (i.e. two weeks)?
In short, Agile development is like a miniature software project. Each miniature project includes all the tasks, such as the planning and requirement analysis tasks, necessary to release the mini-increment of new functionality. The fact that the iterations (or releases) are smaller makes it even more important to have FeaturePlan help you do what-if scenarios and provide an easy way to report the scope of each one of your iterations. Extreme Programming is one of several Agile software development methodologies. One of the goals of Extreme Programming is to give all developers a view of the system that matches the view held by the users (i.e. user/developer collaboration). This interaction is documented through user scenarios (a supported document type in FeaturePlan). The output of the scenarios is requirements being fed into the release planning phase. In summary, you get short cycles where development is interacting with the requirements from the users. It follows the gather, define
