title: User stories for integration in Scrum
body: <p>I am working on a project that has very complex integration needs, specifically with receiving and sending EDI data and all the "fun" stuff that happens in between.  I can definitely focus efforts around data processing (validation, required fields, transformation), but the problem I am having is how to frame stories and epics in the backlog to plan and track work.</p>
  
  <p>It is very easy to say "As a manager, I can deny a vacation request so that I can make sure that I have enough workers on staff to meet my commitments."  Actually, I am very very good at this, but I am very new to this kind of integration effort.</p>
  
  <p>For a big integration project, it is tougher to indicate who the user is, and what the value is.  The EDI integration are just interface (non-functional) requirements, but the implementation is a big effort.</p>
  
  <p>Can anyone provide some guidance on how to structure / frame these kinds of requirements in the product backlog I am creating?</p>