Contents 1. Introduction
The agile manifesto declares that individuals and interactions are above processes and tools, and working software is above comprehensive documentation [1]. This movement appears to overthrow what programmers have learned about traditional software engineering. Although little attention has been given to relationships between programmers and programming tasks, it does not impact much on software development. The reason is that process procedures and control documents downplay the importance of the relationships between programming tasks and prorammes. Prcesses clearly address how software projects should be done. Often, the process comes along with a set of papers that guides and controls what and how programmers perform programming tasks or develop software. Table 1 shows two different perspectives on software development. With fewer process management and control documents in Agile Software development, understanding the links between programmers and programming tasks is more important than ever.
