A project sponsor has requested a clear delivery roadmap for the implementation of a complex system that does not have clear and stable requirements. How should the team address the project…

A product backlog lists user stories at a granular level but does not constitute a delivery roadmap or communicate timing and milestones to a sponsor.

A project schedule with lag addresses sequencing and buffer but cannot be meaningfully built when requirements are not yet stable or clear.

A release plan maps out major feature milestones and delivery windows at a high level, giving the sponsor the roadmap they need while accommodating the evolving nature of unclear requirements. It is the appropriate artifact in adaptive/hybrid projects to communicate planned delivery points without committing to a fully detailed schedule that would be premature and likely inaccurate.

A prototype helps clarify requirements but does not directly produce a delivery roadmap or address the sponsor's communication need.