User stories | Example

1. User stories
A user story is the smallest unit of work in an agile framework. It’s an end goal, not a feature,
expressed from the software user’s perspective. A user story is an informal, general explanation
of a software feature written from the perspective of the end user or customer.
User stories provide a small-scale and easy-to-use presentation of information, with little detail,
thus remaining open to interpretation, through conversations with on-site customers.
College Management System –
Features –
1. Attendance management
2. Library management

2. Feature (modules) Epic (sub modules) User stories
Attendance management
Staff’s attendance
As a staff, I want to regularly
see my attendance status, so I
can manage my attendance
efficiently.
Student’s attendance
As a student, I want to
regularly see my attendance
status, so I can manage my
attendance efficiently.
As a staff, I want to add or
update the student’s
attendance every day, so I
can track student’s
attendance record.
As a staff, I must be able to
download the attendance
record, so I can have it handy
for further evaluation.
Library management
Librarian access
As a librarian, I want to add
and modify the data of
books, book items, and users,
so that I can have an overall
check and control of the
library.
Member
As a member, I want to pre-
book the books I need, so I
can make sure it is not
reserved by others
As a staff member, I want
whole access to the question
bank and research papers, so
I can upgrade my teaching.
(Note – Similarly, write for more features :)

3. User stories describe the why and the what behind the day-to-day work of development team
members, often expressed as persona + need + purpose. Understanding their role as the source
of truth for what your team is delivering, but also why, is key to a smooth process.
Users should keep the following agile principles in mind when writing user stories.
• Working software is the primary measure of progress.
• The highest priority is to satisfy the customer through early and continuous delivery
of valuable software.
• Simplicity.