How to Run a BI Project

8/6/2019 How to Run a BI Project

1/74

How to run a BI project?

Friday, 10 December 2010


2/74

But what about success?



3/74

Look at approaches to projects Unpinned by management techniques

Aided by best practices

What is this about?



4/74

What is this about?

Project

Methodology

Management techniques

Best practices



5/74

Also about an unsung hero...

...or how an old guy in a loud shirt can helps us



6/74

Slide-uments?

How is this going to work?



7/74




8/74




9/74




10/74

This is about me talking...




11/74

Who am I?



12/74Friday, 10 December 2010


13/74

Not Prince 2 certied

Not a Scrum Master

This is not a technical project manager piece I see this in a number of organisations I see this over a number of years I did a Software Engineering degree

Should you believe me?



14/74

Requirements

Resources

People Software Hardware

Time

What is a project?



15/74

But what about failure?



16/74

Wikipedia1. Unrealistic or unarticulated project goals2. Inaccurate estimates of needed resources3. Badly dened system requirements

4. Poor reporting of the project's status5. Unmanaged risks6. Poor communication among customers, developers, and users7. Use of immature technology8. Inability to handle the project's complexity

9. Sloppy development practices10. Poor project management11. Stakeholder politics12. Commercial pressures



17/74

So people haveMethodologies...



18/74

Waterfall Agile

Spiral Model

Methodology



19/74

Waterfall

(Winston Royce)



20/74Friday, 10 December 2010


21/74

Agile



22/74

Embrace change

Develop software in short amounts of time Multiple development cycles Emphasis on face-to-face communication

Agile



23/74

Communication

Feedback Simplicity

Courage

Respect

Agile Principles



24/74

Storyboards Scrums

People standing up in meetings

Sprints

Backlog

In practice



25/74

Do people adhere to it too rigidly? Does it suit Business Intelligence?

Good or bad?



26/74

Spiral Model



27/74



28/74



29/74



30/74

But before we evenstart...



31/74

...it can go wrong



32/74

An estimate is not a contract Commercial pressures of estimation

Bottom up or top down?

Planning and Estimation



33/74

Detailed Estimation

Approach Choose the team

Kickoff meeting

Individual preparation Estimation session Assemble tasks Review results



34/74

Build a Plan



35/74

Requirements Analysis

Data Analysis

Design ETL build OBIEE build Testing Rework Release

Stages of a project



36/74

Stages of a project

Review 3

Review 2

Iteration 2

Month 1 Month 2 Month 3

Discovery

Iteration 1

Review 1

Analysis

Development

Cycle 1 rework+

Development



37/74



38/74

Discovery

Discovery

Requirements Analysis

Data Analysis

Architecture

High level design

Planning

Infrastructure



39/74

Iteration 1

Iteration 1

Detailed Design

ETL Development

OBIEE Development

Selection

Unit/Smoke Testing

Release

SIT/UAT



40/74

Iteration n

Iteration n

Detailed Design

ETL Development

OBIEE Development

Selection

Unit/Smoke Testing

Release

SIT/UAT

Rework



41/74

Project Manager Business Analyst Data Analyst Dimensional Modeller ETL Developer

OBIEE Developer

Trainer Evangelist

Project Roles



42/74

Elicit requirements Document requirements

Dene acceptance criteria

Requirements



43/74

Evaluate availability of source data

Prole data and assess data quality Dene error handling rules

Prototype ETL using SQL Modelling

Data Analysis



44/74

Dene dimensional model Dene ETL ow

Dene ETL frequency

Design



45/74

Source and Target database objects

Mapping or Interfaces Orchestration layer

Security

ETL build



46/74

Physical mappings

Logical/business model Presentation layer

Reports, dashboards, alerts, scorecards etc

Security

OBIEE build



47/74

Unit testing

Smoke testing Integration testing

User acceptance testing

Volume testing

Testing



48/74

See previous steps....

Rework



49/74

Automated Repeatable

Release



50/74

Iterate...



51/74



52/74

How to ensure success?



53/74

Risk Management Conguration Management

Release Management

Providing visibility




54/74


Iteration 1

Detailed Design

ETL Development

OBIEE Development

Selection

Unit/Smoke Testing

Release

SIT/UAT

Risk mananagement

Conguraiton mananagement

Release mananagement

Visibillity



55/74

Capture and register (ACRI logs)

Communicate Ownership

Assign resources

Risk management



56/74

CongurationManagement



57/74

Release Management



58/74

Adaptive tools

Visible tasks Easy documentation

Reporting

Visibility



59/74

Involving the business

Acceptance criteria SQL Modelling

Reporting tool abstraction

Testing Training (post implementation support)

Best practices



60/74

Involving the business Co-location

What is their role?

Involving the business



61/74

We must be able toidentify success



62/74

Early denition of acceptance criteria



63/74

= early visibility of datato business



64/74

Prototyping

Evolutionary or throwaway? SQL modelling Reporting tool abstraction



65/74

SQL modelling



66/74

Reporting toolabstraction


R li i OBIEE


67/74

Re-aligning OBIEE

physical layer

Common Enterprise Information Layer

Presentation Layer

PrototypeProduct

Dimension

PrototypeCustomerDimension

PrototypeSales Fact


R li i OBIEE


68/74

Re-aligning OBIEE

physical layer


Presentation Layer

PrototypeProduct

Dimension


PrototypeSales Fact

PrototypeProduct

Dimension

ActualCustomerDimension

PrototypeSales Fact


R lig i g OBIEE


69/74

Re-aligning OBIEE

physical layer


Presentation Layer

PrototypeProduct

Dimension


PrototypeSales Fact

PrototypeProduct

Dimension


PrototypeSales Fact

ActualProduct

Dimension


PrototypeSales Fact



70/74

Test-driven development

Automation and smoke testing Regression testing

Volume testing

Test driven development

Automated Testing



71/74

Ensuring developers are up to speed Ensuring end-user and tester are up to speed

Post implementation support

Training



72/74

What is this about?

Project

Methodology


Best practices



73/74

Look at approaches to projects Unpinned by management techniques Aided by best practices

Conclusion



74/74

Questions?

Documents

How to Run a BI Project