More on this book
Community
Kindle Notes & Highlights
Read between
May 21 - May 21, 2021
As you work on requirements for the solutions you were asked to build, remember to story map your ideas. Use your story m...
This highlight has been truncated due to consecutive passage length restrictions.
when a stakeholder brings a solution to you, story map and identify assumptions with them. The idea will improve right then and there.
Work with your stakeholders to identify the impact they expect a given feature to have. Document that conversation. As you implement the feature, be sure to instrument what you need to measure against the expected impact. Start doing post-release impact reviews with your stakeholders. Remind them what impact they expected a feature to have. Share with them the impact the feature actually had.
approach the situation as a collaborative problem solver.
“What did we learn during this sprint that surprised us?”
Then, for each item on the list, ask, “How could we have learned that sooner?”
have news for you. There is no “one right way” to do discovery. All of the habits in this book can and should be adopted to match your team’s preferences and needs. This book isn’t designed to be recipes that should be followed to the T, but rather templates that should help you get started.