1.4.4.2. Deliverables

Deliverables:

• Stakeholder List & Roles
• Interview Notes / Persona Profiles
• Stakeholder Requirement Summary

In the first phase, the deliverables focus on understanding who the stakeholders are and their needs. You need to create a list of stakeholders and define their roles in the project. This includes collecting interview notes or profiles of potential users (personas) to better understand their perspectives. Finally, summarize the requirements gathered from stakeholders to ensure clear communication.

Imagine you're planning a birthday party. First, you would identify important people to invite (your stakeholders). Then, you would ask each person what their favorite food is (an interview) and write down their answers. Finally, you would create a list summarizing everyone's preferences to ensure the party meets their expectations.

Deliverables:

• User Stories Document
• Acceptance Criteria Sheet
• BRD or FRD (can be simplified)
• RTM in Excel or Table format

The second phase revolves around documenting the requirements that were elicited. This involves writing user stories that describe the functionality from the user's perspective, defining clear acceptance criteria for each story using the Gherkin format, and categorizing requirements into business, functional, and non-functional types. Additionally, creating a Requirement Traceability Matrix (RTM) helps track the requirements throughout the project.

Continuing with the birthday party analogy, this phase is like creating the menu and shopping list based on everyone’s food preferences. You would write down stories like 'As a guest, I want pizza so that I can enjoy my favorite food.' The acceptance criteria would specify details like 'Must have pepperoni and vegetarian options.' The RTM is similar to tracking ingredients needed to ensure everything aligns with guests' preferences.

Deliverables:

• Use Case Diagram
• Activity Diagram
• Low-fidelity Wireframes (for 2–3 key screens)

In this phase, the key deliverables include visual representations of how the system will work. A Use Case Diagram illustrates the interactions between users and the system for tasks like placing an order. An Activity Diagram showcases the step-by-step flow of a customer journey from browsing to checkout. Low-fidelity wireframes provide a basic layout of key screens to visualize the interface design.

Think of this phase as creating a map for your birthday party. The Use Case Diagram is like marking on the map who enters which room (guests interacting with the system), the Activity Diagram is like showing the path guests take from the living room (browsing) to the dining area (checkout), and wireframes are rough sketches of how the rooms are set up for food and games.

Deliverables:

• Test Case Table (ID, Steps, Expected Result)
• Defect Log (Optional, for extra challenge)

During the optional phase of test planning, the focus is on ensuring that the system works as expected. This involves creating test cases that outline specific actions to be taken and the expected outcomes. Additionally, maintaining a Defect Log helps identify and track any issues encountered during testing.

Imagine you're a chef testing recipes for the party. You would create a test case like 'Make a cake and check if it rises properly’ (steps and expected outcome). If something goes wrong, like the cake doesn’t rise, you note it down in your 'Defect Log' to fix it later.

Deliverables:

• Slide Deck (PDF or PPT)
• Optionally, record a 5-minute video walkthrough

The final phase focuses on summarizing and reviewing all the work done through a presentation. This includes creating a slide deck that outlines the business problem, the proposed solution, the user stories, the diagrams, and the next steps. Optionally, presenting the project through a recorded walkthrough can also be included to demonstrate the findings and engage the audience.

Think of this phase as creating a scrapbook of your birthday party planning. The slide deck summarizes everything you did, from the initial ideas to the final plans. If you make a video walkthrough, it's like inviting someone to watch how you organized everything from start to finish, sharing why you made certain choices and what you learned.

--