Split business and technical discussions
From "Fifty Quick Ideas to improve your user stories" Book
It is not a good idea to discuss business and technical sides of the user story at once what ever user stories often involve technical design changes .
Technical discussions are important but shouldn't happen at the same time as the conversation about the business perspective of a user story , unless your business users are also programmers , split two discussions into separate more focused meetings .
There are many benefits when separate two meetings,
1# Allowing teams to shorten the business conversations and use the time of their business users more efficiently, Staying focused on the business needs during a story discussion prevents business users from getting bored .They won't feel that conversation waste their time and they will be more engaged in discussion
领英推è
2#Allows team to consider a whole batch of stories when thinking about design changes, related stories often impact the same functional areas of underlaying software system, so considering an entire group of stories at once often leads to shorter technical discussion and better design decisions.
3# A focused discussion also prevents teams from jumping into implementation details too soon and instead makes them spend more time on really understanding what needs to be done. Delivery teams often propose better, faster or cheaper solutions once they understand what business users are trying to achieve.
To make this work specially with a team that often jumps into technical discussions with business users , Try to agree with this team upfront when the implementation details should be discussed For example 'Have a separate technical meeting immediately after the user stories refinement sessions '
If some technical implementation has a significant impact on capability to deliver something , such as a subset of features with not so good performance which could be improved later , choosing between the options is a business decision and stakeholders need to understand possible benefits and tradeoffs , But watch out for technical discussions that don't really help in deciding what should be done .