The Agile Software Development Process

1566 Words Sep 13th, 2015 7 Pages

Over the last several years, agile software development processes have become increasingly popular. According to Fowler (2003), the agile software engineering processes attempt to enable more flexible and adaptive software development than the traditional software engineering processes offer.

Agile practitioners consider documentation as an important aspect for their projects but there is too little internal documentation available in their projects (Stettina and Heijstek, 2011). Although the documentation is mentioned, it is not anchored in the original process that relies on verbal communication (Schwaber and Beedle, 2001). Verbal communication is susceptible to lapses of memory and after some time it gets progressively harder to recall design rationale. This problem is compounded by team turnaround (Stettina and Heijstek, 2011).

The main objective of documenting a project is to instruct consumers about the structure of the system, its functionality, operability and the design structure in case there is need to redesign the system. The primary consumers of the design documentation are those who maintain or upgrade the system. Other stakeholders, such as users, testers, and project managers may also need to know about the system (Selic, B., 2009). However, according to Bran Selic, (2009) software developers do not like to document, as it has no value for them. Even the agile manifesto, issued by the software industry’s avant-garde, proclaims “Working software…
Open Document