2.2) but change
over time so that a few developers focus for a certain period of time on updating the
DSM solution. At other times they may be part of the team using the DSM solution. It
is worth noting that the amount of expert resources needed to build and maintain a
DSMsolution does not growwith the size of products developed in the domain or with
the number of modelers.
Waiting Cost Figure 2.2 shows a simpli?¬?ed version of the costs, since DSM
development is only one part of the overall costs.We need to consider also the cost
of waiting: the bene?¬?ts lost because the DSM solution was not yet available. If you
have decided to improve development productivity, what is the value of being able
to start next month versus next year? Let??™s assume that you have 10 developers and
that each application or feature in an application takes 6 man-months. Then you
allocate one developer from the application development team to build a DSM
solution for 4months. Of course, the other developers would not sit idle, waiting for
the DSM solution; they continue building applications in the old way. After 4
months your nine developers would have completed six applications compared to
nearly seven??”hardly noticeable. Then you introduce the new DSM solution and
assume that each application can now be made in 1 month.
Pages:
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97