Please enable JavaScript.

Coggle requires JavaScript to display documents.

BUSINESS INTELLIGENCE - Coggle Diagram

- - - - Completeness
      - Consistency
      - Conformity
      - Accuracy
      - Redundancy
      - Integrity
      - Timeliness
  - - - Outcome
      - Project
      - Service
  - - - Confirmation bias occurs when an analyst is either exploring or trying to interpret data to confirm with their prior beliefs.
    - - occur when dealing with samples which are not representative of the entire population
    - - sociocultural prejudices and beliefs are mirrored into systematic processes.
    - - Averages are a great way to hide anomalies and outliers while skewing our observation.
- - - - The executive team
        
        strategic and operational leadership to the company
      - The customer-facing team
        
        includes anyone in an organization who has some level of interaction with customers and potential customers
      - The data science team:
        
        includes data analysts, data scientists, and data engineers.
- - - - Business problem: What is the primary question to be answered or problem to be solved?
      - Stakeholders: Who are the major stakeholders of this project, and what are their job titles?
      - Stakeholder usage details: How will the stakeholders use the BI tool?
      - Primary requirements: What requirements must be met by this BI tool in order for this project to be successful?
    - - What questions must be answered before starting this project?
      - What does the BI team need to know before starting this project?
      - What are the questions that must be answered/problems that must be solved by this project?
      - What datasets are considered important to this project?
      - Who should have access to the dashboard? Will the entire dashboard be visible to all stakeholders?
  - - - Purpose: Briefly describe why this project is happening and explanation of why the company should invest its resources in it.
      - Purpose: Briefly describe why this project is happening and explanation of why the company should invest its resources in it.
      - Stakeholder requirements: List the established stakeholder requirements, based on the Stakeholder Requirements Document. Prioritize the requirements as: R - required, D - desired, or N - nice to have.
      - Success criteria: Clarify what success looks like for this project. Include explicit statements about how to measure success. Use SMART criteria.
      - User journeys: Document the current user experience and the ideal future experience.
      - Assumptions: Explicitly and clearly state any assumptions you are making.
      - Compliance and privacy: Include compliance, privacy, or legal dimensions to consider.
      - Accessibility: List key considerations for creating accessible reports for all users. Who needs to access this feature? How are they viewing and interacting with it?
      - Roll-out plan: Briefly describe the expected scope, priorities and timeline. Consider at what points during the rollout will measurements be made to determine whether the feature is performing as expected? Is there a rollback plan and timeline if this feature does not meet its intended goals?