Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Solution Overview

The document purpose is to discover the Business Needs of the project including business objectives, current problems and situations to solve, assumptions and constrains. The document should provide a clear idea on the project scope, requirements and success criteria.

Solution Background

Is this a brand new solution or a change? If change, why? What lead to the project initiation?

Business Need

What business problems should be addressed? What benefits should the project bring?

Solution Timelines

  • Solution Design: Click or tap to enter a date.
  • Development/Feature Freeze: Click or tap to enter a date.
  • QA Testing: Click or tap to enter a date.
  • Bug Fixes: Click or tap to enter a date.
  • UAT Testing: Click or tap to enter a date.
  • Go Live: Click or tap to enter a date.
  • Other Dates: Specify other key project dates

Communication & Responsibilities

BI Engineering Team

Team Member

Title

Role & Responsibility

 



Project Stakeholder Team

Team Member

Title

Role & Responsibility

 



Solution Scope/Deliverables

Specify list of expected deliverables to be included as part of solution. Ex:

  1. Sales Dashboard
  2. Marketing Dashboard
  3. Inventory Report

 Requirements (Repeat for each Deliverable)

Example Reports / Dashboard Mock Ups and Design

Provide any mock up or design screenshots

Target Audience

User Group

Business Need

Skill Set

User Story

 




Business Objective/Metrics

<< Identify business need/problem this dashboard/report should solve.>>

Interactivity

<< Specify an interactivity that is desired. Ex. Filtering with prompts, drill-downs, navigations to other Views etc.>>

Access/Security

Specify any data-level security between the different user groups. Specify any other security privileges between the user groups i.e. read access vs read and write access

Data Sources and Backend Architecture

<<Provide list of each data source to be used i.e. DB Name, Schema Name, Table Names>>

<<Provide any details on required ETL, dependencies, timliness of the load job, frequency of execution, or high level relationship diagrams of data structures.>>


  • No labels