![]() While it's important to timebox discovery, don't arbitrarily use sprint length to set timing for your discovery research. The tight timeframes make discovery feel like a lost cause, so teams omit it from the Agile process and rush to features and solutions instead –- a risky approach. Or teams think that all discovery activities must be completed by the end of a sprint. UX professionals often find it challenging to do discovery work in Agile, so they rush or skip it entirely. ![]() Discovery gives us the information we need to understand what’s valuable to our users and organizations, and thus the ability to do iterative product development well. Practitioners often ask us, "How can we fit discovery in Agile?" We typically answer with a reminder that Agile isn't about moving fast or recklessly: it's about prioritizing and delivering small, high-value increments to users, early and often. At the end of discovery, teams should be able to formulate a problem or opportunity statement and confidently propose potential solutions. Discovery provides insight into how to approach the problem, what factors to consider along the way, and what success looks like. Discovery involves gathering information from multiple methods and sources to determine whether a problem is worth solving or an opportunity warrants further pursuing. ![]() The goal of discovery is to learn about a problem or opportunity before developing solutions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |