1. Chapter 24: Real-time Business Case Challenge

To prepare and present a complete business analysis deliverable pack for a given case scenario by applying all techniques learned throughout the course.

The objective of this mini-project is to create a comprehensive business analysis deliverable pack. This requires students to utilize the various techniques they have learned in their coursework to demonstrate their understanding of business analysis. Essentially, students will be simulating a real-world project where they take on the role of a Business Analyst, which includes gathering requirements, documenting them, and preparing presentations.

Imagine you are planning a wedding. You need to gather details about the couple's preferences (requirements), document them in a checklist (deliverables), and later present everything to a wedding planner (presentation). This process mirrors the approach expected in the mini-project where planning and execution are crucial.

Project: Online Grocery Ordering System (Mini MVP) Problem Statement: A local grocery chain wants to launch a simple web-based system where customers can view available products, add them to a cart, place an order, and schedule home delivery.

This section presents a case scenario in which students are tasked with developing an online grocery ordering system. The problem statement outlines the basic functionality desired by the local grocery chain, which includes product viewing, cart management, order placement, and scheduling for home delivery. Understanding the problem statement is vital as it sets the context for all subsequent activities in the project.

Think of it as opening an online shop for groceries where you want to ensure that your customers can easily find what they need, place orders, and have items delivered to their homes, similar to how services like Instacart work.

Phase 1: Elicit Requirements

• Identify stakeholders (e.g., customers, store staff, delivery team, admin)
• Conduct 2–3 mock interviews or prepare stakeholder personas
• Create a stakeholder matrix (with RACI if possible) Deliverables:
• Stakeholder List & Roles
• Interview Notes / Persona Profiles
• Stakeholder Requirement Summary

In this phase, the focus is on eliciting requirements. This involves identifying various stakeholders who will interact with the online grocery system, such as customers, staff, and delivery personnel. Students will conduct mock interviews or create personas to better understand the needs of these stakeholders. A stakeholder matrix helps visualize roles and responsibilities, which is crucial for clear communication. The deliverables include a list of stakeholders, notes from interviews or persona profiles, and a summary of the requirements gathered from these sources.

Imagine launching a new app for fitness enthusiasts. You would need to identify users (gym-goers, trainers, nutritionists) and find out their preferences and needs through interviews. This step ensures the app fulfills its purpose effectively.

Phase 2: Document Requirements

• Write 5–8 user stories using INVEST format
• Define acceptance criteria using Gherkin (Given–When–Then)
• Categorize requirements: business, functional, non-functional
• Create a Requirement Traceability Matrix (RTM) Deliverables:
• User Stories Document
• Acceptance Criteria Sheet
• BRD or FRD (can be simplified)
• RTM in Excel or Table format

In Phase 2, students shift to documenting the requirements. They need to write user stories that capture the needs of the users, ensuring that these stories are crafted in the INVEST format (Independent, Negotiable, Valuable, Estimable, Small, Testable). Next, acceptance criteria are defined, which specify conditions under which a product is acceptable to its stakeholders. Requirements are categorized into business, functional, and non-functional for clear understanding. A Requirement Traceability Matrix (RTM) is also created to track the lifecycle of requirements from inception to implementation. The deliverables from this phase include various documents summarizing these points.

If you were developing a home automation app, you might outline user stories such as 'As a user, I want to control lights remotely.' Each user story will have acceptance criteria to ensure it meets user expectations, just like drafting a recipe before cooking.

Phase 3: Model the System

• Draw Use Case Diagram for order placement
• Draw Activity Diagram for customer flow (browse → checkout)
• Create Wireframes or Mockups (use Draw.io, Balsamiq, or Figma) Deliverables:
• Use Case Diagram
• Activity Diagram
• Low-fidelity Wireframes (for 2–3 key screens)

Phase 3 focuses on modeling the system to visualize how it will work. A Use Case Diagram shows the interactions between users and the system during order placement, outlining essential functions. The Activity Diagram illustrates the flow of actions a customer goes through from browsing to checkout, highlighting critical touchpoints. Wireframes or mockups are low-fidelity representations of the system’s user interface, allowing stakeholders to visualize design concepts. Deliverables include the diagrams and wireframes created during this phase.

Think of these diagrams as blueprints for a house: they help everyone understand what the finished product will look like and how different areas will be used, whether it's showing how a room flows into another or how to move through a store.

Phase 4: Test Planning (Optional)

• Write 3–5 test cases
• Map them to requirements in RTM
• Identify a sample defect (if any) from testing Deliverables:
• Test Case Table (ID, Steps, Expected Result)
• Defect Log (Optional, for extra challenge)

In Phase 4, testing is introduced as an optional step to ensure that the system functions as intended. Students will write test cases that provide specific scenarios to validate whether the requirements are met based on the previously created user stories and acceptance criteria. These test cases will be mapped to the RTM to track coverage. A defect log can also be maintained to document any issues encountered during testing. The deliverables consist of a table outlining the test cases and an optional defect log.

This phase is akin to a dress rehearsal before a big show. Just like actors run through their lines to ensure everything works smoothly, the testing phase verifies that all parts of the online grocery system function correctly before the actual launch.

Phase 5: Presentation & Review

• Create a summary presentation (6–8 slides max)
• Include business problem, solution scope, user stories, diagrams, and next steps
• Present your project to peers or mentor (live or recorded) Deliverables:
• Slide Deck (PDF or PPT)
• Optionally, record a 5-minute video walkthrough

In the final phase, students prepare to present their work. The presentation serves as a summary of the entire project, including the initial business problem, the proposed solution, key user stories, diagrams, and the next steps for implementation. Presenting can be done live in front of peers or recorded for review. The primary deliverables are a concise slide deck and potentially a video walkthrough, aimed at showcasing not just the analysis but also the student's understanding of the project.

Consider this phase as pitching a new restaurant concept to investors. You would present a clear and engaging slideshow summarizing your business idea, including your menu (solution scope), customer feedback (user stories), and marketing strategy (next steps) to demonstrate your readiness and passion.

--