Which information radiator would provide both epic-level and story-level status to a product owner?

The correct answer highlights the significance of managing both epics and user stories in the Agile framework. A parking lot chart serves as an informal visualization tool that is used to track ideas, tasks, or features that are important but not immediately actionable. In the context of delivering information to a product owner, this chart can effectively capture both high-level features (epics) and individual user stories.

The parking lot chart provides a clear overview of what is being worked on and what has been proposed or identified for future consideration. It is particularly useful for product owners to ensure they understand the current status of ongoing work while also maintaining insight into potential future items. This dual perspective helps in prioritizing and planning releases in alignment with overarching project goals.

Other options, while useful in their own ways, focus on different aspects of Agile project management. For instance, a burndown chart primarily tracks the amount of work completed versus the remaining work over a sprint but does not categorize work by epics or stories. A Kanban board visualizes the flow of tasks through various stages of completion rather than explicitly showing their relationship to epics or the status of individual stories. The product backlog, while containing all the items including epics and user stories, does not serve as an immediate