Reporting roadmap for

Your client

The current date

Prepared by:
Your name & your teams names go here

Prepared for & in collaboration with:

Put your stakeholders here
<CLIENT NAME> Roadmap for Data & Reporting

Contents

1 Company profile ....................................................................................................... 3

1.1 History and notable achievements ............................................................................................................ 3
1.2 Big data, BI, and AI strategy & execution ................................................................................................ 3
1.3 Data migration ............................................................................................................................................ 3
1.4 Timeline........................................................................................................................................................ 3

2 Our understanding of the current situation and objectives ................................ 3

2.1 Definitions.................................................................................................................................................... 3
2.2 Data sources................................................................................................................................................. 3
2.3 ETL process................................................................................................................................................... 3
2.4 Data validation & documentation ............................................................................................................. 3
2.5 Networking .................................................................................................................................................. 4
2.6 Reporting ..................................................................................................................................................... 4

3 Proposed solution .................................................................................................... 5

3.1 Phase 1: Remediation ................................................................................................................................. 5
3.2 Phase 2: UAT & release ............................................................................................................................... 6
3.3 Phase 3: Ongoing operational optimization ............................................................................................ 6

2
<CLIENT NAME> Roadmap for Data & Reporting

1 Company profile
This is where your profile / team’s profile will go.

1.1 History and notable achievements

Any relevant background you have goes here.

1.2 Big data, BI, and AI strategy & execution

Methodological detail

1.3 Data migration

Methodological detail

1.4 Timeline

2 Our understanding of the current situation and objectives

This is a summary of the current state

2.1 Definitions
Definitions go here.

2.2 Data sources

A list of data sources goes here
2.2.1 Data source 1
2.2.2 Data source 2
2.2.3 Etc.

2.3 ETL process

Any processing steps, requirements, and diagrams go here.

2.4 Data validation & documentation

Data detail goes here
2.4.1 Data dictionary, source log & data test definitions
More info on data
2.4.1.1 Logical data tests
Logical data tests are tests based on the content of specific fields
2.4.1.2 Physical data tests
These tests are based on row counts and growth metrics in tables rather than logic.

3
<CLIENT NAME> Roadmap for Data & Reporting

2.4.1.3 Data test definitions & source log

Call out to the data dictionary.
2.4.1.4 Event logging
This is also a good idea.
2.4.2 Roadmap
Refer to this document.
2.4.3 Source control process
It’s always a good idea to document your process for source control.
2.4.3.1 Azure DevOps & VS Code
Call out the tools you’re using,
2.4.3.2 Triage process
The supporting process,
2.4.4 Escalation path, RACI, roles & responsibilities
And who is responsible.
2.4.5 Managing & monitoring
It’s also a good idea to add accountability to this.

2.5 Networking
Denote any particulars of network requirements.

2.6 Reporting
Outline the high-level of reporting objectives.
2.6.1 User stories
Writing user stories is key to keeping scope for reporting manageable.
2.6.1.1 User Story 1: Business User
Typically, there’s 3 user stories you’ll end up writing for reporting. The first is basic users.
2.6.1.2 User Story 2: Managers
The second is often their managers.
2.6.1.3 User Story 3: Executives
The third is typically their executives.
2.6.2 Security
Based on these user stories, you’ll want to create a security and access plan.

4
<CLIENT NAME> Roadmap for Data & Reporting

2.6.3 Creating and managing a user-base

And a user-base management strategy. https://go.microsoft.com/fwlink/?linkid=2057861 – this Microsoft
Power BI whitepaper outlines top-down and bottom-up deployment scenarios, and these options are key for
Power BI adoption success.
2.6.4 Report evolutions & environmental changes
Outline how this reporting will change.
2.6.4.1 Refresh
What needs to be updated?
2.6.4.2 AI
What needs AI in it?
2.6.4.3 Upcoming projects
Any other upcoming projects required.

3 Proposed solution
Put in a GANTT Chart of timeline & phases.

3.1 Phase 1: Remediation

This is just an example proposal.
3.1.1 Remediation
Outline what’ll be required for remediation here.
3.1.1.1 Set-up, planning & documentation
Why not include this as a main deliverable since you’re already writing a roadmap document?
3.1.1.2 Source control
You’ll always want to have a source-control strategy. See our DevOps blog post for more on how this should
work!
3.1.1.3 Remediate & prepare for release
Outline any remaining pieces.
3.1.2 Data warehouse creation
Create your data warehouse!
3.1.2.1 Model creation
Outline preliminaries of physical & logical data modelling.
3.1.2.2 Architecture unification
Describe the architecture.

5
<CLIENT NAME> Roadmap for Data & Reporting

3.1.2.3 Security & reporting consolidation

Describe & summarize what you’d change about reporting.

3.2 Phase 2: UAT & release

3.2.1 UAT
Outline your UAT plan.
3.2.2 Release
Outline your release plan.
3.2.3 Build trust & community
Building trust and community is a key to any successful data warehouse, and the whole point of writing this
roadmap. If you review the Microsoft whitepaper, you’ll see section 9 is dedicated to this.
3.2.4 Continue & refine operations
Always call out that you’re going to improve.

3.3 Phase 3: Ongoing operational optimization

Because it’s always good to call out you’ll improve twice.
3.3.1 Release
Good release planning & launch is key, since it can help you build your community with a splash.
3.3.2 CI/CD implementation approach
Yup, more improvement.