When running a successful client project, we must know what the user story is. User stories help us understand who the client is and what we are trying to achieve. They are structured in the following way:
<AS A> This tells us exactly who the person is.
<WHEN> What is the person looking for/ going to do.
<I WANT TO> this tells us what is going to happen. This statement should be able to tell us what type of graphs and charts I should create to tell the story.
<SO I CAN> This is the action which needs to be measurable.
For example: during my final application process, I was given a data set with on London Fire Brigade call outs, including location, time and incident type. I chose to add data on property price to investigate if the average property value of the borough affects the services received. My user story will be as follows:
<AS A> potential homeowner
<WHEN> looking at the property value against the London Fire Brigade call outs,
<I WANT TO> see if living in an area with a lower average property value affects the services provided by the LFB.
<SO I CAN> deduce where the safest place to live in London is.
Our user story should be referenced throughout the project.