3 ms·

I started reading DMBOK, it's quite detailed as you describe. It's more of a reference in my opinion though. It can be a nice exercise to read through it with

I started reading DMBOK, it's quite detailed as you describe. It's more of a reference in my opinion though. It can be a nice exercise to read through it with a group at your company. Have people relate to what is stated in the book to create actionable goals.

NAR8789 5y ago
Thanks! To pick your brain... did you approach mostly the data modeling / data security / other slices more closely related to software engineering, or did you also socialize it out and get other people and teams involved in other slices like data governance? Can you speak to your specific situation at the time and any specific takeaways? More nitty-gritty... any suggestions for how to read through as a group in remote work? Feels like the only way might be to get each person a copy...
- haffi112 5y ago
  We read it cover to cover (this was a mistake as the book is just way too long). We usually covered a chapter in each meeting. I recommend picking one or two chapters that you need to focus on. They also have a shorter version that was released a couple of years ago you might want to look at first. Every meeting started with five minutes of writing on post-it notes how the contents of the chapter related to us (6-10 people in each meeting). Each person then put their post-it notes on a whiteboard. We had several categories to put the notes into (like "good"/"bad"/"how to apply"). This encourages people to read as they need to actively participate and contribute in the discussion. However, this book is not for everyone, some will definitely find it boring and dry. I think it is more fun the deeper you are involved in data related issues. The end of the meeting consisted of us summarizing the results to see if people were experiencing the topic similarly. We had several stakeholders in the reading group and they were from different siloes in the enterprise. It was nice to see that a lot of the experience was shared and there was general agreement regarding feedback. One memorable takeaway was the realization that we needed a data dictionary. That eventually led to a pilot project.

NAR8789 5y ago

Thanks! To pick your brain... did you approach mostly the data modeling / data security / other slices more closely related to software engineering, or did you also socialize it out and get other people and teams involved in other slices like data governance? Can you speak to your specific situation at the time and any specific takeaways? More nitty-gritty... any suggestions for how to read through as a group in remote work? Feels like the only way might be to get each person a copy...

haffi112 5y ago
We read it cover to cover (this was a mistake as the book is just way too long). We usually covered a chapter in each meeting. I recommend picking one or two chapters that you need to focus on. They also have a shorter version that was released a couple of years ago you might want to look at first. Every meeting started with five minutes of writing on post-it notes how the contents of the chapter related to us (6-10 people in each meeting). Each person then put their post-it notes on a whiteboard. We had several categories to put the notes into (like "good"/"bad"/"how to apply"). This encourages people to read as they need to actively participate and contribute in the discussion. However, this book is not for everyone, some will definitely find it boring and dry. I think it is more fun the deeper you are involved in data related issues. The end of the meeting consisted of us summarizing the results to see if people were experiencing the topic similarly. We had several stakeholders in the reading group and they were from different siloes in the enterprise. It was nice to see that a lot of the experience was shared and there was general agreement regarding feedback. One memorable takeaway was the realization that we needed a data dictionary. That eventually led to a pilot project.