We use QSM SLIM Control frequently and we feel that we have more grip on the projects now. Echter, there are some things we struggle with. QSM SLIM Control is based on the so-called S-curve for product delivery and forecasts are made based on this curve. This means that the tool assumes that after a period of realizing functionality, a period follows in which less functionality (or slocs) is added, and where more test activities and integration takes place. This may be true for waterfall projects and to some extent to some agile projects that are supposed to stop at one time.
We have a number of contracts where we maintain applications of customers functionally using Agile/Scrum. During these contracts, every sprint functional (en niet functioneel) back-log items are realized in sprints of 2,3 of 4 weken. Echter, there is no specific end date for this. The maintenance can go on for years for all we know.
Forecasts are therefore not used to estimate the overrun in time or cost/effort, but forecasts are used to estimate how much functionality will be delivered after for instance 12 maanden. We don’t want to have the S-curve effect happening and we don’t want to forecast overruns. We just want to know how many (COSMIC) function points will be ready on December 31st.
Does anyone have any idea how to model the tool in order to do so?