The core part of any Smart project consists of a sequence of Realize
iterations. During these iterations the software is built, in a use case driven approach. During the previous iterations, usually types as Propose
the size and scope of the project were determined and a backlog of smart use cases and additional work items is prepared.
Now it's time to build the software. This is done in a sequence of Realize
iterations, possibly followed by one or two Finalize
iterations. Both types of iteration follow the smart iteration cycle
How many Realize
iterarion a project contains, depends on a small number of factors:
- Complexity. The total complexity of the project is of course of main importance. This complexity is expressed in smart use case points (SUCPs) and is determined during a Propose iteration, and usually sharpened during a following Scope iteration, when reusable services are investigated.
- Velocity. The size and experience of the development team decides the velocity (or speed) of the team. This velocity is expressed in two figures: the number of hours per smart use case point (h/SUCP) and the number of smart use cases points per iteration (SUCP/i).