If you know what you want and what are your limitations, you need a prioritized list within those constraints. In the SCRUM agile software development framework, we call this list a product backlog, and it is one of the most iconic SCRUM artifacts. My favorite definition for a product backlog is from Ken Schwaber: “Product Backlog: A prioritized list of project requirements with estimated times to turn them into completed product functionality. […] The list evolves, changing as business conditions or technology changes.”
Arrange the possible things in the descending order of importance. This is the first and most crucial step of creating a successful product backlog.
For our cat-sitter, the backlog's ...
