title: How to write User stories in Data Warehouse project
body: <p>In my Data Warehouse(More like data logistics because of we just transport data with a minimal transformation to a central HUB) project(which is said to be Agile-SCRUM) team have been writing User stories like</p>
  
  <ol>
  <li>As an analyst, I want to prepare the specification sheet so the development can start</li>
  <li>As a Developer, I want to develop the Transformation layer so that the HUB can be loaded</li>
  <li>As a tester, I want to test the table so the same can be moved to production</li>
  </ol>
  
  <p>Now for a fact I know that this is not how you write User stories since none of these represent functionality, they just represent a technical task.</p>
  
  <p>I proposed something like,</p>
  
  <ul>
  <li>As a data consumer, I want the table to be tested so there will not be any issues during consumption</li>
  </ul>
  
  <p>And for this I got questions like "The consumer never asked the table to be tested, we test it because of the process we follow. The consumer only asked for data so why should we say as a consumer in the User story"</p>
  
  <p>I do not know how to answer that and also I feel the User stories can still be composed in a better way but still sticking to the principle that <code>"User stories are chunks that can be completed within 1-2 days"</code></p>
  
  <p>I need some help to understand how others do it in a SCRUM Data logistic project and any suggestion on how this can be composed better</p>