Final answer:
In building a product backlog, a Product Owner should include the level of effort, a clear description from the customer's perspective, and due dates for each item, while avoiding strictly procedural or finalized valuation details.
Step-by-step explanation:
As a Product Owner building a Backlog, three essential pieces of information should be included for each item. These are:
- The level of effort needed to complete the item, which helps in planning and prioritizing.
- A clear description from the perspective of the customer or user, ensuring that the team understands the value of the work and who it is for.
- Whether the item has a due date, which can be critical for release planning and setting expectations.
It's important to note that step-by-step instructions (option a) are usually not part of an initial backlog item, as these details are worked out when an item moves into development.
Instead, a backlog should define the problem clearly, outline the unknowns, and provide a level of understanding of the scope and resources available, as per Step 1 and Step 3 methods of problem-solving.