Agenda for Discussion Risk Management Stakeholder Analysis

1. project solutions for your world ™ “Data Warehousing Projects” Agenda for DiscussionRisk ManagementStakeholder Analysis Gina Davidovic, PMP Gina.Davidovic@Bay3000.com Bay3000 Consulting Inc.

2. Risk Management • Risk Profiles • Risk Assessment • Risk Strategy

3. Risk Profile Questions The Team • How large is the team? • What % of the team is dedicated to project? • What is the experience level of the stakeholders? • Have these team members worked together before? • Is the team spread out geographically? The Client • Are the clients from multiple departments or divisions? • Will roll out of the DW result in changes to existing processes? • Have these clients looked at the quality of their data before? The Technology • Will there be technology that is new to this development team? • Will there be technology that is new to the clients or users? • Will there be leading-edge technology used?

4. Risk Analysis

5. What Are Some Common DW Risks?

6. Common DW Risks • Resistance at the cultural level asking the customer relationship to be shared across the organization • Staffing support requirements are underestimated. • Number of users of the technology were underestimated • Business unit does not provide good people for the project • Several business units cannot agree among themselves • Business priorities change • Existing business process is in poor condition • Business unit management resists change • Sponsor not available • New sponsor • Other work has higher priority for the business unit

7. Common DW Risks Cont. • The technology does not interface or integrate with existing systems. • A newer version of the technology will be available soon • The performance of the technology is not satisfactory • Technology in use is obsolete • Lack of support from the vendor • Vendor attempts to take over the project • Vendor provides the wrong staff or has high staff turnover • Project manager pulled to another project • Performance not as expected • Turnover of project team members • Delays in vendor responses to problems • Data quality issues

8. Condition The new corporate standards require that all data models be developed using xyz technology, which our staff have not used before. Risk Analysis Example Consequences All data modeling tasks will take longer. It is also likely that re-work of the early work will be necessary as staff learn to use the tool more effectively. On average, the slower work will add up to 25% more effort on data modeling tasks. Probable labor cost: 1.25 Strategy Send staff that will be creating and updating data models on a 2-day course on xyz. The training cost is $5,000. Make one team member the tool expert. This tool expert will spend 5 days to create templates, and a data model management strategy to ensure smooth version control for the rest of the users. Can get Prod factor back to 1 Notes Probability here is a subjective estimate based on the average normal productivity of a data modeler.

9. Risk Lessons Learned • Select an executive steering committee that will support the initiative throughout its lifecycle. • Ensure the plan includes scenarios on how the data warehouse is expected to generate and support bottomlineimprovements. • Find the best projectmanager who has strong interpersonal and communications skills, understanding of business issues, ability to mobilize quickly, ability to build a good team, and have the courage to make tough decisions -- and acquire them at all costs. • Insist on an achievable execution plan and on a proactive communication strategy. • Monitor your vendor relationships closely. • Avoid creating additional risk by rushing, under staffing, under funding, or ignoring the obvious. • Do not take the risk if the benefits are not identified or the risk does not achieve a defined project objective • Manage and analyze your assumptions, as you would risk. Changing assumptions are additional risk events.

10. Managing Stakeholders (A Risk Strategy !) “Stakeholder management is a must in order to generate synergy and minimize conflict among key players.”Paul C. Dinsmore What does a good ‘stakeholder manager’ do?

11. How Do You Know Who Holds The Stake? Sponsor External Client Project Manager Team Members

12. Identify / Analyze Who are they ? What do they want? What do they contribute? How do they contribute? What’s their style / behavior? Past project experience? What do they Expect?

13. Example Who will contribute? Identify / Analyze Stakeholders

14. Strategize Go to a Higher Altitude Educate / Plan Seeds Be Proactive Win support and Sponsorship Outline objectives Develop tactics / timing Re-Analyze -> Satisfaction

15. Steering Committee = Sponsor Possible Roles • Provide the project manager with strategic direction, set priorities • Approve key deliverables, approve or deny recommendations • Support the project process, provide help in the resolution of issues • Ensure that all that can be done is done to achieve the business objectives • Assist project manager with problem solving Motivation Steering groups are a great way to receive regular positive feedback on the project. Team members will feel a greater sense of motivation if they get a note on occasion from the Steering Committee saying ‘thank you’ or ‘well done’ as a result of Steering Committee discussions. "I've got a great sponsor: His boss' boss' boss is a manager."source unknown

16. Gina Davidovic, PMP Gina.Davidovic@Bay3000.com www.Bay3000.com Thank You for Allowing Me to Share Some of My Experience !