Agenda for Discussion Risk Management Stakeholder Analysis

advertisement
“Data Warehousing Projects”
Agenda for Discussion
Risk Management
Stakeholder Analysis
project solutions for your world
Gina Davidovic, PMP
Gina.Davidovic@Bay3000.com
Bay3000 Consulting Inc.
™
Risk Management
Risk Profiles
Risk Assessment
Risk Strategy
2
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?
3
Risk Analysis
Major Impact
No Major Impact
Not Very Likely
Very Likely
Should have a risk strategy
MUST put a strategy in place not
only to respond to these risks, but
to mitigate them from the start
Do not spend time on these
Keep your eye on these in case their
‘no impact’ assessment changes.
4
What Are Some Common DW Risks?
project solutions for your world
™
5
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
6
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
7
Risk Analysis Example
Condition
The new corporate standards require that all data
models be developed using xyz technology, which our
staff have not used before.
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.
8
Risk Lessons Learned
1
Select an executive steering committee that will support the initiative throughout its lifecycle.
2. Ensure the plan includes scenarios on how the data warehouse is expected to generate and
support bottom line improvements.
3. Find the best project manager 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.
4. Insist on an achievable execution plan and on a proactive communication strategy.
5. Monitor your vendor relationships closely.
6. Avoid creating additional risk by rushing, under staffing, under funding, or ignoring the
obvious.
7. Do not take the risk if the benefits are not identified or the risk does not achieve a defined
project objective
8. Manage and analyze your assumptions, as you would risk. Changing assumptions are
additional risk events.
9
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?
10
How Do You Know Who Holds The Stake?
Sponsor
External
Project
Manager
Client
Team
Members
11
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?
12
Example
Who will
contribute?
Identify / Analyze Stakeholders
Role
Contribution
Project Team Skills and effort to perform tasks
Sponsor
Expectations
Frankness, professional
development, fairness,
career advancement
Authority, guidance, and maintains project priority
By …
Actively participating in monthly steering meetings,
assisting in problem solving and issue resolution,
motivating team members, and visibly supporting the
project in the organization
Client
Product requirements, funding
Functional
Managers
Resources, corporate policies
13
Strategize
Go to a Higher Altitude
Educate / Plan Seeds
Be Proactive
Win support and Sponsorship
Outline objectives
Develop tactics / timing
Re-Analyze -> Satisfaction
14
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
15
Thank You for Allowing Me to Share
Some of My Experience !
Gina Davidovic, PMP
Gina.Davidovic@Bay3000.com
www.Bay3000.com
project solutions for your world
™
16
Download