How to capture user stories (1)-Find value streams in Human-Computer Interaction

At the BA discussion forum at noon yesterday, Xiao Yu talked about the collection of requirements in a project and the process of capturing user stories. It is worth pondering. The key lies in V (valuable) in the Invest principle ). This project is a transformation project with many analysis charts. You need to maintain the current data and modify or add some charts. For example:

 

 

So how do I write a user story for such analysis charts?

 

Initially, user stories are divided based on the chart area ). That is, the line chart on the left is the first story, the table on the right is the second story, and the text box below is the third story. It looks good, but something went wrong when discussing with developers and estimating the workload. Developers asked a lot of questions, and the root cause of these questions is "Where are the values of these three story ". Indeed, they seem to be unrelated to each other in the story list, but the opposite is true. The three story is tightly coupled with data.

 

After analyzing the report, we found that users browsed the chart in a certain order and made different choices based on the data on the chart. That is to say, this Order and different options are actually the Value Stream (business flow or data flow) of this function ).

 

In the end, this chart is extracted into approximately 10 story records and clearly shows the business data flow.