|
  Some Kaytek Software Documentation Experiences.... |
Consulting
Software
Projects
Methodology
Software Documentation
|
Some Kaytek Software Documentation Experiences.... |
 Focus on Continous Documentation Kaytek focusses extensively on strong continous documentation in all our software projects. The internal philosophy we follow for recording all customer interactions is called DAMAGES for No Damages. Where DAMAGES is an Acronym for " Documentation After Meetings Always Guarantees Enhanced Specifications". It has worked for us successfully. |
When customers are presented with honest data metrics on their project statistics and quantum of work done, they are willing to look at your viewpoints seriously when all other factors (including past track record and mutual trust) are in order. Specially, in software projects where measurable outputs may not correlate easily to consumed inputs, trust and transparency both ways helps. |
Though it is tough to get people to document all customer interactions and requirements. Especially young Bright Software Technical Engineers and MBA's who provide the most resistance to creating documentation. They erroneously view it as a challenge to their independent thinking and creativity. Ensuring upto-date project technical documentation & it's proper mapping to the software source code is also crucial. Software Tools & Integrated Development Environments (IDE's) help greatly. |
Some partial documentation statistics of our projects : |
Project # |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|