Programming productivity: Difference between revisions

Revision as of 19:28, 2 December 2015

Revision as of 19:29, 2 December 2015

Line 39:

===Quality===

Tangen states: "Improvements in quality, other than the fact that no-fault products add to output levels, ought not to be included in the concept of productivity."<ref name="tangen2005" /> However, most of the classic literature in non-software disciplines, especially in the manufacturing area, does not explicitly discuss the role of quality of the output in the productivity ratio.<ref>[10] Thomas, B. E. & Baron, J. P. Evaluating Knowledge Worker Productivity: Literature Review Construction Engineering Research Lab (USACERL), 1994</ref> More recent works from non-manufacturing disciplines have a stronger focus on knowledge, office or white-collar work and hence increasingly discuss the role of quality with respect to quality.<ref>Al-Darrab, I. A. Relationships between productivity, efficiency, utilization, and quality. Work Study, 2000, 49, 97-104</ref><ref name="saari2006">Saari, S. Productivity: Theory and Measurement. In Business Proc. of the European Productivity Conference (EPC), 2006</ref><ref>Ray, P., Sahu, S. The Measurement and Evaluation of White-collar Productivity. International Journal of Operations & Production Management, 1989, 9, 28-47</ref><ref name="drucker1999" /><ref name="ramirez2004 />

Drucker stresses the importance of quality for the evaluation of knowledge worker productivity: "Productivity of knowledge work therefore has to aim first at obtaining quality—and not minimum quality but optimum if not maximum quality. Only then can one ask: "What is the volume, the quantity of work?""<ref name="drucker1999" />