Raise Iteration Improvement Proposals

Objective

Let any delivery participant propose a bounded change to Junior Edda or its project-specific application. The Delivery Manager facilitates and records; the team—not the Delivery Manager alone—authors proposals.

Procedure

1. Review the retrospective, MIN drift/escalations, AIN report, and repeated Project-Management Tickets.
2. Create an IIP only for a repeatable process defect or improvement opportunity. Product defects and one-off project work remain tickets/backlog items.
3. Search open IIPs for the same concern; update or link an existing proposal instead of duplicating it.
4. Write each proposal to docs/project/iips/<iip_id>-<slug>.md with:
   - stable IIP ID and title;
   - author(s), affected workflow/activity/rule/artifact;
   - problem and evidence;
   - proposed change;
   - expected effect and measurement;
   - compatibility/migration impact;
   - owner and decision point;
   - status: proposed | accepted | rejected | deferred | implemented.
5. Do not edit released Junior Edda directly. Route accepted playbook changes through the applicable governance/PIP mechanism.

Completion evidence

Every IIP has evidence, a bounded change, affected objects, an owner, decision point, status, and duplicate check. It is acceptable to record “no IIP warranted” with rationale.