program development and documentation

Had an interesting discussion with one of my colleagues the other day. He said that the team he is working in has adopted a 'sprint' approach. I thought that was good, until he went on to say that he had no time to document the work that was being done. That is not at all good, and goes against one of the main principles - "Done means done". In my view, if work is not documented, then it is not completed. It becomes impossible to maintain, and hard for someone else to deal with when the originator goes on holiday (or is ill).

It is something I will bring up at the monthly staff discussion group next week.