User Stories

XYZ - ABC

example.com Document

version:    0.1
date:       <DATE>
Status:     Initial Release

Developed by:	XYZ
(@person)

Developed for:	ABC

    1. Introduction

        1.1 Purpose
        
        The Purpose of this document is to ensure alignment of understanding between the end customer and the development team. This document will ensure that ABC and XYZ’s development team interpret requirements in the same way. The document is also to enable planning of development. This document will capture description of a example.com features from an end-user perspective.

        1.2 Intended Audience
        
        All stakeholders of the system including
        • ABC - Designers, Programmers, Testers, Integrators, Deployment Engineers
        • Project Managers
        • XYZ’s Team associated with this project
        
    2. User Stories

      Sdmin User Stories

      Here the user is SAdmin and this story and parts will be able to define the SAdmin capabilities & flow.        
      
      
      2.1.1 Login

      AUS-01        Login: Successful Login to System
      
      Definition    As a SAdmin, I want to blah bla bla..
      
      Acceptance Criteria
        • something that we understand
        • something which we are purposing
        • some doubt can also put as ?
        • confirming something before go