Executive Summary

This report provides a comprehensive overview of the “App Refresh” e-commerce project undertaken in collaboration with IT Career Switch. It covers the project’s objectives, roadmap and prioritization, sprint planning, resource management, communications strategy, risk management approach, sprint highlights, challenges encountered, and recommendations for future phases.

1. Project Overview

The App Refresh initiative aims to modernize Bargains Extra’s mobile and web applications by enhancing payment flexibility, improving UX/UI, integrating with backend systems, and bolstering information security. The project is structured into six two-week sprints, targeting a Minimum Viable Product (MVP) by the end of Sprint 6.

Key Deliverables:

• Multi-payment methods (e.g., card, in-app payments)
• Enhanced UX/UI with responsive design
• Real-time inventory visibility via warehouse integration
• CRM integration readiness
• Information security compliance and backup processes

2. Objectives & Scope

• Primary Goal: Deliver an MVP “App Refresh” that supports multiple payment options, seamless navigation, and robust security.
• Scope Inclusions:
  • Payment feature implementation
  • UX/UI redesign
  • Backend integrations (warehouse, CRM)
  • Customer-centric features (favourites, back-in-stock alerts)
• Scope Exclusions (for initial phases):
  • Full CRM feature set (deferred due to capacity constraints)
  • Expanded customer hub FAQs beyond core transactional flows

3. Roadmap & Prioritization

Based on Bargains Extra’s strategic objectives, features were prioritized to maximize customer convenience and quick ROI:

1. Pay on App, Collect In-Store
2. Browse All Products
3. Account Creation & Favorites
4. Real-Time Warehouse Integration
5. Back-In-Stock Notifications
6. Multiple Payment Types
7. Returns & Fault Reporting
8. CRM Integration (post-MVP)
9. Customer Hub FAQs (low priority)

Next Projects (post-App-Refresh):

• Email Receipts (P006)
• Social Media Management Tool (P007)
• Customer Loyalty Programme (P002)

4. Sprint Planning & Goals

Sprint Goal (Sprint 1):

Implement payment feature, address information security compliance, and finalize core UX/UI designs to enhance user experience.

Sprint Breakdown:

• Sprint 1: Payment module MVP, security requirements analysis, UI mockups
• Sprint 2: Expand payment options, begin integration testing, refine designs
• Sprint 3–6: Complete warehouse and CRM hookups, beta release, user acceptance testing

5. Resource Management

To align workload with capacity, resource allocation and variance were closely monitored:

• Capacity Constraints:
  • Two developers lacked critical software licenses, delaying payment backlog items.
  • Test Lead scheduled leave in Sprint 3, impacting testing cadence.
  • UI/UX team overallocation (75% vs. agreed 50%) strained design capacity.
• Action Steps:
  • Re-balance UI/UX assignments via time-blocking.
  • Expedite license procurement to unblock development.
  • Cross-train team members for testing during leave periods.

Key questions for continuous improvement include estimation accuracy, resource re-allocation, and process refinements for variance tracking.

6. Communications Strategy

Effective stakeholder engagement was maintained through:

• Weekly Team Meetings & Bi-Weekly Stakeholder Updates using Microsoft Teams and Jira for transparency.
• Structured Email Updates:
  • Progress reports, challenges surface, and upcoming milestones communicated to the Chief of Staff and leadership.
  • Example email highlights Sprint status, resource issues (licenses, leave), and upcoming beta readiness by end of Sprint 4.
• Open Feedback Culture: Encouraged real-time input via Slack channels and retrospective sessions.

7. Risk Management

A proactive risk-management approach was applied to anticipate and mitigate disruptions:

• Key Risks Identified: License shortfalls, resource leave, scope creep (CRM requests), estimation inaccuracies.
• Mitigation Plans:
  • License procurement timelines tracked in the Risk Log.
  • Backup test resources identified for planned absences.
  • Change-control process enforced for scope additions.
  • Regular estimation calibration workshops.

8. End of Sprint Highlights

The End of Sprint report (Highlight Report) summarizes accomplishments, challenges, and next sprint priorities:

• Achievements: Payment feature prototype delivered; security audit passed initial review; UX wireframes completed.
• Challenges: Licensing delays causing backlog slippage; Test Lead absence planning; UI/UX bandwidth constraints.
• Next Steps: Finalize multiple payment methods; onboard temporary test support; prepare beta demo for leadership review at Sprint 4 close.

9. Challenges & Mitigations

10. Recommendations & Next Steps

1. Complete MVP & Beta Release: Target end of Sprint 4 for leadership demo and UAT.
2. Resource Stabilization: Secure licenses, confirm backfill for testing, and rebalance UI/UX workloads.
3. Scope Control: Formalize change-request process to protect sprint commitments.
4. Post-MVP Roadmap Execution: Initiate Email Receipts, Social Media Tool, and Loyalty Programme as per prioritization.
5. Continuous Improvement: Hold estimation workshops, refine risk-log entries, and standardize retrospective actions across sprints.