Agile Scrum Process
Agile Scrum
Epic
└── Feature
└── User Story
└── Task
During my Software QA certification, I delved into the Agile Scrum Process. From Epics to Tasks, I showcased my grasp of Agile methodologies and workflows. Below is the process involving a shopping cart app idea
EPIC 1 -
Epic – Core Functionality & Data Management
Feature: Real-Time Item Updates
-
User Story 1: Real-time item sharing between devices
-
Task: Implement real-time syncing
-
Task: Test sync across devices
-
-
User Story 2: Instant updates while shopping
-
Task: Push notifications for changes
-
Task: Real-time list view updates
-
​
EPIC 2 -
Epic – User Login & Authentication
Feature: Two-Factor Authentication
-
User Story 1: Enable 2FA for accounts
-
Task: Integrate Google Authenticator
-
Task: Add setting toggle for 2FA
-
-
User Story 2: One-time passcode via SMS on new devices
-
Task: SMS OTP implementation
-
Task: Device tracking for 2FA trigger
-
EPIC 3 -
Epic – User Interface and Design
Feature: Drag-and-Drop Reordering
-
User Story 1: Reorder list items
-
Task: Implement drag-and-drop UI
-
Task: Sync updated order across devices
-
-
User Story 2: Move items between categories
-
Task: Enable drag between categories
-
Task: Update item category on drop
-
Sprint Planning:
The team meets to define what features and tasks will be tackled in the next sprint. For the Shopping List App, this could include deciding whether to focus on implementing drag-and-drop functionality or starting two-factor authentication setup.
​
​
Daily Scrum (Stand-up):
A short daily check-in where the team shares progress, plans for the day, and any roadblocks. For example, a developer might mention needing help integrating real-time syncing across devices.
Sprint Review:
At the end of the sprint, the team demonstrates completed features—like showing how items can be dragged between categories—and gathers feedback from stakeholders or users for improvements.
Sprint Retrospective:
After the sprint review, the team reflects on what went well, what didn’t, and how to improve. For instance, the team might note that testing on multiple devices took longer than expected and decide to start testing earlier in the next sprint.