Project management is a complex process that requires careful planning, execution, and monitoring to ensure success. It is essential to incorporate lessons learned from previous projects into future projects to improve project outcomes. This article will discuss the project management lessons learned related to contract management.
Definition in contract for identified issues:
Issues are an inevitable part of any project, and it is crucial to have a well-defined process for addressing them. One of the key lessons learned in project management is to include a clause in the contract that defines the grace period for issues identified before the customer acceptance or final acceptance. For instance, a 2-3 week grace period for issues identified after ATP and before CA should be added to the contract. This clause will provide a framework for addressing issues and ensure that they are resolved within a reasonable time frame.
Handling of issues identified between CA and FA:
It is not uncommon for issues to arise between customer acceptance and final acceptance. Therefore, it is essential to include a service level agreement (SLA) in the contract that outlines the process for handling these issues. The SLA should define the roles and responsibilities of both the customer and the vendor and provide a timeline for issue resolution.
Include business use cases closure date/milestone in project plan:
Business use cases are an integral part of any project, and it is crucial to define a closure date/milestone for them in the project plan. This date should be agreed upon by both the customer and the vendor and should be included in the contract.
Include FRS documentation closure date/milestone in project plan:
Functional requirement specifications (FRS) are critical documents that outline the product’s features and functionality. It is important to define a closure date/milestone for FRS documentation in the project plan and include it in the contract.
ATP list should be detailed and agreed with the customer two weeks before ATP start – include in contract:
The acceptance test plan (ATP) is a critical document that outlines the acceptance criteria for the product. It is essential to detail the ATP list and agree on it with the customer two weeks before the ATP start date. This agreement should be included in the contract to avoid any confusion or miscommunication.
Product feature details must be broken down to the lowest level of detail during SOC Q&A session:
During the system operational capability (SOC) question and answer (Q&A) session, it is important to break down the product feature details to the lowest level of detail. This will help avoid any misunderstandings and ensure that all parties have a clear understanding of the product’s features and functionality.
FRS – business requirements must be clarified before FRS closure:
Before finalizing the FRS, it is essential to clarify the business requirements to ensure that the product meets the customer’s needs. This clarification should be done before FRS closure and should be included in the contract.
Project methodology that will be used must be agreed upon in the contract:
The project methodology that will be used should be agreed upon and included in the contract. This will help avoid any confusion or misunderstanding about the project’s execution and ensure that all parties are on the same page.
Review the list of attachments with the customer before contract signature:
Before the contract is signed, it is important to review the list of attachments with the customer to ensure that all necessary documents are included. This review should be included in the contract.
Assumptions must be clearly stated in the contract:
Assumptions are a part of any project, but it is crucial to clearly state them in the contract to avoid any misunderstandings. This will help ensure that all parties have a clear understanding of the project’s assumptions.
Change management must be included in the contract:
Change management is an important part of any project, and it should be included in the contract. This will help ensure that any changes to the project are documented and
