GMAT lessons learned are things that we did well and should keep doing, or large scale things we should be doing to improve the software or our project. Lessons learned are discussed by the team and if we decide there is an real issue, required a plan for improvement in required areas. To make sure we are efficiently handling Lessons learned, here are some high level guidelines.
Lessons learned are issues that cause significant problems or could have caused significant problems, or are issues where we did something that significantly improved the software or our project. Lessons learned require group discussion and probably a change in team habits, process or strategy.
A lesson learned is not a minor annoyance, a tweak to an existing process, or something that can be resolved between team members in the every day process of getting work done. Bring these types of issues up at meetings, or work them among the team members involved.
JJKP: Some Visual Freeze things don't actually need to be in visual freeze.
DJC: Make sure that the entire team understands the end-of-cycle and start-of-cycle repository procedures.