This project follows the Agile methodology with a focus on sprint-based development, ensuring iterative progress, continuous feedback, and adaptive planning.
Each Sprint lasted for 2 weeks, focusing on specific goals such as User Authentication, Product Catalog, Cart Management, and Order Tracking. At the end of every sprint, a review and retrospective were conducted to evaluate progress and plan for improvements.
A prioritized list of work items (features, bugs, enhancements, etc.) that need to be completed. It is divided into:
-
Product Backlog – Managed by the Product Owner, contains all future work.
-
Sprint Backlog – Tasks chosen for the current sprint.
All tasks were maintained in the Product Backlog, prioritized by importance and dependency. For each sprint, selected items were moved into the Sprint Backlog (e.g., “Add to Cart Functionality”, “Checkout Integration”).
The project followed a 4-sprint timeline, progressing as follows:
Sprint 1 or Version 1: User Login & Registration
Sprint 2 or Version 2: Product Listing & Filtering
Sprint 3: Cart & Checkout Flow
Sprint 4: Order Tracking & UI Enhancements
A large user story or feature that can be broken down into smaller tasks or stories. It represents a significant business goal (e.g., “Implement User Authentication System”).
Defines the nature of the task, such as:
-
Feature – new functionality
-
Bug – error or issue to be fixed
-
Task – general work item
-
Improvement – enhancement to existing functionality
Indicates the current progress of a work item. Common statuses include:
- To Do
- In Progress
- In Review
- Done
Tags used to categorize tasks or issues, such as frontend, backend, bug, or enhancement, for better tracking and filtering in tools like Jira or GitHub Projects.
End with a short statement connecting Agile principles and your learning outcome:
This project reflects how Agile principles — especially sprint planning, backlog management, and iterative feedback — help in building structured and adaptive software solutions efficiently.