#06 - Core Business Events, What data is required?
What data is required and where is it first captured?
Once I have captured the frequency the data has to be refreshed as outlined in my previous post:
I move onto the sixth area, the Core Business Events.
In the Core Business Events area I identify what data is required to deliver the Information Product.
I want to understand the essential data I need, help discover if I have already collected it, or identify which System of Capture it needs to be collected from.
Core Business Events represent key business processes, activities or transactions within your organisation that capture the necessary data to answer the stakeholders’ business questions.
These Core Business Events generate the data that will be used in the Information Product.
In identifying core business events, consider all activities that produce relevant data. This includes events related to the business questions, as well as related events that may provide further context or insights.
I use the Agile Data “who does what” pattern to quickly understand the related Core Business Concepts and Processes.
This pattern helps establish a shared language between the business experts and Agile Data Team.
It prevents premature delving into detailed data requirements, this can occur once the Information Product is prioritised for delivery.
We want to identify if the required data has already been collected, designed and transformation rules have been applied. If not, the Agile Data Team will need to initiate that work.
This information aids the Agile Data Team in estimating the complexity and effort needed to deliver the Information Product. It also proves essential in future discussions about trade-off’s decisions with stakeholders.