My first Publication Agile-Data-Warehouse-Design-eBook | Page 140

Modeling Business Processes
In Figure 4-16, dimensions have been rated by first sorting events by importance.
CUSTOMERS ORDERS and PRODUCT SHIPMENTS have come top so their
importance points (600 or 500) are copied to their dimensions. Stakeholders have
then rated order dimensions 610-670 and shipment dimensions 510-540. This
numbering scheme allows dimensions and events to be sorted correctly when
transferred to a single product backlog.
119
Dimensions and
events are rated so
they sort correctly
on a single product
backlog
Figure 4-16
Dimension
importance
rating
In subsequent sprints, the stakeholders/product owner will need to prioritize BI
reporting requirements too. While these “report user stories” are more important
to stakeholders than data models they must be rated below the star schemas back-
log items they are used to query, as in Figure 4-17 which shows a product backlog
containing prioritized reporting, dimension and event requirements.
BI reporting
requirements must
be rated lower than
the events they
measure
Figure 4-17
A DW/BI product
backlog
For more advice on Scrum, sprint planning and time-boxing read Scrum and XP
from the Trenches, Henrik Kniberg (InfoQ.com 2007).
When you have finished rating all the events and dimensions on the matrix, if the
most important events (top 1 or 2 usually) and all their dimensions have been
modeled with examples, your modeling work is done, for now, and you can bring
the modelstorm to an end. You have reached point B with enough information.
However, if matrix only events have been rated highly important you may have
one or two more events to model in detail before you can proceed to star schema
design and sprint planning.
When you have
modeled the most
important events
and dimensions with
examples, the
modelstorm is
complete. If not…