Common use of Release Plan Clause in Contracts

Release Plan. The parties must collaborate on writing a Release Plan within the framework of the Project and milestone plan in Appendix 4 at latest when planning the first Release, and in accordance with the software development method in Appendix 6. The Release Plan must contain an overall description of the content of each Release and its placement in time. The division into Releases must allow separate testing and Field testing of Releases. The Contractor is responsible for each Release being put together in such a way that it can be tested and field tested, and with consideration of interdependencies. The Contractor must notify the Customer in writing if the Customer makes decisions that will hinder test of the Release. 3.1. It must be constantly updated and contain every change related to development, testing and Field testing of Releases. Every time the Release Plan is revised, a decision must be made as to whether to revise the Test strategy in Appendix 5 and the Project and milestone plan in Appendix 4. An eventual revision of the Project and milestone plan that is not caused by circumstances for which the Contractor is responsible, shall be handled as a change in accordance with the provisions in chapter 3. Revisions of the Project and milestone plan that are due to circumstances for which the Contractor is responsible must not lead to a delay to the agreed estimated Handover date for the deliverables as a whole. If the parties do not agree on the Release Plan, the parties may terminate the collaboration pursuant to clause 2.3.6 (Exit) before conducting the Acceptance Test of the first Release. The Contractor shall be responsible for keeping the Release Plan updated in the case of changes. The Release Plan must be labelled with the version. An updated version of the Release Plan must be available to the Customer at all times. Other components of the deliverables in the Agreement must be delivered in accordance with the deadlines set out in the Project and milestone plan in Appendix 4. Also see clause 2.1.2.

Release Plan. ‌ The parties must collaborate on writing a Release Plan within the framework of the Project and milestone plan in Appendix 4 at latest when planning the first Release, and in accordance with the software development method in Appendix 6. The Release Plan must contain an overall description of the content of each Release and its placement in time. The division into Releases must allow separate testing and Field testing of Releases. The Contractor is responsible for each Release being put together in such a way that it can be tested and field tested, and with consideration of interdependencies. The Contractor must notify the Customer in writing if the Customer makes decisions that will hinder test of the Release. 3.1. It must be constantly updated and contain every change related to development, testing and Field testing of Releases. Every time the Release Plan is revised, a decision must be made as to whether to revise the Test strategy in Appendix 5 and the Project and milestone plan in Appendix 4. An eventual revision of the Project and milestone plan that is not caused by circumstances for which the Contractor is responsible, shall be handled as a change in accordance with the provisions in chapter 3. Revisions of the Project and milestone plan that are due to circumstances for which the Contractor is responsible must not lead to a delay to the agreed estimated Handover date for the deliverables as a whole. If the parties do not agree on the Release Plan, the parties may terminate the collaboration pursuant to clause 2.3.6 (Exit) before conducting the Acceptance Test of the first Release. The Contractor shall be responsible for keeping the Release Plan updated in the case of changes. The Release Plan must be labelled with the version. An updated version of the Release Plan must be available to the Customer at all times. Other components of the deliverables in the Agreement must be delivered in accordance with the deadlines set out in the Project and milestone plan in Appendix 4. Also see clause 2.1.2.