Capstone Project - E-commerce Website Development
1. Narrative Charter Statement
Project Title: E-commerce Website Development for Fashion Retailer
Project Purpose:
The purpose of this project is to design, develop, and launch a fully functional e-commerce website
for a mid-sized fashion retailer, enabling customers to browse products, make secure purchases,
and track deliveries online. This will expand the retailer's sales channels and improve customer
convenience.
Project Objectives:
1. Design a modern, mobile-friendly UI/UX that aligns with the brand identity.
2. Implement secure payment gateways (Visa, MasterCard, PayPal).
3. Build a product catalog with filtering and search functions.
4. Integrate inventory and order management systems.
5. Launch the website within 6 months and achieve 10% increase in sales in the first quarter after
launch.
High-Level Requirements:
- Responsive website accessible on all devices.
- Secure login and user account management.
- Admin dashboard for product, order, and customer management.
- SEO-friendly architecture.
- Multi-language and multi-currency support.
Key Stakeholders:
- Sponsor: CEO of Fashion Retailer
- Project Manager: Internal IT Project Manager
- Development Team: Frontend & Backend Developers, UI/UX Designer
- Marketing Team: Digital Marketing Specialist, SEO Expert
- Customers: End-users purchasing online
Budget Summary: Estimated budget: $35,000 (Development: $25,000, Hosting & Security: $5,000,
Marketing: $5,000)
Success Criteria:
- Fully functional, secure, and user-friendly website delivered on time and within budget.
- At least 95% uptime in the first 6 months.
- Minimum 500 registered users in the first month after launch.
2. Work Breakdown Structure (WBS)
Level 1: E-commerce Website Development
1. Project Initiation
1.1 Define project scope
1.2 Identify stakeholders
1.3 Develop project charter
2. Planning
2.1 Requirements gathering
2.2 Technology selection
2.3 Schedule & budget planning
3. Design
3.1 UI/UX design
3.2 Wireframe approval
3.3 Prototype development
4. Development
4.1 Frontend coding
4.2 Backend coding
4.3 Database setup
4.4 API integration
5. Testing
5.1 Functional testing
5.2 Security testing
5.3 User acceptance testing (UAT)
6. Deployment
6.1 Server setup
6.2 Domain & SSL setup
6.3 Website launch
7. Post-launch Support
7.1 Bug fixes
7.2 Performance optimization
7.3 Marketing campaigns
3. Sequence Project Activities
1. Define scope -> Identify stakeholders -> Develop project charter
2. Requirements gathering -> Technology selection -> Schedule & budget planning
3. UI/UX design -> Wireframe approval -> Prototype development
4. Frontend & backend coding -> Database setup -> API integration
5. Functional testing -> Security testing -> UAT
6. Server setup -> Domain & SSL setup -> Website launch
7. Post-launch bug fixes -> Performance optimization -> Marketing campaigns
4. Build a Project Schedule
Task | Duration | Start Date | End Date
Project Initiation | 1 week | 01/09/2025 | 07/09/2025
Planning | 2 weeks | 08/09/2025 | 21/09/2025
Design | 3 weeks | 22/09/2025 | 12/10/2025
Development | 8 weeks | 13/10/2025 | 07/12/2025
Testing | 3 weeks | 08/12/2025 | 28/12/2025
Deployment | 1 week | 29/12/2025 | 04/01/2026
Post-launch Support & Marketing | 4 weeks | 05/01/2026 | 01/02/2026
5. Create a Project Budget
Category | Estimated Cost (USD)
Development | $25,000
Hosting & Security | $3,000
Domain & SSL | $500
Marketing Campaigns | $4,000
Testing Tools | $1,000
Contingency (5%) | $1,500
Total | $35,000
6. Responsibility Assignment Matrix (RAM)
Task | Project Manager | Developer | Designer | QA Tester | Marketing
Project Charter |R | | | |
Requirements Gathering | R |A |C | |
UI/UX Design |C | |A | |
Development |C |A | | |
Testing |C |C | |A |
Deployment |R |A | |C |
Marketing Campaign |C | | | |A
7. Identify Project Risks with Responses
Risk | Probability | Impact | Response Strategy
Delay in requirements gathering | Medium | High | Hold early workshops with stakeholders
to finalize requirements quickly.
Technical issues during development | Medium | High | Allocate buffer time in schedule and
have contingency budget for external experts.
Security vulnerabilities after launch | Low | High | Conduct penetration testing and apply
regular security patches.
Budget overrun | Low | Medium | Track expenses weekly, get sponsor
approval for any change in scope.
Low user adoption | Medium | Medium | Run strong pre-launch marketing
campaign and offer first-month discounts.
