User Stories

Project
“Arogya Bhagya Yojane”
ABY

Confidential

xxxxx
Change Records

Version Date Prepared by / Release Significant Changes

No. Modified by

0.1 6th June Advali, Robert Draft

2010

0.2 7th June Advali, Robert Draft Consolidated two of the epics
2010

Reviewers

Name Position

Vinod CTO

Robert Functional specialist

Bjarte Fosse Tech lead

Distribution

Copy No Name Location

Version 0.2 Jardar, Bjarte, Kenneth, Vinod E-mail

Note to Holders:
If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the
cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.
Table of content

OVERVIEW............................................................................................................................................................. 5

EPICS........................................................................................................................................................................ 6

EPIC A..................................................................................................................................................................... 6
EPIC B........................................................................................................................................................................ 6
EPIC C.......................................................................................................................................................................... 6
EPIC D......................................................................................................................................................................... 6
EPIC E.......................................................................................................................................................................... 6
EPIC F.......................................................................................................................................................................... 6

STORIES BASED ON EPIC A................................................................................................................................ 7

STORIES BASED ON EPIC B................................................................................................................................ 7

STORIES BASED ON EPIC C................................................................................................................................ 8

STORIES BASED ON EPIC D................................................................................................................................ 8

STORIES BASED ON EPIC E................................................................................................................................ 8

STORIES BASED ON EPIC F................................................................................................................................ 9

ITERATIONS (EXAMPLE)................................................................................................................................. 10

REPORTING (EXAMPLE).................................................................................................................................. 10
Overview

The overall scope of this document is to cover the user stories required to develop a systems
platform administration web for monitoring performance, changes and stability using Agile
development strategy.

The user stories are structured in epics to give an overall picture, followed by more detailed user
stories.

The user stories will be estimated with a rating from 1-13 where 13 is the highest value. The value
expresses the demand for development time.

One of the goals of user stories is to get people talking rather than writing. Software requirements
are a communication problem. To succeed, a project relies on information from the heads of very
different people. What we need is a way to work together so that neither side dominates, nor the
resource allocation becomes a shared problem. This is why we use user stories.

A final release plan will be organized in iterations. Each iteration will consist of one or more user
stories and there will be story points (story points are an expression for the resources needed in
order to support the user story in the application) to each of the stories in order to do proper
prioritizing.

Finally stories will be prioritized based on their value to the organization.

Roles:

1. Administrator(DG/ADG)
2. Nodal Agency (Basket Option)
3. Network Hospital
4. Unit

Flow:-

Patient

Seeks for acknowledgment

Unit
Provides acknowledgment

Patient with Acknowledgment letter

Network hospital

Network hospital verifies the Acknowledgment with Unit.

Patient gets treatment

Network Hospital sends bill to BO

BO pay to NH

BO seeks unit for reimbursement

EPICS

EPIC A
Hospital can login under Network Hospital Login Type.

EPIC B
Hospital can enter details of patient in an Admission form.

EPIC C
Hospital can view no. of patients admitted under ABY scheme.

EPIC D
Hospital can cross-verify ABY acknowledgement card with respective Units and get confirmation.

EPIC E
Hospital can send bills along with Patient treatment history to Basket Option for reimbursement.

EPIC F
Hospital can have configurable menus like Bill submission; Claim list; Patient history documents;
Recovery reports, Claim settlement statement, Claim status query.

EPIC G
Hospital can receive payment through RTGS from DG.

EPIC H
Hospital can view list of claims under ABY scheme are approved

EPIC I
Hospital can view list of claims under ABY scheme are rejected.

EPIC J
EPIC A
Hospital can login under Network Hospital Login Type.

EPIC B
Hospital can enter details of patient along with acknowledgement no. in an Admission form.

EPIC C
Hospital can view no. of patients admitted under ABY scheme.

EPIC D
Hospital can cross-verify ABY acknowledgement card with respective Units and get confirmation.

EPIC E
Hospital can send bills along with Patient treatment history to Basket Option for reimbursement.

EPIC F
Hospital can have configurable menus like Bill submission; Claim list; Patient history documents;
Recovery reports, Claim settlement statement, Claim status query.

EPIC G
Hospital can receive payment through RTGS from DG.

EPIC H
Hospital can view list of claims under ABY scheme are approved

EPIC I
Hospital can view list of claims under ABY scheme are rejected.

EPIC J
EPIC A
Unit can login under Individual Unit Login Type.

EPIC B
Unit can view the list of application seeking for acknowledgement.

EPIC C
Unit can create unique acknowledgement ID No.

EPIC D
Unit can send acknowledgement card to applicant (patient) through email.

EPIC E
Unit can send bills along with Patient treatment history to Basket Option for reimbursement.

EPIC F
Unit can enter details of police man in acknowledgement form and can create unique
acknowledgement ID No.

EPIC G
Hospital can receive payment through RTGS from DG.

EPIC H
Hospital can view list of claims under ABY scheme are approved

EPIC I
Hospital can view list of claims under ABY scheme are rejected.

N Story point
o Stories based on EPIC A
“A Hospital can login as Network Hospital type”

A1 A hospital will be to login by providing valid username and password

A2 A hospital can logout
A3 A hospital will be redirected to the admission form after logging in where patient details
like Name of the patient, Name of the Applicant, Self/Dependent, Age, Sex, I.D., Name of
Unit, Date of admission, Date of Discharge, Preliminary diagnosis, Treatment
undertaken, Bill No., and Department Name.
Note: Applications not running should appear on the main page
Iterations (Example)
Iteration Stories Story Points
Iteration 1 A1, B4 XX
Iteration 2 C2, D2 XX
Iteration 3 E2 XX

Reporting (Example)

Iteration Iteration Iteration Iteration

1 2 3 4
Story points at start of iteration 130 113 78 31
Completed during iteration 45 47 48 31
Changed estimates 10 4 -3
Story points from new stories 18 8 4
Story points at end of iteration 113 78 31 0