221.2 User stories and backlog

This section defines the user stories and prioritised feature backlog that guide the development of the Task Tracker app across multiple sprints.

User stories

User stories describe the desired functionality from the user’s perspective. Each story follows a consistent format, helping to clarify what the system must do and why it matters. These stories provide the foundation for class and method design in the next module.

User story ID	Story
US1	As a user, I want to create a task by entering a title, description, and due date.
US2	As a user, I want to view a list of all my tasks with their completion status.
US3	As a user, I want to mark a task as completed or uncompleted.
US4	As a user, I want to view the full details of a specific task.
US5	As a user, I want to filter tasks by whether they are complete or incomplete.
US6	As a user, I want to sort tasks by due date or alphabetically.
US7	As a user, I want to save my tasks so they are available the next time I use the app.
US8	As a user, I want to add optional categories or priority levels to help organise my tasks.

These stories will be tagged and tracked through sprints to guide development priorities.

Feature backlog

The backlog groups stories into sprints based on their importance and the sequence of implementation. The first sprint focuses on the minimum viable product (MVP), while later sprints introduce enhancements.

Core features (Sprint 1 – MVP)

Feature	Description	Linked User Stories
Task creation	Create a new task with a title, description, and due date	US1
Task storage	Store multiple tasks in memory	US1–US4
Task listing	Display tasks with title and completion status	US2
Mark as complete/incomplete	Change task status	US3
Task detail view	View full information for a selected task	US4

Additional features (Sprint 2+)

Feature	Description	Linked User Stories
Task filtering	View only completed or incomplete tasks	US5
Task sorting	Sort tasks by due date or alphabetically	US6
File persistence	Save/load tasks to/from a file	US7
Categories or priority	Add organisational tags or labels	US8
Input validation	Improve user feedback and error handling	Internal

Sprint planning summary

Sprint 1 targets core functionality: creating, storing, and interacting with task objects in memory. It will result in a functional and testable program that utilises OOP principles. Sprint 2 will focus on extending functionality, improving usability, and introducing persistence. Each sprint includes time for testing, refactoring, and updating documentation.