Documenting progress

One of the biggest parts of keeping logs and documentation, in any project, is to see where you need to make changes. This week, we looked into the documentation of multiple teams, and provided feedback on the documents provided, as well as where the teams could make changes, to become more efficient.

This documentation also provides a means of 'selling' a team's methods, and organization skills. When a team finds a way, to keep communication lines open, and stay on target with their sprints, it is good to share these ideas, with other teams, so that they might be able to make the changes they need.

These changes may not work for every team, and that is why keeping these documents is so important. Daily, Weekly, and Periodic updates, with input from the entire team, is essential to the productivity of the team.

However, it is also important to know what needs to be documented, and what needs to be focused on elsewhere. A great quote to follow, "You can't ship a doc". Overdocumentation can prove to be conflicting with the needs of the team. If the information is difficult to find, it is less helpful at staying organized, and efficient.