![]() |
Diagram 1 |
Thereby the breadth or scope of a measure plays an important role: How large is the percentage of the total development process being affected by the measure? Example: An action which doubles the productivity but only in a part of a project which accounts for 50% of the total effort (blue area of diagram 1) increases the productivity of the overall project only by 33%. Explanation: Productivity and effort are reciprocal, i.e. increasing the productivity results in a reduction of the effort and vice versa (see: Measuring Productivity in Software Development). The mentioned action reduces the effort in a sub-project with 50% of the total effort by 50%. This results in an effort reduction of 25% for the overall project, i.e. 75% (3/4) of the effort remains. Due to the reciprocity the productivity is 4/3 of the original value, which is a raise of 33%.
![]() |
Diagram 2 |
![]() |
Diagram 3 |
The following lessons can be drawn from these examples:
- Improvement measures are more effective the higher the effect on the entire process is (percentage of the total effort).
- Any productivity improvement resulting by multiple measures depends on how these measures influence each other. As a general rule: The more independent they are, the more effective they are in total. Unfortunately this is difficult to predict. Usually only a range can be determined for the expected improvement.
No comments:
Post a Comment