Agile Development with SCRUM (COMP1807)
5th Tutorial Exercise – Product Backlog User Stories Estimation – Planning Poker
Case Study Summary
The Greenwich University Book Stores project aims to build an online and hybrid book
ordering system that allows students, staff, and external customers to register, browse,
purchase, and interact with store staff online.
The system should support:
- Online catalog browsing and search
- Shopping cart and online payment
- Live chat and enquiry form
- Delivery tracking and guaranteed dates
- Integration with payment and stock systems (VISACheck, WALTERSBOOKS)
- Access for sales staff to handle problematic orders and customer enquiries
Budget: £35,000
Timeline: 8 months
Exercise 1: Breaking Down Epic User Stories
Epic ID Epic Story Breakdown into MoSCoW Order
Smaller User Stories Priority
1 As a registered 1.1 As a user, I want Must 1
user, I want to to search books by
browse and title/author/category.
search books 1.2 As a user, I want
to filter results by
price, popularity, or
rating.
1.3 As a user, I want
to view detailed book
descriptions and
reviews.
2 As a registered 2.1 Add items to a Must 2
user, I want to shopping cart.
make a 2.2 Checkout using
payment for PayPal or credit card.
books 2.3 Receive order
confirmation.
2.4 Validate payment
via VISACheck.
3 As a user, I 3.1 Add item to cart. Must 3
want to 3.2 Remove item.
manage my 3.3 Update quantity.
shopping cart 3.4 View total price
before checkout.
4 As a user, I 4.1 Open a live chat Should 4
want to get live window.
help 4.2 View chat history.
4.3 Delete chat
history.
5 As a sales staff, 5.1 Be notified when Should 5
I want to an order fails.
handle 5.2 View and edit
problematic problematic order
orders details.
5.3 Contact customers
for confirmation.
Exercise 2: Estimation using Planning Poker
User Story ID Description Story Points Reasoning
1.1 Search books by 5 Moderate
title/author/category complexity,
database and UI
integration
1.2 Filter search results 3 Simple filter logic
1.3 View book details and 8 Integration with
reviews review database
2.1 Add items to shopping cart 3 Reusable CRUD
logic
2.2 Checkout with 13 Payment gateway
PayPal/credit card integration
(VISACheck API)
2.3 Order confirmation and 5 Backend
receipt confirmation and
email
3.1–3.4 Manage cart 8 UI and backend
(add/remove/update/view) synchronization
4.1 Live chat support 13 Requires chat
integration
4.2 View chat history 5 Message database
required
5.1–5.3 Handle problematic orders 8 Moderate backend
logic
Acceptance Criteria (Examples)
User Story Acceptance Criteria
1.1 Search books - Search returns results within 2 seconds.
- Results show title, author, and price.
- No results message displayed.
2.2 Checkout - Users can pay via PayPal or credit card.
- VISACheck validates payment.
- Confirmation email sent.
3.3 Update cart - Users can change item quantities.
- Cart updates instantly.
- Total price recalculated correctly.
4.1 Live chat - Chat connects to staff.
- Messages displayed in real time.
- Chat ends after inactivity.
5.1 Problematic order alert - Staff notified within 1 minute.
- Staff can view error details.
- Orders can be marked as resolved.
Definition of Done (DoD)
- Coded to standards and peer reviewed
- Unit tested with Test Driven Development (TDD)
- 100% automated test coverage
- Integrated into main branch
- User documentation updated
- Approved by Product Owner
Draft Release Plan
Release Sprint Focus Estimated Duration Key Deliverables
Release 1 (Sprint 1– Core system setup & 4 weeks Login, registration,
2) authentication browsing catalog
Release 2 (Sprint 3– Shopping cart & 4 weeks Add to cart,
4) checkout payment, receipt
Release 3 (Sprint 5– Chat and staff 4 weeks Live chat, order
6) features management
Release 4 (Sprint 7– Integration & 4 weeks VISACheck,
8) testing performance test,
documentation
