1.4.2.2. Deliverables

Deliverables:

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

In the first phase, the primary goal is to identify who the stakeholders are. Stakeholders can be anyone involved or affected, such as customers and staff. After identifying them, interviews or persona profiles are created to understand their needs. The deliverables include a list detailing each stakeholder's role, notes from the interviews, and a summary of their requirements.

Think of this phase like planning a party. You need to know who will be attending (stakeholders) and what they enjoy (requirements) before you can decide on the food and activities.

Deliverables:

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

In this phase, you convert the gathered requirements into user stories, which describe what the user needs the system to do. Each user story should have acceptance criteria that dictate when the user story is considered complete. The documents include a User Stories Document, an Acceptance Criteria Sheet, and a Requirement Traceability Matrix (RTM) to track the requirements throughout the project.

Imagine writing a recipe. Each ingredient (user story) must have a defined quantity (acceptance criteria) so that the dish is a success. The RTM is like a shopping list that helps ensure you have all necessary ingredients before you begin cooking.

Deliverables:

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

During the modeling phase, you visualize how the system will work. This includes creating diagrams like Use Case Diagrams to depict the interactions and Activity Diagrams to show customer flows. Wireframes are also created to provide a visual layout of key screens in the application.

This phase is similar to drawing a blueprint for a house before construction. You need to define where the rooms will be and how people will move through the space to ensure everything is functional and meets needs.

Deliverables:

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

This phase focuses on creating test cases that verify whether the system meets the defined requirements. Each test case outlines specific steps to execute and what the expected outcome should be. Additionally, a Defect Log can be maintained for tracking issues that arise during testing.

Think of it like preparing a checklist for a car service. You check each component (test case) to ensure everything works, and if something isn't right, you note it down (defect log) for further inspection.

Deliverables:

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

In the final phase, you summarize your findings and present the project. This includes creating a presentation that outlines the business problem, the proposed solution, user stories, diagrams, and next steps. You may also record a brief video to explain your project further.

This is much like giving a final presentation at school. You need to clearly communicate your project while also engaging your audience, ensuring they understand the importance of your work.

Final Output Checklist

• Stakeholder Summary
• BRD or FRD
• 5+ User Stories with Acceptance Criteria
• RTM
• 2 Diagrams (Use Case + Activity)
• Wireframes
• Test Cases (Optional)
• Final Presentation

The final output checklist ensures that you have all necessary deliverables compiled before completing the project. It prompts you to review whether you have a summary of stakeholders, a Business Requirement Document (BRD) or Functional Requirement Document (FRD), a set of user stories with associated acceptance criteria, the RTM, necessary diagrams, wireframes, and an optional set of test cases.

This checklist can be compared to a packing list for a vacation. You want to make sure you have everything you need before you leave, so you don’t forget any crucial items and have a successful trip.

--