One of the "assumption" that is often made, when starting to adopt Scrum, is that there will be a Product Owner and there will also be a Product Backlog. Well, it happens that the Product Backlog quality is one of the major responsible for the outcome of what the team will produce in terms of software, and is absolutely one of the most difficult things to work out. There are many problems related to having a right Backlog in place, and as you may guess there is no "one recipe" for the right Backlog, only some important ingredients to mix up in the right way ;-)
From Requirement to User Story
Requirements Engineering is still one of the major challenges also in agile software projects.

