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

Modeling Business Processes
Higher rated events are more important and should be implemented sooner
—if possible.
117
Event Rating Rules
Every event gets an importance rating.
Every event gets a different importance rating, except…
Events that have been completed have an importance of 0.
Events that are truly unimportant (currently) can all have an importance of
100.
Events are rated in 100 importance point increments, e.g. 100, 200 (you’ll see
why the gaps are useful shortly).
The importance rating is only used to sort events by importance not measure
their relative business value. If Event A has importance 100 and Event B has
importance 500, B is simply more important than A, not five times more im-
portant.
Figure 4-15
Event importance
rating
If you are using the downloadable BEAM✲ matrix template, you can hide and
unhide the built in planning columns (Figure 4-15) which include event importance
and planning rows (Figure 4-16) which in turn include dimension importance.
Before you use the importance column to actually sort the event rows make sure
you fill in the event sequence column first, so that you can re-sort events back
into time/value sequence when you have finished.
As soon as the importance rules are understood, start by rating the initial event
that the stakeholders modeled. Theoretically, this should be the most important
event so you might suggest an importance based on that starting position; for
example, if the matrix describes 10 events that haven’t been implemented yet
Start by rating the
initial event highly.
Then rate other
events relative to it