Do a fully-fledged requirement analysis:
i. Have a common project folder structure as per enterprise project management standards (which includes naming convention and versioning) to access the below requirements and analysis documents, important emails archive and inculcate a practice that all future artefacts like daily updates are placed in the common folder by every stakeholders involved in the projects.
ii. Physical Visual Chart showcasing key milestones and project status showing in-progress, parked issues, in-live, and future-live status etc. on project execution floor – Bay Area.
iii. Stakeholder analysis matrix document to be placed in common project folder to identify key personnel both internal and external for requirements gathering.
iv. Recommended approach is Targeted in-person workshops to understand requirements. Document MOM of the workshops and placed in project folder.
v. Going through the existing reporting to ensure that the stated requirements meet the actual reporting needs of end-user.
vi. Elicitation of requirements as a BRD with targeted sections for Scope, Metrics, Data Elements etc.
1. An ideal BRD with the following sections will be base lined.
a. Scope of work – Inputs and Outputs
b. Business Objective
c. Assumptions/ Limitations
d. Risks
e. Out of Scope
f. Stake Holder’s (Business SME / IT SME.) contact list
g. Personnel Workflow list to identify key stakeholders critical to the execution to the project.
h. Reporting and quality assurance
i. Delivery schedule for deadlines and milestones.
j. Sign offs section
k. Ancillary list of artifacts may be packaged with BRD w.r.to BI Projects are
i. Business Data Elements list.
ii. Business Formulae and Calculation steps for Metrics in Reporting Requirements
iii. Data Dimensions organized by Business Subject Areas & Hierarchies.
iv. Standardization of Business Data Elements List.
v. Business Priority Matrix
vi. Requirements traceability Matrix to support testing artifacts
vii. Data dictionary or Glossary of Terms
vii. Walkthrough of BRD & Review.
viii. Place a Change Log Artifact for BRD and SRD versioning before and after base lining.
ix. Maintain and update a Review Log by both Internal and External stakeholders for BRD and SRD
x. Updating comments in BRD for Base lining and sign-off.
xi. Signed Off BRD will lead to SRD requirements
1. System Requirement Document (SRD) will be prepared after Analysis by elaborating the BRD in detail by function requirement by describing the granularity of data, metrics calculations for reporting requirements, limitations, reconciliation and open issues.
a. Ancillary list of artifacts that can be packaged along with SRD are;
i. Solution Architecture Diagram
ii. Data Flow Diagram
iii. Dimensions, Measures for reporting requirements, type of visual requirement for reports
iv. Bus Matrix
v. Non – Functional requirements
vi. Data Governance Implementation Documents
vii. Data profiling document to check Availability, Completeness, Consistency and Accuracy.
viii. Data dictionary or Glossary of Terms.
xii. Walkthrough of SRD & Review
xiii. Open Issue Log will be kept updated in parallel with BRD and further.
xiv. Have a SIT/UAT step and UAT sign-off by Business Stakeholders both internal and external.
xv. Pre-go Live testing in Prod environment by Business Analyst.
xvi. Go-Live.
xvii. Follow the prod support work for the live BI reports which are deployed followed by the BI reports which are under deployment.