A Story About Misunderstood Requirements
In this Scrum Tapas video, Professional Scrum Trainer Chris Lukassen is joined by Intergamma's Scrum Master Jochen Hendriks to discuss how misinterpreted requirements can provide the completely wrong solution for the users, yet sound as if it was exactly what they wanted. They will use a real-world example of how users wanted one thing and the development team delivered what they interpreted, but not what was desired. Their solution includes getting the Development Team closer to the customer.
If you aren't sure how to better align the customer/user and the Development Team, then these questions might be insightful during your next Sprint Retrospective:
- Can we talk to actual users during Product Backlog Refinement?
- How can we get actual users interacting with the product during Sprint Review?
- What can we do to have an interaction between the Development Team and Business on a daily basis?
- What can we do to speed up our feedback cycle?