Why Is It That Teams Do A Poor Job of Post-Writing-Project Analysis?

Project teams may recognize that reviews are not working well, though the may not understand why. A valuable solution is to conduct ”lessons learned” analysis following the end of the project. Too often, though, post-writing-project analysis receives little commitment or meaningful effort, but why?

Cuppan, Gregory P. Brainery.net (2009). Articles>Documentation>Collaboration>Assessment

Corporate Collaborative Authoring

The idea of a Book Sprint is that you can get lots of documentation written in a focused amount of time with the right team and some amount of content already in place. Gathering people in the same room when possible is extremely helpful and motivating as well.

Gentle, Anne. Just Write Click (2009). Articles>Collaboration>Agile>Documentation

Authoring in an Agile Environment

It's a simple fact of life. Developing products in today's world requires shorter cycles, sensitivity to customer needs, and a focus on deliverables that breaks the old waterfall development paradigm. More and more there is a need for teams to focus on the entire development process and deliver precisely what customers need with little or no fluff. As products move towards the user-centric model of product development the push is for more intuitive interfaces with little need for documentation -- or does it really?

Vazquez, Julio J. SDI Global Solutions (2009). Articles>Documentation>Collaboration>Agile