AgileData Newsletter #19
AgileData Refactoring
You should always plan to refactor your data, code and platform from day one.
Start off small, make some bets, plan to change if they don't work.
Sounds simple. but it is a hard pattern to utilise.
The theory of sunk costs hits often and hard.
Listen to the AgileData podcast or read the transcript @ AgileData.io
AgileData Pattern - System of Capture > Persistent History > Data Vault > Consume
AgileData Patterns are a widely used concepts to describe good solutions to recurring technical problems using an common language.
In this Data Architecture pattern we describe a way of solving the problem of:
"How do we store data centrally, in a way that provides context and absorbs changes, while also making it quickly available for use with minimal upfront work."
Read more @ AgileData WoW
Catalog - Reviews
Capturing the level of data quality is critical, so in AgileData we automatically profile the data and let you create validation rules to show you the level of trust you can have in your data.
But sometimes as well as this automated quantitive data, you want to capture qualitative data on how much the data can be trusted.
So we added the ability for your users to "review" the data and provide feedback, just like they provide feedback reviews in AirBNB, yelp etc
Shane Gibson, our Chief Product Officer gives a quick overview of how the review feature works.
Watch on YouTube
Agile Product Management
Murray Robinson and Shane Gibson had a chat with Chris Butler about agile Product Management at Microsoft, Facebook and Google.
Chris mentioned three core things that Product Managers should do, which are all applicable in the data domain:
- Wrangle uncertainty
- Help stakeholders make good decisions
- Build alignment through communication
Listen to the No Nonsense Podcast or read the transcript @agiledata.io
Buy vs Build vs Lease
One of the first agile-tecture principles we had to decide was build, buy or lease.
Read which we picked and where we applied it.