If the stakeholder has not agreed on the final details of a requirement, it might be changed to a lower priority due to the immaturity, or what we refer to here as the stability level, of the requirement. This is because it is assumed that the requirement will still change as and when new information becomes available. From an initiative delivery point of view, it doesn't make sense to spend time and resources on requirements that are not finalized or considered somewhat unstable, due to the fact that any work and effort might have to be reworked once the stakeholders come to an agreement on the intent and content of a particular requirement.