Data Intelligence Tip: Importance of the user stories in the use case description
Most of the time during the use case design phase we are focused on the problem and solution, forgetting about who and how will be using this solution. And then later it caused a lot of issues with the adoption of the use case.
So why do we need user stories and why they are so critical:
- List item User stories add an emotional element to our use cases, making them more engaging and understandable to end-users. This is especially important for pure data governance use cases, which might otherwise sound abstract or too complex. For instance, DQ use cases are much easier to explain since they demonstrate value in the short term, while some of the data governance use cases are investments in long-term value and serve as a basis for the execution of strategic initiatives.
- List item User stories clearly explain what value our new solution brings to the organization and to individuals. Newly implemented capabilities will allow users to work with the data in a way they were not able to before. And exactly this change will improve their productivity and at the end of the data will generate business value for the organization.
- List item User stories will help us to clearly set the expectations for the users that will allow us to measure the progress and calculate the value to make sure that anticipated results are being achieved.
- List item We can’t expect that people will understand how to use a brand new solution simply by osmosis, they will need to be guided on how to do this and why. By having the user stories we can tailor our educational plans to train users and make sure that the solution is used in a way as it was planned.
Define the user stories for every use case you design and implement and you will see how much better and easier will be the adoption of your use cases.
Dmytro Lugovyi
Posted 2 years ago · Edited 1 year ago
0 comments
