During the
Propose stage of a Smart project, it is not always possible to execute the full smart use case modeling step required to create a smart estimate, either due to lack of resources or time, or due to the large scope of the project. In this case creating a quick estimate can help.
If at estimation time it is not feasible to create a full smart use case model, create a quick estimate.
Note A quick estimate is created during the
Propose stage produces a swift but less accurate estimate is available. Normally a more accurate estimate is than produced during the
Scope stage when the smart use case model is modeled after all. This produces a much more accurate and complete estimate.
 Mark and Diederik producing a quick estimate running through an existing application |
Triggers
During the
Propose stage of a Smart project, the smart use cases are modeled to be able to create a smart estimate. Under some conditions however it is unlikely that a full smart use case model is produced during this early stage. Reasons for this can be several:
- Limited resources. There are too few people on the project team enabled to create the smart use case model.
- Limited time. The proposal has to be out in a weeks time.
- Re-engineering. Project that requires re-engineering of an existing application often have rather clear requirements. In this case a quick estimate can be produced while demonstrating all functionality of the existing application.
- Scope. On larger projects, the scope of the smart use case model is big. Now either more time is spent on the Propose stage, or a quick estimate is produced.
Technique
Instead of modeling the smart use cases, we count them. To this means a simple spread sheet will do:
- Note scale. Note the smart estimation scale (1..5, 8, 10) on the columns of the spread sheet
- Note smart use cases. Note the smart use cases on the individual rows of the spread sheet. Mainly note the user-goal level smart use cases, which are equal to the elementary business processes to be implemented
- Count to scale. Count the individual user-goal level and sub-function level smart use cases and mark these in the columns. For instance, for an typical Manage Select scenario, put a mark in the 3 column for the Manage and put another mark in the 2 column for the Select.
- Sum up. Sum the marks in all columns to add to the total number of smart use case points.
In real life, multiple variation to this theme are applied. Check the example below, which is in fact a master detail detail, where the master is presented in a list.
 An atypical Master Detail |
Sander Hoogendoorn
Read more
- Pattern catalog. Collection of analysis, design and software architectual patterns.