Agile Documentation (Part 2)
Article Registered Access
This content is available to Registered Users, Subscribers, or select Customers Only.
Most of the content in the resources section is available by merely registering at the site.
If you’ve taken one of our courses, please send a note to register@netobjectives.com and include the name and date of the course you took. If it was an on-site course, please include the name of the company as well.
Most of the content in the resources section is available by merely registering at the site.
If you’ve taken one of our courses, please send a note to register@netobjectives.com and include the name and date of the course you took. If it was an on-site course, please include the name of the company as well.
This featured article is a continuation of the article appearing in the October 2007 Ezine by Amir Kolsky, Senior Consultant, Agile coach and trainer at Net Objectives. This installment extends the discussion of the place documentation takes within an Agile process by considering the unreliability of written documentation in terms of accuracy and immediacy which often leads Agile teams to put an emphasis instead on warm, high bandwidth communication media such as face-to-face conversations.
Publish Date
12/12/2007
