Friday, 10 December How to run a BI project?

Transcription

1 How to run a BI project?

2 But what about success?

3 What is this about? Look at approaches to projects Aided by best practices Unpinned by management techniques

4 What is this about? Methodology Project Management techniques Best practices

5 Also about an unsung hero......or how an old guy in a loud shirt can helps us

6 How is this going to work? Slide-uments?

7 How is this going to work?

8 How is this going to work?

9 How is this going to work?

10 How is this going to work? This is about me talking...

11 Who am I?

12

13 Should you believe me? Not Prince 2 certified 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

14 What is a project? Requirements Resources People Software Hardware Time

15 But what about failure?

16 Wikipedia 1. Unrealistic or unarticulated project goals 2. Inaccurate estimates of needed resources 3. Badly defined system requirements 4. Poor reporting of the project's status 5. Unmanaged risks 6. Poor communication among customers, developers, and users 7. Use of immature technology 8. Inability to handle the project's complexity 9. Sloppy development practices 10. Poor project management 11. Stakeholder politics 12. Commercial pressures

17 So people have Methodologies...

18 Methodology Waterfall Agile Spiral Model

19 Waterfall (Winston Royce)

20

21 Agile

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

23 Agile Principles Communication Feedback Simplicity Courage Respect

24 In practice Storyboards Scrums People standing up in meetings Sprints Backlog

25 Good or bad? Do people adhere to it too rigidly? Does it suit Business Intelligence?

26 Spiral Model

27

28

29

30 But before we even start...

31 ...it can go wrong

32 Planning and Estimation An estimate is not a contract Bottom up or top down? Commercial pressures of estimation

33 Detailed Estimation Choose the team Kickoff meeting Assemble tasks Review results Approach Individual preparation Estimation session

34 Build a Plan

35 Stages of a project Requirements Analysis Data Analysis Design ETL build OBIEE build Testing Rework Release

36 Stages of a project Month 1 Month 2 Month 3 Discovery Analysis Review 1 Iteration 1 Development Review 2 Iteration 2 Cycle 1 rework + Development Review 3

37

38 Discovery Requirements Analysis Data Analysis Discovery Architecture High level design Planning Infrastructure

39 Iteration 1 Selection Detailed Design ETL Development Iteration 1 OBIEE Development Unit/Smoke Testing Release SIT/UAT

40 Iteration n Selection Rework Detailed Design ETL Development Iteration n OBIEE Development Unit/Smoke Testing Release SIT/UAT

41 Project Manager Business Analyst Data Analyst ETL Developer OBIEE Developer Trainer Evangelist Project Roles Dimensional Modeller

42 Requirements Elicit requirements Document requirements Define acceptance criteria

43 Data Analysis Evaluate availability of source data Define error handling rules Profile data and assess data quality Prototype ETL using SQL Modelling

44 Design Define dimensional model Define ETL flow Define ETL frequency

45 ETL build Source and Target database objects Mapping or Interfaces Orchestration layer Security

46 OBIEE build Physical mappings Logical/business model Presentation layer Reports, dashboards, alerts, scorecards etc Security

47 Testing Unit testing Smoke testing Integration testing User acceptance testing Volume testing

48 Rework See previous steps...

49 Release Automated Repeatable

50 Iterate...

51

52 How to ensure success?

53 Management techniques Risk Management Configuration Management Release Management Providing visibility

54 Management techniques Selection Detailed Design ETL Development OBIEE Development Unit/Smoke Testing Release Iteration 1 SIT/UAT Risk mananagement Configuraiton mananagement Release mananagement Visibillity

55 Risk management Capture and register (ACRI logs) Communicate Ownership Assign resources

56 Configuration Management

57 Release Management

58 Visibility Adaptive tools Visible tasks Easy documentation Reporting

59 Best practices Involving the business Acceptance criteria SQL Modelling Reporting tool abstraction Testing Training (post implementation support)

60 Involving the business Involving the business Co-location What is their role?

61 We must be able to identify success

62 Early definition of acceptance criteria

63 = early visibility of data to business

64 Prototyping Evolutionary or throwaway? SQL modelling Reporting tool abstraction

65 SQL modelling

66 Reporting tool abstraction

67 Re-aligning OBIEE physical layer Presentation Layer Common Enterprise Information Layer Prototype Customer Dimension Prototype Sales Fact Prototype Product Dimension

68 Re-aligning OBIEE physical layer Presentation Layer Common Enterprise Information Layer Prototype Actual Customer Dimension Prototype Sales Fact Prototype Product Dimension

69 Re-aligning OBIEE physical layer Presentation Layer Common Enterprise Information Layer Prototype Actual Customer Dimension Prototype Sales Fact Prototype Actual Product Dimension

70 Automated Testing Test-driven development Regression testing Volume testing Test driven development Automation and smoke testing

71 Training Ensuring developers are up to speed Post implementation support Ensuring end-user and tester are up to speed

72 What is this about? Methodology Project Management techniques Best practices

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

74 Questions?