Learn
Games

1.4.4.2 - Deliverables

Interactive Audio Lesson

Listen to a student-teacher conversation explaining the topic in a relatable way.

Eliciting Requirements

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

To kick off our project, we need to elicit requirements effectively. Who can tell me why understanding stakeholders is crucial?

Student 1
Student 1

Because they have the information we need to build our system, right?

Teacher
Teacher

Exactly! Remember, we use the acronym RACI to clarify roles: Responsible, Accountable, Consulted, and Informed. This helps us understand who is involved.

Student 2
Student 2

Can we use personas instead of just interviews?

Teacher
Teacher

Great point! Creating persona profiles can also help visualize the user needs. Can anyone summarize what deliverables we produce in this phase?

Student 3
Student 3

We create a stakeholder list, interview notes, and a stakeholder requirement summary.

Teacher
Teacher

Yes! Well done. The clarity in our documentation sets the foundation for the next phases.

Student 4
Student 4

What if the stakeholders have conflicting requirements?

Teacher
Teacher

A great question! It's our job to negotiate and prioritize their needs fairly. Let's remember that our task is about delivering value and clarity.

Teacher
Teacher

To wrap up, eliciting requirements is critical; we gather, clarify, and document needs. We'll move on to documenting these requirements next.

Documenting Requirements

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Now that we've gathered requirements, how do we document them effectively?

Student 1
Student 1

We write user stories in the INVEST format!

Teacher
Teacher

Right! Can anyone explain what INVEST stands for?

Student 2
Student 2

Independent, Negotiable, Valuable, Estimable, Small, and Testable!

Teacher
Teacher

Excellent! Additionally, who can tell me how we define acceptance criteria?

Student 3
Student 3

Using Gherkin's Given-When-Then format!

Teacher
Teacher

Correct! This format helps outline specific outcomes tied to user stories. What do we produce in this phase?

Student 4
Student 4

User stories document, acceptance criteria sheet, and a requirement traceability matrix!

Teacher
Teacher

Good job! Documenting clearly not only assists in the development but also aids testing later on.

Teacher
Teacher

To summarize, we write user stories to maintain clarity, and establish acceptance criteria to ensure requirements meet user needs. Let's proceed to modeling our system.

Modeling the System

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

In modeling the system, we primarily focus on creating diagrams and wireframes. Who can tell me the significance of using diagrams?

Student 1
Student 1

Diagrams help to visualize processes and understand user interactions with the system!

Teacher
Teacher

Exactly right! For our project, we should create a use case diagram and an activity diagram. What do these diagrams depict?

Student 2
Student 2

The use case diagram shows the interactions between users and the system, while the activity diagram outlines the flow of actions!

Teacher
Teacher

Perfect! Additionally, we can create low-fidelity wireframes for initial screen designs. Why do we start with low-fidelity?

Student 3
Student 3

They are quicker to produce and easy to adapt based on feedback!

Teacher
Teacher

Very insightful! Visuals are vital for development and serve as a reference throughout the project lifecycle.

Teacher
Teacher

Recapping, our task in system modeling involves creating diagrams to represent user functionality and initial wireframes to visualize the design. Next, we’ll touch on test planning.

Test Planning

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Test planning is crucial for quality assurance. What should our approach include?

Student 1
Student 1

We need to write test cases that verify if the requirements are met!

Teacher
Teacher

Correct! What format should our test cases adhere to?

Student 2
Student 2

It should include ID, steps, and expected results!

Teacher
Teacher

Exactly, and we can also map these test cases back to our requirements using the requirements traceability matrix. Can someone explain its purpose?

Student 3
Student 3

It ensures that all requirements are tested and that nothing is missed!

Teacher
Teacher

Exactly! While optional, identifying defects during testing adds great value. To sum up, the test planning phase gives us a clear strategy for verifying our deliverables and ensuring quality.

Presentation & Review

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Lastly, we must present our work effectively. What are key elements to include in our presentation?

Student 1
Student 1

The business problem, our proposed solution, and visuals like diagrams!

Teacher
Teacher

Well noted! How many slides should we aim for?

Student 2
Student 2

Six to eight slides maximum!

Teacher
Teacher

That's right—we want to keep it concise. Additionally, what’s a good way to engage our audience?

Student 3
Student 3

Using interactive elements like questions or inviting feedback!

Teacher
Teacher

Absolutely! Finally, recording a summary video can enhance our presentation. In summary, our presentation should focus on clarity and engagement to convey our findings effectively.

Introduction & Overview

Read a summary of the section's main ideas. Choose from Basic, Medium, or Detailed.

Quick Overview

The section details the comprehensive deliverables required for a mini-project in business analysis, simulating a real-world BA project lifecycle.

Standard

This section outlines the necessary deliverables for an end-to-end mini-project that includes requirements elicitation, documentation, modeling, and presentation. It emphasizes the importance of creating detailed outputs that represent real-world business analysis work.

Detailed

In Chapter 24's section on Deliverables, learners are guided through the necessary outputs that a Business Analyst (BA) must produce for an Online Grocery Ordering System project. The phase-oriented structure includes five key phases: eliciting requirements, documenting requirements, modeling the system, test planning, and presentation & review. Each phase has specific tasks and deliverables such as stakeholder matrices, user stories, diagrams, and presentation slides, ensuring full coverage of the BA lifecycle. The section emphasizes practical application, reflection, and presentation as core components of the learning experience.

Audio Book

Dive deep into the subject with an immersive audiobook experience.

Phase 1: Elicit Requirements

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Deliverables:

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

Detailed Explanation

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.

Examples & Analogies

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.

Phase 2: Document Requirements

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Deliverables:

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

Detailed Explanation

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.

Examples & Analogies

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.

Phase 3: Model the System

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Deliverables:

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

Detailed Explanation

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.

Examples & Analogies

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.

Phase 4: Test Planning (Optional)

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Deliverables:

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

Detailed Explanation

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.

Examples & Analogies

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.

Phase 5: Presentation & Review

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Deliverables:

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

Detailed Explanation

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.

Examples & Analogies

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.

Definitions & Key Concepts

Learn essential terms and foundational ideas that form the basis of the topic.

Key Concepts

  • Business Analysis Deliverables: Key outputs required in each phase of business analysis.

  • User Stories: Features written from a user perspective guiding functionality.

  • Models and Diagrams: Visual aids that illustrate system functionality and user interaction.

  • Testing and Validation: Ensures that requirements are met through systematic exploration.

  • Presentation Skills: Critical for effectively communicating findings and engaging stakeholders.

Examples & Real-Life Applications

See how the concepts apply in real-world scenarios to understand their practical implications.

Examples

  • A stakeholder list might include customers, store staff, and delivery team members with specified roles.

  • An example user story could be: 'As a customer, I want to view products so that I can order my groceries efficiently.'

  • A use case diagram may depict actors like 'Customer' and 'Admin' with their interactions with the system functionalities.

Memory Aids

Use mnemonics, acronyms, or visual cues to help remember key information more easily.

🎵 Rhymes Time

  • When gathering needs, please take heed, A stakeholder's voice is what we need.

📖 Fascinating Stories

  • Imagine being a customer shopping online. You want everything easy and fine. You say what you need, and the BA takes note, crafting stories that help the team build your hope.

🎯 Super Acronyms

Remember USER for user stories

  • Understand
  • Simplify
  • Evaluate
  • and Review.

E-L-M for the key phases

  • Elicit
  • Document
  • Model.

Flash Cards

Review key concepts with flashcards.

Glossary of Terms

Review the Definitions for terms.

  • Term: Elicit

    Definition:

    To gather information or requirements from stakeholders.

  • Term: User Stories

    Definition:

    Short, simple descriptions of features from the user's perspective.

  • Term: Use Case Diagram

    Definition:

    A visual representation that shows interactions between users and the system.

  • Term: Activity Diagram

    Definition:

    A visual representation of workflows, depicting the sequence of actions.

  • Term: Requirement Traceability Matrix (RTM)

    Definition:

    A document that links requirements to their corresponding test cases.

  • Term: Acceptance Criteria

    Definition:

    Conditions that a product must satisfy to be accepted by stakeholders.