Data Analytics With Tableau Project Knowledge Session - 2

Knowledge Session Overview

Introduction to the Knowledge Session

• Participants are encouraged to invite friends to join the session for a comprehensive learning experience.

• The speaker confirms that their voice is audible and requests confirmation from participants.

• Emphasis on the importance of knowledge sessions, which will cover essential templates and documentation needed for upcoming projects.

Project Phases Discussion

• The session will focus on two main phases: Ideation Phase and Requirement Analysis.

• In Phase One, three documents must be completed: Problem Statement, MTH (Methodology), and Streaming. In Phase Two, four documents are required: Customer Journey Map, Data Flow Diagram, Solution Requirements, and Technology Style.

Session Agenda and Announcements

Key Announcements

• Participants do not need to take notes as explanations will be provided during the session. All necessary details will be shared later via email by Monday evening.

• There will be no quiz today; however, Quiz Number Three is scheduled for Tuesday with a grand assessment next Saturday (27th). Details regarding project access will also be communicated by Monday evening.

Project Development Process

Overview of Project Development Steps

• The speaker outlines a structured project development process consisting of several key steps including prerequisites setup and configuration requirements for tools like Tableau Desktop.

• Each step in the process is designed to guide participants through defining problem statements, ideation phases, requirement analysis, technical architecture design milestones, project planning, development processes, functional testing, performance testing, monitoring reviews, and approvals before final submission via GitHub links.

Design Thinking in Solution Development

Importance of Design Thinking

• The session emphasizes using design thinking as a creative problem-solving approach that focuses on understanding user needs while developing solutions tailored to those needs effectively.

• A quote from Albert Einstein highlights spending more time defining problems than solving them; this principle underlines the significance of thorough problem statement formulation before seeking solutions.

Stages of Design Thinking Process

1. Empathize: Engage with users to understand their experiences and motivations.

2. Define: Clearly articulate the problem statement from various perspectives.

3. Ideate: Generate ideas without constraints.

4. Prototype: Create tangible representations of ideas.

5. Test: Evaluate prototypes based on user feedback for iterative improvement.

Each stage plays a crucial role in ensuring that solutions developed are both practical and aligned with user expectations while being economically viable within technological limits.

Empathy Mapping Techniques

Utilizing Empathy Maps

• Empathy maps serve as tools for capturing insights about users' thoughts and feelings related to specific projects or products they interact with.

• Participants are guided on how to create empathy maps by engaging with users directly through observations or interviews.

Example Scenario

• An example scenario illustrates how an individual might navigate purchasing decisions such as buying a TV—considering factors like brand preferences or product features—demonstrating how empathy mapping can clarify user motivations.

This structure provides clarity around each topic discussed during the knowledge session while linking back directly to relevant timestamps for further exploration if needed!

How to Define a Problem Statement and Brainstorm Ideas

Defining a Problem Statement Template

• A problem statement template is introduced, emphasizing the need for clarity in defining project goals.

• Participants are instructed to fill out their details such as team ID and project name while referring to the provided template.

• A free template link is shared, encouraging users to accept cookies and sign up before using it.

• Users must provide two scenarios based on the problem statement, reinforcing the importance of context in problem definition.

• The process involves selecting the type of work participants want to engage in, with options available for further customization.

Filling Out the Template

• After logging in, users should open and fill out the template, taking screenshots for documentation purposes.

• An example is provided on how to complete the table within the template effectively.

• Participants are reminded that they need to capture all perspectives related to their roles as customers when filling out this section.

• The focus remains on defining what each participant aims to achieve through their contributions in relation to others' ideas.

• Emphasis is placed on submitting completed templates along with any necessary screenshots.

Transitioning to Brainstorming Ideas

• The session transitions into brainstorming ideas and prioritizing them based on defined obstacles or problems identified earlier.

• Each participant will contribute different ideas; collaboration is key in gathering diverse thoughts for effective solutions.

• Rules of brainstorming include encouraging wild ideas without judgment and building upon others' suggestions for enhanced creativity.

• Focus should remain on quantity over quality initially; generating numerous ideas can lead to more refined solutions later on.

Understanding Prototyping and MVP Concepts

What is an MVP?

• An MVP (Minimum Viable Product) concept is introduced as a way of selecting feasible ideas from a pool of generated concepts.

• Participants are encouraged to think about technological needs, time requirements, costs involved, and resources needed for implementation during prototyping discussions.

• Real-life analogies like building a car illustrate that projects require foundational elements before scaling up.

• Emphasis is placed on understanding that one cannot build complex systems without first mastering simpler components.

Iterative Process of Prototyping

• Testing becomes crucial after initial prototypes are developed; it helps refine products based on user feedback.

• The iterative process allows teams to return back through phases if new insights arise during testing stages.

• Continuous learning about user interactions informs future iterations of product development.

Requirement Analysis: Functional vs Non-functional Requirements

Understanding Functional Requirements

• Functional requirements define what a product must do; they outline features developers must implement for user tasks completion.

• Examples include authentication processes or external interfaces necessary for system functionality.

Exploring Non-functional Requirements

• Non-functional requirements address usability aspects like security measures ensuring data protection against unauthorized access.

• Usability focuses on how easy it will be for users unfamiliar with technology (e.g., language barriers).

Data Flow Diagrams: Visualizing System Processes

Introduction to Data Flow Diagrams

• Data flow diagrams visually represent how data moves through systems; they help clarify input-output relationships within projects.

• Components include external entities (users/systems), processes depicted by rounded rectangles, data stores where information resides, and directional arrows showing data movement.

Creating Effective Data Flow Diagrams

• Clear guidelines are provided regarding creating these diagrams accurately reflecting system operations while capturing essential details like milestones or user stories associated with specific tasks involved throughout project execution.

Customer Journey Mapping Explained

Understanding Customer Journey Maps

• A customer journey map is a visual representation of the steps a customer takes when interacting with a product or service, from signing up to actual usage.

• It outlines all stages of the customer's experience, including their thoughts and feelings at each step, which helps in understanding their overall experience.

• The map captures various experiences such as registration, searching for products, delivery experiences, and more.

• This mapping technique aims to highlight how customers perceive the product and identify convenient parts of the process for them.

• Benefits include improving customer onboarding processes and comparing expected versus actual customer experiences.

Components of a Customer Journey Map

• The customer journey map consists of three main sections: Registration, Onboarding, and First Session.

• Registration refers to the sign-up process; Onboarding involves teaching customers how to use the product; First Session indicates when customers start using it actively.

• Each section includes action points like touchpoints (where customers interact with the product), thoughts (what they are thinking), feelings (emotions experienced), ownership (who is responsible for each stage), and opportunities for improvement.

Analyzing Customer Experience

• Actions represent what customers do during their journey. For example, connecting accounts or choosing plans reflects user actions within the platform.

• Touchpoints indicate where interactions occur—like landing pages or dashboards—and help assess ease of access and usability from a customer's perspective.

• Feelings capture emotional responses throughout different stages—whether happy, confused, or neutral—which can inform improvements in service design.

Benefits of User Stories in Agile Development

Introduction to User Stories

• User stories are concise descriptions that express activities users want to achieve within a system. They focus on user needs rather than tasks alone.

• A typical format includes identifying who the user is ("As a..."), what they want ("I want..."), and why it matters ("So that...").

Importance of User Stories

• They keep teams focused on solving problems rather than just completing tasks. This approach fosters collaboration among team members towards achieving common goals.

• Completing user stories provides motivation by creating a sense of achievement after finishing specific activities.

Technical Requirements Template Overview

Creating Technical Architecture

• The technical architecture template requires detailing components like user interfaces and application logic used in projects.

• Users must specify technologies employed in development—such as databases or frameworks—to ensure clarity on project requirements.

Key Elements in Technical Documentation

• Important aspects include security features, scalability considerations, performance metrics (e.g., speed), and whether tools are open-source or proprietary.