PROJECT BRIEF (MVP) New Supermatket – New Mobile App Build (MVP Scope) 1. Purpose of This Document This document defines the Minimum Viable Product (MVP) scope for the New Supermatket mobile application rebuild. It outlines what is essential to launch a stable, scalable, and business-ready platform while deliberately excluding non-critical enhancements. The intent is to enable a fast, controlled launch while laying a strong technical foundation for future growth. 2. Project Overview New Supermatket currently operates a live mobile application processing approximately 250 orders per day. The business has decided to build a completely new mobile application and backend platform from scratch, reusing only the existing user base and product catalog at launch. The new MVP platform must reliably support at least 500 orders per day from launch and be architected to scale further without requiring a rebuild. 3. Business Continuity & Launch The MVP must be launched in a way that minimizes disruption to existing users. Existing user accounts and product data will be migrated to the new system. The launch approach should support a controlled rollout with monitoring and rollback capability. 4. Customer Mobile App The MVP mobile app (iOS & Android) must support the complete shopping journey: • User login and signup (existing and new users) • Product browsing via categories and search • Product detail pages • Add to cart and cart management • Checkout with supported payment methods • Order confirmation and order tracking • Order history • User profile management The app must be fast, reliable, and optimized for repeat usage. 5. Backend Platform The backend must support all core commerce functions: • User authentication and session management • Product and category services • Pricing and basic promotions • Cart and checkout logic • Order lifecycle management • Inventory updates • Payment gateway integration • Notification handling The backend must be designed to handle 500+ orders per day at launch and scale horizontally as demand increases. 6. Admin & Operations Platform A simple admin dashboard must be provided to support daily operations: • Product and category management • Pricing updates • Inventory management • Order monitoring and management • User management and role-based access • Basic reporting and data export The admin platform must be usable by non-technical teams. 7. Data Migration The MVP includes migration of: • Existing user accounts • Existing product catalog Historical order data migration is out of scope unless agreed separately. 8. Analytics & Monitoring The MVP must provide visibility into: • Daily order volume • Active users • Conversion funnel • App crashes and errors • Backend performance indicators This data should support operational monitoring and basic business decision-making. 9. Infrastructure & Reliability The platform must be deployed on cloud infrastructure with: • Separate development, staging, and production environments • Basic CI/CD pipeline • Monitoring and alerting • Secure access control • Cost-efficient scalability 10. Security & Compliance The MVP must meet baseline security standards: • Secure authentication • Encrypted data transmission and storage • Role-based access control • Regular data backups • Basic disaster recovery 11. Ownership & Documentation All source code, infrastructure access, and documentation ownership will be discussed one the agreement is signed. The MVP must include sufficient documentation to allow future enhancements or handover to another team. 12. Explicitly Out of Scope for MVP The following are intentionally excluded from the MVP: • Loyalty programs • Subscriptions or memberships • Advanced personalization • Multi-warehouse or complex fulfillment logic • Advanced analytics or BI tooling • Marketplace or vendor onboarding 13. Definition of MVP Success • The MVP will be considered successful if: • The new app launches smoothly • Existing users transition without friction • The platform reliably supports 500+ orders per day • Core operations run without manual workarounds • The system is ready for iterative enhancement