Revise Project Documentation

• Project objectives  Objectives should be broken down into timeframe by phase. For example, if the original project objectives were for a, b, and c by date x, the revised project objectives will be a by date x1, b by date x2, and c by date x3. Here there are three phases or segments: x1, x2, and x3.
• Project priorities  Dates when each functional item or feature needs to be delivered.
• Architecture  The core architecture must support the full solution, but there will be several iterations of it as it scales up to support future releases.
• Organization chart  A detailed organization chart that describes roles and responsibilities for anyone connected with the project. Poorly structured organizations are a major source of problems, so take care to remove redundancies, inconsistencies, and inefficiencies here.
• Communications plan  A formal communications plan addressing each person in the preceding organization chart must be defined and communicated to the extended project team. This plan describes how and when each person and organization will receive written and oral communications from the project manager.
• Acceptance criteria  Criteria should be divided into the phases or segments that are defined.
  
• Key metrics  This should document what can be modified as the project unfolds and gets off track again. In other words, prepare for the next adjustment as a precautionary measure.
• Risk assessment  This should document what went wrong in the project thus far and the mitigation strategies for avoiding the problems in the future.
• Project Charter  The Charter needs to be updated with the new dates and phases."