1. Data Lakes vs Data Warehouses
I think in the next few years the differentiation between a data lake and a data warehouse will disappear and we will just talk about the different collection and storage approaches we use to create a “central data repository” and what sort of data sits in each layer and which technology pattern it uses.
For now here is an interesting article that identifies the differences in patterns we use between each of them.
2. Change Management in an Agile approach
When implementing a new platform and capability using an AgileBI approach, change is a constant.
In a formal waterfall project, you would always bring in a “change manager” into the team to manage change “within the business”.
But is this role still required in an AgileBI project?
We always need to effect change, and we need people to lead and encourage that change, but is it a formal role or just one of the t-skills and focus areas the Agile team have to deliver?
The following article brings some interesting content to the debate:
3. So you wanna be a Scrum Master
A few years ago I spent my time in presales roles for some of the big BI vendors. When I started in the world of presales it was often thought that a consultant could do presales in their “spare time”. Eventually, it was recognised that presales is a skill itself and one that needed to be learned and practised.
The same seems true of Scrum Masters at the moment. It seems as the waterfalls dry up, project managers now believe they can be Scrum Master because they have all run a “stand up”. In my experience being a Scrum Master with new inexperienced teams is worse than trying to wrangle 30 x 5-year-olds to all stand still in one place.
Interesting article on the subject of being a Scrum Master:
When the team have time I am nagging them to add new cool features to ODE, our open source data vault automation engine at ode.ninja.
Most of my time is actually spent teaching and coaching customers how to deliver using AgileBI as part of the Optimal Orange team.