Preventing IT projects Failure: Practical way to navigate through project storm, for CIOs and other executives by Naftaly Moshe

Preventing IT projects Failure: Practical way to navigate through project storm, for CIOs and other executives by Naftaly Moshe

Author:Naftaly, Moshe [Naftaly, Moshe]
Language: eng
Format: epub
Publisher: Simple Story
Published: 2018-06-25T16:00:00+00:00


Figure 14 - Less Aggressive Agile Model

The main considerations in distributing the scenarios into iterations are the importance of the scenarios to the users (the more important scenarios should come earlier), complexity (complex scenarios first), and the logical order that will allow testing the scenarios without dependency on others that were not yet developed (such as creating a customer comes before making changes to a customer’s details)

Additional consideration is the expectation for changes that will be required along the timeline. The changes will be required because of the later identification of additional needs, and because the legacy software continues to support the urgent needs of the business. Changes that are implemented in the legacy systems, might need to be supported in the new solution. The changes need to have a place in the last iteration, so it is necessary to plan the last iteration almost empty to allow the changes to be developed (20-25% of the development volume (!))



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.