How to write a Product Requirement Document - Shoieb Yunus
Example PRD : Online Garment Tracking and Management System
Software Requirements Specification (Sample)
Version: 0.1
1. Purpose
The purpose is to demonstrate the general understanding of an online garment tracking and management system. The web portal leverages order fulfillment and logistics practices.
2. Scope
The scope of this document is limited to a high-level overview of the key components, functionality and steps requiring garment life cycle management module.
3. Key Components
The system consists of the following key components that need to be designed, developed and integrated for a uniform experience:
- E-Commerce platform
- Inventory Management and Order Fulfillment
- Payment System
- Recommendation System – Collaborative Filtering
- CRM (tightly coupled with Real-time Reporting and RecSys)
4. Product Requirements
4.1 Functionality
- Web site visit – user lands on the home page
- Display – user is shown the latest arrival of garments
- User registration – user registers to browse the garment
- Search – user is allowed to perform search based on brands prior to capturing user profile (preferences/taste/etc.)
- User profile – user creates her profile for better search results
- Browse – user can browse the site
- Search – user performs search on the garment(s) based on multiple search criteria such as, garment type, size, brand, latest arrival, etc.
- Check availability
- If yes, goes into the shopping cart
- Else, continue browsing
- Pricing and Plan Options – user selects the pricing and plan option and enters the credit card info
- Credit card info is instantly verified
- Upon checking out, the credit card is processed
- Order acknowledgement email is sent to the user
- Order is sent to the Fulfillment Center for immediate processing
- Operations, Sales and Marketing are notified of the user action via CRM for relevant actions
- Order processing, shipping, tracking and delivery managed by the Fulfillment Center
- Full cycle repeats when the user sends in the garment for replacement (the Netflix model)
4.2 Garment Life Cycle Management
The purpose of this system is to determine life of each garment based on historical/product usage data, and manage garment life cycle. Fulfillment center clerk/operator is trained to enter the required data into the system every step of the way.
- Garment visual inspection
- Re-kitting if missing minor parts
- Garment washing/steaming, folding and bagging
- Ready for order fulfillment
- Track each garments wear and tear upon each return.
- Determine ROI(Return On Investment) per garment and SKU (Stock Keeping Unit)
- When garment reaches EOL(End-of-life), then discard or auction (at a discounted rate)
4.3 GUI
- Uniform look and feel on all web pages
- Easy to navigate product catalog
- Community-building features to foster word-of-mouth and growth
- Product recommendations
5. Challenges
- # of SKUs and total inventory management
- Efficiency and reliability in product delivery to the customer
- Data mining for decision making
- Timely demand fulfillment
6. Optimization
- Pull, pack and ship the same day
- Optimization of inventory, delivery time, resources (labor), and territory coverage
- As an example, what SKU’s to be stocked at which warehouse?
- Data capture and analysis at all times. Dashboard views for real-time data for different groups
- Use of predictive analytics for SKU management and cost control
- Features development for Users community building for early adaptors
- Features development for customer life cycle management from user acquisition, engagement, retention, referral and revenue
Reference : Shoieb Yunus and Gaurav Oberoi