Key to successfully complete a #DigitalTransformation initiative that generate real value is a proper definition and understanding of the requirements.
Asking to business people to define them in detail without knowing the Digital Opportunities you have may limit the benefits you could built.
You can overcome this risk by considering requirements definition as "High level wishes" (user story) a goal of the #Agile project exactly as their development.
It will be useful both for developers to enter properly into the topic and for the business resources that will "see" their needs from a completely different perspective.
This Is what I do as #scrummaster everytime i have that opportunity.
Do you follow a similar approach? Which suggestions do you have?