Market needs can be expressed in many appropriate ways: use cases, user stories, and other functional requirements non-functional requirements architectural changes other statements of fact Key aspects of the process are expressing market needs in a ways: that are small enough for the dev team to estimate that are clear enough to build that can be tested Sometimes user needs will be direct – “fix this bug” or “send me an email when there is a high temperature reading”. Other times you will need to convert – for example, you might want to generalize fixing the bug into fixing a whole set of bugs by improving your architecture. This can be challenge with ex-developers who become product managers, in that they tend to think in terms of “tasks”, not “needs”.
&lt;number&gt; Innovation Games® are low-cost techniques that make user research very accessible to normal agile teams.
Not a lecture on how to write a good backlog item, but how to prioritize them.