Project managers can increase their productivity in a variety of ways. The most obvious methods involve automation and computerization which minimize the task that must be performed by employees. The growth of productivity – output per unit of input – is the fundamental determinant of the growth of a country’s material standard of living. The most commonly cited measures of productivity are in terms of a unit of size per unit of time. One cannot have sustained growth in output per person.
Regarding the first issue, measuring productivity in terms of number of lines is somehow futile. It is for the reason that different languages can produce different numbers of lines of code. Nowadays, as a programmer who always runs out of time, we typically make line of source codes shorter but concise to make it easier to decode and manage.
Productivity in lines of code cannot also be measured until an implementation starts. It is only generated during the implementation period. Measuring productivity through this kind of way can somehow take no notice of the other phases of development. Simply because we cannot identify its efficiency not until it’s implemented.
But, on the other hand, programmers may structure code to meet productivity goals ineffective because a programmer is already known on manipulating program making it more efficient.
Total productivity is a productivity measure that incorporates all the inputs required to make a product. Thus measuring productivity by means of lines of source codes are not an effective way but inputs could be grouped in several ways as long as they determine the total inputs required to produce an output.
No comments:
Post a Comment