A new feature requested after an iteration has started should be captured in the product backlog and evaluated by the Product Owner against the value and priority of existing work. Agile delivery supports changing priorities, but it does not require uncontrolled insertion of new scope into an active sprint. The team should assess ROI and relative importance, then communicate the resulting priority and expected delivery timing to the stakeholder. This approach is preferable because it uses the platform feature designed for the exact lifecycle stage involved, rather than forcing the requirement into a neighboring layer. Accepting work simply because a stakeholder escalates or because the change seems small undermines sprint predictability and can prevent completion of already committed stories. Backlog governance is the mechanism that preserves adaptability without sacrificing delivery discipline. In Communications Cloud, that separation materially affects maintainability, performance, and the accuracy of future MACD or order-processing behavior. The solution should therefore preserve parent-child and inventory dependencies, use standard qualification or orchestration semantics, and ensure that downstream systems receive only the information relevant to their responsibility. The same design also simplifies regression testing because the business rule is expressed in one authoritative place and can be validated independently from unrelated product or integration behavior.

Study Guide Reference:Agile delivery; product backlog; Product Owner; sprint scope; prioritization.