Project Management Central

Please login or join to subscribe to this thread

Topics: Benefits Realization, Business Intelligence, Risk Management
Any hard won lessons to share on Cloud Data Warehouse implementation project?
Network:474



Serval month long vendor and install partner selection process is done and we are kicking off the project execution phase of a data warehouse solution using MS Solution stack including SSIS, Azure and Power BI. Any hard-won lessons learned from PMs who have been through this battle before that you would suggest to keep an eye on? I am a seasoned PM and have been watching relevant webinars as well as reading articles but would like input from the great minds here.
Sort By:
Page: 1 2 next>
Network:1669



Yes. First of all, Service level agreement. Second, security, mainly information security, features. But all of that, are not project management responsabilities. They are business analysit (in charge of the solution) and SME´s responsabilities. As project managers we manage progress, we do not make miracles.
...
1 reply by Sam Motes
Oct 28, 2018 3:54 PM
Sam Motes
...
As always Sergio great insight. Keeping pressure on the business analysts to own their deliverables will be key I agree fully. Thank you Sir.
Network:108



Hi Sam,

This is a very important issue and becomes one forward-step of IT projects.
There are many hard lessons, but I will try to write down a few of many list:-

-Using more than 6 different visual reports in BI (Radar , Sunburst, KPIStatusWithHistory)
chars.
- Using management tools of MS ( will be linked to endless of MS tools.
(MS project, SSIS,SSRS,SQL,BI,MS-R Language,ML, .....e.t.c.

-Sharing On Cloud Data Warehouse (is an advantage reducing time,cost,scope).
( I used to share some Daily telecom traffic via BI).

-Sharing On Cloud Data Warehouse will be future decades challenges as it will use
structural and nonstructural database (Daa science) with (AI,ML and IoT).

-Easy to combine different Project Management knowledge and get a good Trend
Analysis or good Analogous Estimating) as an examples only.

One thing is (dis-advantage) to this which they required your visa-card to be registered and any future charges will be charged. (Even they say they will inform you in advance.)
It means using such modern SW will be costed for unplanned projects.
(I will never accept to give my visa-card and let them overcharged me because I did not confirmed or I will be on a vacation or for another reason- It oppose the Ethic code for PMI) as I guess.


BR,
Mansour
Network:474



Oct 28, 2018 1:07 PM
Replying to Sergio Luis Conte
...
Yes. First of all, Service level agreement. Second, security, mainly information security, features. But all of that, are not project management responsabilities. They are business analysit (in charge of the solution) and SME´s responsabilities. As project managers we manage progress, we do not make miracles.
As always Sergio great insight. Keeping pressure on the business analysts to own their deliverables will be key I agree fully. Thank you Sir.
...
1 reply by Sergio Luis Conte
Oct 28, 2018 8:59 PM
Sergio Luis Conte
...
You are welcome.
Network:1106



Sam -

Make sure you are engaging all of your internal control partners (e.g. risk, legal, privacy) to ensure that their control needs are met both via the service contract and in the implemented capabilities.

Kiron
...
1 reply by Sam Motes
Oct 28, 2018 8:01 PM
Sam Motes
...
Thank you Kiron, good advice. Yes we have engaged these groups during contract discussions and signoff process.
Network:474



Oct 28, 2018 6:02 PM
Replying to Kiron Bondale
...
Sam -

Make sure you are engaging all of your internal control partners (e.g. risk, legal, privacy) to ensure that their control needs are met both via the service contract and in the implemented capabilities.

Kiron
Thank you Kiron, good advice. Yes we have engaged these groups during contract discussions and signoff process.
Network:1669



Oct 28, 2018 3:54 PM
Replying to Sam Motes
...
As always Sergio great insight. Keeping pressure on the business analysts to own their deliverables will be key I agree fully. Thank you Sir.
You are welcome.
Network:929



Sam you do not state how this project will be implemented. What I'm getting at is that typically a data warehouse project typically involves some data migration and integration components. If this is also the case with your project then I would keep a close eye on these activities since it can make or break a project like this. The bulk of this work also reside with the analyst and architect team.
...
1 reply by Sam Motes
Oct 30, 2018 10:50 AM
Sam Motes
...
Yes Anton this is typical data warehouse project with the whole migration, integration and ETL process. We have this under control for the scope of the initial project and have done brain storming for future state for other data feeds beyond the scope of this project. Thanks for the input Anton!
Network:474



Oct 29, 2018 3:55 AM
Replying to Anton Oosthuizen
...
Sam you do not state how this project will be implemented. What I'm getting at is that typically a data warehouse project typically involves some data migration and integration components. If this is also the case with your project then I would keep a close eye on these activities since it can make or break a project like this. The bulk of this work also reside with the analyst and architect team.
Yes Anton this is typical data warehouse project with the whole migration, integration and ETL process. We have this under control for the scope of the initial project and have done brain storming for future state for other data feeds beyond the scope of this project. Thanks for the input Anton!
Network:38



Managing stakeholder expectations. I've seen executives get impatient when it took a long time to implement a new integrated data warehouse system and demand that we "flip the switch", cut over to the new system already, and simply deal with the problems post-implementation. We had to explain that there is no actual switch to flip. That's just a figure of speech, and it's actually a rather involved process to cut over all the various business systems to the new data store.
...
1 reply by Sam Motes
Oct 30, 2018 12:12 PM
Sam Motes
...
Keith great input. Already fighting that battle. Some see is as just a report generation project without considering the data warehouse foundation that has to be set first to ensure the end users can self feed for data needs. Thanks for the input!
Network:474



Oct 30, 2018 11:16 AM
Replying to Keith Novak
...
Managing stakeholder expectations. I've seen executives get impatient when it took a long time to implement a new integrated data warehouse system and demand that we "flip the switch", cut over to the new system already, and simply deal with the problems post-implementation. We had to explain that there is no actual switch to flip. That's just a figure of speech, and it's actually a rather involved process to cut over all the various business systems to the new data store.
Keith great input. Already fighting that battle. Some see is as just a report generation project without considering the data warehouse foundation that has to be set first to ensure the end users can self feed for data needs. Thanks for the input!
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Laughter is the shortest distance between two people."

- Victor Borge

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events