From the course: Agile Analysis Weekly Tips

Unlock this course with a free trial

Join today to access over 22,600 courses taught by industry experts.

Needs vs. guesses

Needs vs. guesses

From the course: Agile Analysis Weekly Tips

Start my 1-month free trial Buy for my team

Needs vs. guesses

“

- So you're in a backlog refinement meeting, and you and the team are discussing some of the most recent requirements. How do you know if you're articulating customer needs or guessing at their needs? How about the rest of the team? How do we know if they're guessing? Being aware of this difference can make or break getting meaningful results as a team. So for example, let's say you've got some requests coming in and some data that show there's a problem with order history. Your users are searching and searching for it. They can't seem to find it, and this is a pattern that you're seeing. With that, the team decides to create a backlog item and tackle this issue. We've got to do something about order history. To make it easier to find, the team decides to put a link on the homepage for order history. Problem solved, right? Not quite. I would actually say the team just guessed at the user need. Why do I think that? Well, upon further research, if we look at the entire user context…

Contents