Software Engineering Process
Models
Agile (Scrum) Applied to an Online Shopping System
Why This Case Study Matters
E-commerce demands rapid iteration
Customer needs shift weekly — what worked last month may already
be outdated.
Scrum handles evolving requirements
Where waterfall locks you into an upfront plan, Scrum embraces
change as a feature.
Used by industry leaders
Netflix, Amazon, and Shopify all build products using iterative, agile-
first approaches.
The Project: Online Shopping System
Platform Overview
A medium-to-large e-commerce platform serving multiple user roles across
interconnected systems.
Users: Customers, admins, sellers, delivery staff
Core features: Browse, order, pay, track shipments
Customer Portal Admin Panel Payment Gateway Inventory & Shipping
Functional Requirements
User Accounts Product Catalog Cart & Checkout
Registration, login, and profile Browse products with robust search, Add to cart, proceed to checkout, and
management for all user roles. filtering, and category navigation. complete secure payment processing.
Order Tracking Admin & Seller Tools
Real-time order status updates and full Inventory management, seller
order history for customers. onboarding, and platform administration.
Non-Functional Requirements
System Quality Standards
⚡ Scalability 🔒 Security
Handle traffic spikes — Black Encrypt payment data end-to-end
Friday, flash sales, and seasonal and protect user privacy at every
peaks. layer.
🚀 Performance 🟢 Availability
Sub-2-second page loads — every 99.9% uptime guaranteed — the
extra second costs conversions. store never closes.
Why Scrum Fits This Project
Requirements Always Early Delivery Builds
Evolve Confidence
Customer trends shift, Stakeholders see working
competitors launch features, software in weeks, not months.
new payment methods emerge Trust is earned through
— Scrum absorbs this naturally. demonstrated progress.
Continuous Feedback Loops
Misalignment is caught early — before it becomes an expensive rework
at the end of the project.
Scrum Framework Applied
Product Backlog Sprint Planning
Sprint Review Daily Standups
Each 2–4 week sprint delivers a working software increment — stakeholders see real progress, and the team continuously refines its
process based on feedback from every cycle.
Scrum Roles in Action
Product Owner Scrum Master Development Team
Prioritizes the feature backlog, gathers Removes blockers, facilitates ceremonies, Cross-functional engineers who design,
customer feedback, and ensures the team and shields the team from external code, test, and deliver working increments
always builds the most valuable thing distractions so they can focus on delivery. at the end of every sprint.
next.
Real Benefits for E-Commerce
Scrum Delivers Measurable Value
Ship payment integration in Sprint 2, gather real feedback before building order
tracking
Continuous testing catches bugs early — especially critical for payment and
checkout flows
Adapt mid-project to competitor moves, new regulations, or shifting market
demands
Stakeholders see progress every 2–4 weeks — not only at the very end
Scrum turns every sprint into a checkpoint — catching problems while
they're still cheap to fix.
Risks & Limitations
Scope Creep Third-Party Delays
Evolving requirements can balloon the timeline if the Payment gateway or shipping API issues can block an entire
backlog isn't carefully managed and prioritized. sprint — dependencies require proactive planning.
Team Dependency Cost Unpredictability
Scrum requires experienced, self-organizing developers and Final budget is harder to forecast than waterfall —
strong communication habits to function well. stakeholders must be comfortable with adaptive planning.
Scrum vs. Alternatives
Choosing the Right Model
Waterfall: Better for fixed, well-understood requirements
— but risky for e-commerce where requirements always
change
Incremental Model: Useful if modules are truly
independent; less effective with tightly coupled systems like
payment and inventory
Kanban: A powerful complement to Scrum for continuous
delivery and flow optimization after initial build
For an online shopping system, Scrum is the
recommended approach — its flexibility and regular
feedback loops directly match the pace of e-
commerce.