Distinguish between things that are ‘need to have’ and ‘nice to have’.
How this helps you
Don’t waste time on ‘nice to haves’. Focus first on what you can’t miss. Once you are in business, the additional features could serve as a great new version of or an upgrade to your product or service.
What is it?
A Product Backlog is a list of items to work on later. It breaks the bigger picture about the end-state down into manageable increments of work called Product Backlog Items (PBIs). These are typically expressed in user story form. A user story describes what is needed, by whom and why. A typical user story looks like this. As a [role], I want [service or product] in order to [goal, desired situation]. A user story for a professional golfer might be. As a [professional golfer] I want [a caddy] in order to [use the richt club for each stroke]. Having well-established rules about how work is added, removed and ordered in the Product Backlog helps to make better decisions about how to change the product. Once Product backlog items become more important, they will be refined. Refinement usually results in several smaller items to work on.
How does it relate?
As with many tools, the product backlog helps you order and prioritise. The product backlog is iterative and used in Scrum processes for development.
Your next Waypoint
The most easy way to get you started with Scrum is to download the scrumguide from scrumguides.org. Afterwards you can test your knowledge for free with one of the open assesments on scrum.org or even get official scrum certification.