Iterations create milestone dates, milestone dates force trade off decisions to be made
Data teams struggle to not “boil the ocean” when doing data work.
Use milestones as a pattern to help the data team to focus on what really needs to be built and manage the trade-off decisions for what doesn’t.
Your data team are mercenaries, define your ways of working based on this
Modern data teams are transient, often staying less than 5 years, unlike past decades of long-term loyalty.
Companies should adapt by defining robust Ways of Working (WoW) that endure beyond individual tenures.
Balancing in-house teams with reliable data vendors for continuity and efficiency may also be a useful pattern as part of your WoW.
I’m getting pedantic about semantics
I’m getting pedantic about semantics TD:LR Having a shared language is important to help a data team create their shared ways of working. When we talk about self-service, we should always highlight which self-service pattern we are talking about. Shane Gibson -...
Most of your data is rotten and it’s not your fault, but it is your problem
Data quality is an expectation, not an exception.
While data quality is crucial, it’s not always directly our fault when issues arise, nevertheless, it remains our problem to solve.
Data Contracts are one pattern that can help us solve this problem.
Recent Comments