What describes a lightweight description of an individual initiative's required functionality?

What describes a lightweight description of an individual initiative's required functionality?

• A. A list of broad areas of required functionality with timelines for when each feature will be complete
• B. A prioritized list of new features, bugs, and architectural tasks
• C. A lightweight description of an individual initiative's required functionality
• D. A list of work organized by epic and version

Answer: (C)

A lightweight description of an individual initiative’s required functionality is a compact, action-focused artifact that states exactly what must work for that initiative, without getting bogged down in schedules, backlogs, or task-level detail. This kind of description keeps focus on the outcome and what the solution must be able to do, making it easier to validate with stakeholders and adjust as needs change. The other options describe broader planning artifacts: one emphasizes timelines and broad areas to cover, which adds scheduling and scope management; another centers on a prioritized backlog of features, bugs, and architectural tasks, which is more about immediate work items than a concise functional description; and the last organizes work by epic and version, which is about grouping and delivery plans rather than a lean statement of required functionality.

A lightweight description of an individual initiative’s required functionality is a compact, action-focused artifact that states exactly what must work for that initiative, without getting bogged down in schedules, backlogs, or task-level detail. This kind of description keeps focus on the outcome and what the solution must be able to do, making it easier to validate with stakeholders and adjust as needs change.

The other options describe broader planning artifacts: one emphasizes timelines and broad areas to cover, which adds scheduling and scope management; another centers on a prioritized backlog of features, bugs, and architectural tasks, which is more about immediate work items than a concise functional description; and the last organizes work by epic and version, which is about grouping and delivery plans rather than a lean statement of required functionality.