Traditional Vs AGILE documentation

Make sure it's always “just barely good enough”(JBGE). Keep in mind that any document you create you will have to maintain later on. If the documentation is light, uncomplicated, and not too detailed, it will be easier to comprehend and update.

Write it “just in time” (JIT). Wait before documenting – it's the best way to avoid accumulating false and outdated information. Produce documentation when it is needed, not before.

Keep it in one place and make it accessible. If documentation is only useful if it's accessible. Store your product documentation in a place where you and your team members can easily find it.

Collaborate with your team. Maintaining documentation in Agile teams is a collaborative process, and every team member should be encouraged to contribute.