1.4.4.1. Tasks

🎯 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 this phase, the goal is to gather all necessary information from individuals involved in or impacted by the project. The first task is to identify who the stakeholders are, which can include customers, grocery store staff, the delivery team, and administrative personnel. The next step involves conducting mock interviews or preparing personas that represent the various stakeholders to better understand their needs and expectations. Lastly, creating a stakeholder matrix, which may use RACI (Responsible, Accountable, Consulted, Informed) principles, helps to clarify the roles and responsibilities of each stakeholder in relation to the project.

Imagine you are throwing a birthday party. Before planning, you need to consider who will be involved—friends, family, and even the venue staff. You might talk to your friends to understand what kind of activities they'd enjoy (the mock interviews) and write down their preferences. Then, you create a list indicating who is responsible for what—who brings snacks, who handles decorations, and so on, similar to the stakeholder matrix.

🎯 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

During this phase, the focus shifts to documenting the gathered requirements in a clear and structured manner. User stories are written, which should follow the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). Additionally, each user story should have acceptance criteria defined in Gherkin format (Given-When-Then), which helps to specify the conditions for satisfying the user stories. Requirements are categorized into business, functional, and non-functional to ensure comprehensive understanding and coverage. Lastly, a Requirement Traceability Matrix (RTM) captures the relationship between requirements and other deliverables, ensuring nothing is overlooked.

Think of this phase like writing a recipe for a cake. Each user story is akin to a specific ingredient, such as flour or sugar. You need to ensure that each ingredient is measured correctly (like defining acceptance criteria). Additionally, you categorize ingredients into dry and wet; this is similar to how requirements are categorized into business and functional. Finally, the RTM is like a checklist to ensure you gather all ingredients needed for your cake before you start baking.

🎯 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 is on visualizing the system through diagrams and models. A Use Case Diagram is created to represent how users will interact with the order placement feature, highlighting the relationships between different actors (users) and the system. An Activity Diagram illustrates the workflow of a customer as they navigate through the site from browsing to checkout, showcasing all possible actions. Finally, Wireframes or Mockups are designed to provide a visual layout of the key screens, helping stakeholders visualize the final product before it is developed.

Imagine you're designing a new house. The Use Case Diagram is like a blueprint showing where different rooms (like the kitchen, living room) are and how people will move between them. The Activity Diagram represents the journey of a person from entering the house to sitting down for dinner. Finally, Wireframes are like sketches of your house, outlining what each room will look like before you actually bring in the furniture.

🎯 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)

This optional phase involves preparing for testing the developed system to ensure it functions as intended. Writing test cases, which outline specific scenarios to verify each requirement, is essential. These test cases are then mapped to the requirements in the RTM to ensure every requirement has corresponding tests. If any defects are found during testing, they should be documented in a defect log for further analysis and resolution.

Think of this phase as quality control in a factory. Just as a factory might set up tests for each product to check if it's made correctly (test cases), the company will track any defects found during testing so they can be corrected. For instance, if a car leaves an assembly line with a scratch, it’s noted in a defect log to ensure it gets fixed before the car is sold.

🎯 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 is about summarizing and presenting all the work that has been completed. The presentation should encapsulate the business problem, the proposed solution, the user stories, essential diagrams, and the next steps moving forward. This not only demonstrates what has been accomplished but also provides an opportunity for feedback and discussion. Deliverables include a succinct slide deck and an optional video walkthrough that showcases the key aspects of the project.

Consider this phase like summarizing a book report. You need to condense the story, main themes, and character analyses into a few clear slides that can be easily presented to classmates. A teacher might ask for a quick video to explain your thoughts on the book. The summary captures both the main points and leaves space for classmates to ask questions about your insights.

--