This content originally appeared on NN/g latest articles and announcements and was authored by Anna Kaley
Summary: Scaling discovery work in Agile helps teams plan appropriately scoped activities around targeted questions and probable assumptions instead of arbitrary sprint timeframes.
The goal of discovery is to learn about a problem or opportunity before developing solutions. Discovery involves gathering information from multiple methods and sources to determine whether a problem is worth solving or an opportunity warrants further pursuing. Discovery provides insight into how to approach the problem, what factors to consider along the way, and what success looks like. At the end of discovery, teams should be able to formulate a problem or opportunity statement and confidently propose potential solutions.
Discovery and Agile-Sprint Timing
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. 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.
UX professionals often find it challenging to do discovery work in Agile, so they rush or skip it entirely. Or teams think that all discovery activities must be completed by the end of a sprint. 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.
Read Full Article
This content originally appeared on NN/g latest articles and announcements and was authored by Anna Kaley
Anna Kaley | Sciencx (2023-02-05T17:00:00+00:00) Discovery in Agile. Retrieved from https://www.scien.cx/2023/02/05/discovery-in-agile/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.