Agile-Lean International 2020 conference

Have you ever experienced this? Your team discusses a story in the planning meeting, codes and tests using good practices, delivers it to the product owner or customer - who then rejects it because it wasn’t what they wanted. High rejection rate leads to long cycle times, wasted time and general frustration. How can teams make sure everyone shares the same understanding of features and stories to build, without spending too much time up front? Teams also need to remember to plan for the many different quality attributes that may be critical to a product’s success.
Janet and Lisa will share some techniques they’ve used to guide conversations about requirements among product people, developers, testers and other team members. Helping the business stakeholders be clear about new features and stories, getting business rules with concrete examples of desired behavior, builds the shared understanding needed to deliver valuable changes frequently and predictably. 
Learning takeaways:
• Ways to explore requirements and do deliberate discovery, in a timely manner, to uncover missing, conflicting, erroneous and unnecessary requirements.
• Techniques from agile business analysis and agile testing models that help teams scope each feature and deliver acceptable value to the business, considering all relevant quality attributes.
• How to use your testing mindset and conversation frameworks to help your whole team build shared understanding for each feature and story, shortening cycle time and reducing rejections.