Our approach is to deliver zero documentation.
Learning about a subject results in documentation such as business models or state models. Zero documentation regards this material as the internal persistent store of the business coach. They know how to access the knowledge in the documentation ans can do so to refresh their memory. Other people (developers, business users) may ask for the documentation but it is not created for them.
Posted by chrismatts at October 25, 2003 2:03 PMSo is the request for documentation by the business user treated as a bug?
I agree that a user should not need documentation to use an application. But that has not been the case where I've worked.
Posted by: David Locke at October 26, 2003 11:02 AMAlso, as a consultant, customers will often ask for documentation. We have in the past treated that like a feature or user story, and it is either done at the end if the request is for maintenance docs or at the beginning as proof of design docs. Internally we have come very close to zero documentation.
Posted by: Darrell at October 27, 2003 4:23 AMI agree that a user should not need documentation to use an application. But that has not been the case where I've worked.
Posted by: clintoen at February 1, 2005 8:19 AM