1.4. Phases & Deliverables

✅ Phase 1: Elicit Requirements 🎯 Tasks: ● 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 the first phase, the goal is to gather the necessary information from various stakeholders involved in the project. This involves identifying who the stakeholders are — these could be customers, store staff, the delivery team, and administrative personnel. It's also important to conduct a few mock interviews or develop personas that represent these stakeholders to better understand their needs. Creating a stakeholder matrix, potentially using a RACI framework (Responsible, Accountable, Consulted, Informed), helps clarify roles and responsibilities. The deliverables for this phase include a stakeholder list detailing their roles, notes from interviews or profiles of the personas, and a summary of the requirements outlined by the stakeholders.

Imagine planning a community event, such as a neighborhood barbecue. First, you'd identify who needs to be involved: the residents, local businesses providing food, and volunteers helping with setup and cleanup. Then, you might conduct mock discussions with a few neighbors or create profiles for them to understand their preferences for food and activities. Once you gather all the feedback, you would write down the ideas and suggestions, ensuring everyone knows their role in making the event successful.

✅ Phase 2: Document Requirements 🎯 Tasks: ● 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

Phase 2 focuses on documenting the requirements that were gathered in Phase 1. This involves writing user stories that capture what users want to achieve and following the INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, and Testable). Each user story needs acceptance criteria defined in Gherkin format, structured as 'Given-When-Then' to clarify conditions for success. Requirements need to be categorized into business, functional, and non-functional areas to ensure comprehensive understanding. Finally, a Requirement Traceability Matrix (RTM) is created to track the requirements throughout the project. Deliverables include a document of user stories, a sheet with acceptance criteria, a Business Requirement Document (BRD) or Functional Requirement Document (FRD), and the RTM in a structured format.

Think of documenting requirements like creating a recipe for a new dish. You start by writing down the ingredients (user stories) that detail what you need and then ensure the instructions (acceptance criteria) clearly explain how to combine them to get the desired meal. You might categorize ingredients into various types like spices (functional) and appliances needed (non-functional). Finally, a checklist (RTM) helps you ensure you have everything covered before you start cooking.

✅ Phase 3: Model the System 🎯 Tasks: ● 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)

In this phase, the focus shifts to creating models that visualize how the system will function. First, a Use Case Diagram is drawn to illustrate how users will interact with the system, such as placing an order. Next, an Activity Diagram outlines the step-by-step process a customer follows while browsing products and checking out. Finally, wireframes or mockups are created for the user interface of the key screens using design tools. The deliverables for this phase include the Use Case Diagram, Activity Diagram, and low-fidelity wireframes showcasing the layout of the product pages and checkout process.

Creating system models is like planning the layout of a new store. The Use Case Diagram is similar to a blueprint that shows where the check-out counters will be and who will use them. The Activity Diagram is akin to mapping out the customer journey through the store, from entering to selecting items and heading to the register. Lastly, wireframes are like sketches of how each aisle will be arranged and what signs you'll put up, helping everyone visualize how the store will flow before it's built.

✅ Phase 4: Test Planning (Optional) 🎯 Tasks: ● 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)

Phase 4 is focused on preparing for testing the system, although it is optional. This involves writing a few test cases that define how to verify whether the system meets the defined requirements. Each test case should detail the steps required to execute the test and the expected results. These test cases are then mapped to the requirements in the RTM to ensure coverage. If any defects arise during testing, such as a bug or a failure to meet a requirement, these need to be logged as well. Deliverables include a test case table providing an organized way to track testing procedures and a log for any defects found.

Consider testing like a dress rehearsal before a theater performance. The test cases are like scripts that outline what actors should do on stage to make sure every scene goes smoothly. Mapping the tests to requirements is like checking your scene transitions to ensure they're in order. If an actor forgets a line or a prop isn’t in the right place, those issues are logged just like defects found during testing. This ensures the final performance is polished and error-free.

✅ Phase 5: Presentation & Review 🎯 Tasks: ● 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

The final phase involves presenting the work completed in the previous phases. A summary presentation should be created consisting of 6 to 8 slides that encapsulate the main elements of the project, including the business problem being addressed, the proposed solution, user stories, diagrams created, and the next steps in the process. This presentation is then delivered to peers or mentors, either live or in a recorded format. The deliverables here include the slide deck in a PDF or PowerPoint format, and optionally, a video walkthrough providing an audiovisual explanation of the project.

Think of this final phase like presenting your science fair project. You create a series of poster boards (slides) that detail your hypothesis (problem), explain your experiment (solution scope), and showcase your findings (user stories and diagrams). When it's time to present, you would stand in front of classmates and teachers, explaining your project and answering questions, making sure to highlight how your experiment contributes valuable insights. Your final slide deck is your organized display, and a video walkthrough could be like recording yourself explaining your project for those who can’t attend the event.

--