Presentation is loading. Please wait.

Presentation is loading. Please wait.

Enhancing the WebFOCUS/BI Development Methodology Prince Knight, PMP Manager BI Administration Independence Blue Cross.

Similar presentations


Presentation on theme: "Enhancing the WebFOCUS/BI Development Methodology Prince Knight, PMP Manager BI Administration Independence Blue Cross."— Presentation transcript:

1 Enhancing the WebFOCUS/BI Development Methodology Prince Knight, PMP Manager BI Administration Independence Blue Cross

2 IT Project Management  The Science of Developing & Delivering IT Solutions/Systems  The specific Development Methodology details steps, processes, and controls  Is a development methodology required for a reporting or BI system?

3 Industry Statistics  Standish Group Reports  31% of projects are cancelled/fail  52% are over budgeted  Only 16% are on time/on budget  GAO  49% over budgeted  23% failure rate  28% on time/on budget

4 Today’s Topics 1. Review of Project Management Methodologies 2. Introduce expanded Spiral Development 3. Review 2 projects and their approaches 4. Lessons Learned

5 Independence Blue Cross  Regional Healthcare Insurance Provider  2 Million Members  8,000 Employees  7 years champion and implementing WebFOCUS and BI concepts  WebFOCUS is the BI Standard

6 Initial IBC BI Objective  To enable our Business User Clients to enhance their reporting and analysis capabilities through the use of WebFOCUS/Business Intelligence  Hands off approach, projects developed “outside” of IT

7 General Problems With this Approach  End users continue to try and use WebFOCUS like EXCEL and Access  Our Associates continued to use the tool for “reports only”.  Did not integrate the capabilities of WebFOCUS into their business process.  The Business Units did not know enough about WebFOCUS to utilize its powers to enhance the business process

8 New IT Influence  New corporate direction to expand the use of Business Intelligence  Formation of “Informatics” Group  Formal development methodology specified by the PMO

9 Traditional Development Methodologies  Linear  Waterfall  Prototype

10 Other Methodology Models

11 Linear/Waterfall Methodologies  Step 1 – Requirements Meeting  Usually an Excel Spreadsheet  Mock up of a screen  Step 2 - Report Creation  Step 3 – User Dissatisfaction with Deliverable  Too Cumbersome  Not what they wanted  Failed BI Project  Phase II

12 Prototype  Spiral Development Methodology Fig. 1 – Boehm’s Prototyping Model

13 Prototype  Problems with Prototyping  Early stages cannot be used  Often the prototype is “thrown out”  Requirements are always “open”  Potential for “infinite” cycles and the prototype is never finished

14 ProtoBuild ®  Spiral Development with deliverable functional building blocks  Short deliverable cycles  Each deliverable is a functioning production component  After each cycle, narrow the focus in the Business Process – use WebFOCUS for the next step of analysis

15 Two Project Scenarios  Project A followed the traditional development methodology as defined by the PMO  Project B used the revised Spiral Development approach

16 Project A  Customer Reporting System  Met the basic requirements  But:  Did not fully integrate BI methodologies  Did not fully use the capabilities of WebFOCUS  Did not modify the process in order to allow for complete analytical capabilities  They are back to the drawing board for Phase II

17 Project B  National Provider Identification Project  Initial Basic Requirements  Produce a report on errors  Must be Web Based  Must be completed by May 1  Required by government regulators  Excel Spreadsheet

18 ProtoBuild Approach  No.... But,  Created building blocks of deliverables, starting with the dashboard  Summary dashboard to be delivered in 3 weeks  Meet to determine next deliverable

19 Spiral Development First Step  Summary Dashboard Requirements/JAD Development Planning/ Evaluation Testing Summary Dashboard

20 NPI Summary Dashboard

21 Next Steps – Drilldowns/Drillthrough Requirements/JAD Development Planning/ Evaluation Testing Drill Downs

22 Drill Segment

23 Add Parameter Driven Requirements/JAD Development Planning/ Evaluation Testing Parameter Driven Analysis

24

25 Ad Hoc Requirements/JAD Development Planning/ Evaluation Testing Ad Hoc/ Reporting Objects

26 Report Assistant

27 BI Functions/Business Analysis  BI knowledge base expanded  Job Jar Expanded  BI Analysis  Use logic/code for key components  Modify the process  BI presents narrowed focus for analysis  MRE

28 Major Points  Must integrate the capabilities of WebFOCUS into the analytical process  BI cannot be developed in a pre-defined box  Our current development methodologies forces this faulty approach. - Linear/Waterfall Reports Only - Spiral Development Business Analysis

29 Do’s & Don’ts Do’s  Enhance & change the Business Process  Develop short delivery objectives & meet them  Have the Business Unit work with the BI experts  Integrate the capabilities of WebFOCUS into the business analytical process  Use the GUI  Use this process when the parties are not familiar with BI  Conduct joint training classes Don’ts  Use traditional development methodology  Use WebFOCUS strictly as a programming tool/language  Resort to native SGL as the first alternative  No “gold plating”

30 Bibliography & Thanks  Barry Boehm – “A Spiral Model of Software Development and Enhancement”  The Standish Group – 1995  GAO Reports – 1997  Jenny Lalik – IBI  Donna Beiseigel – IBC  Allen Ruby - IBC


Download ppt "Enhancing the WebFOCUS/BI Development Methodology Prince Knight, PMP Manager BI Administration Independence Blue Cross."

Similar presentations


Ads by Google