Even if you use lightweight methods, which can be an excellent choice, with less focus on documentation it does not mean that you abandon writing down conclusions from meetings, internal discussions or how a difficult project issue was agreed to be handled. My most basic, but maybe the most useful, tip is:
Be sure to put conclusions in writing immediately, even if not using documentation heavy methods
I find over and over in projects that same discussions will be repeated throughout the project because participants are unsure what was concluded. To settle a discussion can sometimes be hard and time consuming work. Then you ought to think that writing it down and sending it by email just “to confirm and summarize my understanding of the conclusion” would be easy and done at once? The next time, do it.
Writing down conclusions is equally useful for internal architectural discussions and for external commercial ones. This is also related to the previous point about expectations and mutual understanding. You have the chance to use the power of definition. Your customer or your team will even thank you for it most of the time. Writing things down to document decisions will help you tremendously delivering projects, agile or not – it is what consultants like to call quick wins or low-hanging fruits.
That was my tip #3. Now go pick those fruits. I look forward to read any comments – even if you don’t agree, or maybe particularly if that is the case.
This article was originally published at projectmanagementmonkey.com in January 2009.
Sondre Bjørnebekk is an experienced project manager with a proven track record. He is currently running his own company, Innovation Consulting. Sondre holds an MSc degree in computer science from NTNU (the Norwegian University of Technology and Science) and an MBA in technology management from NTNU and MIT Sloan. Sondre maintains a Project Management Blog, the Project Management Monkey.