How does RN fit into the software product life cycle?
The practice is most effective when implemented early in the development cycle to establish a shared vision of what is to be built and minimize the risk of not meeting customer expectations. However, it is also applied throughout the cycle as part of change management in order to maintain the shared vision as the project unfolds. Unfortunately, all too often, RN is implemented as the project approaches a delivery deadline, and developers or acquirers discover that it will be impossible to meet all of the requirements and still make the deadline. At this point in time, it becomes the last resort attempt to salvage something from the project, but its effectiveness is diminished for many reasons; customer expectations are clearly not being met; lack of trust among stakeholders; most resources have already been used. Regardless of what might be accomplished in the last minute negotiation, the project as a whole becomes a lose-lose scenario for most stakeholders. How does it relate to other
