Project Lifecycle Framework Sample Clauses

Project Lifecycle Framework. With the infrastructure terminology and TRLs set out, it is possible to describe how the coordination process works. The Project Lifecycle Framework is key to the coordination of implementation within a given SGA. It defines a set of outputs, which will be used to identify problems during implementation and mitigate risks associated with the inevitable implementation challenges. It also describes how specific types of Key Performance Indicator (KPI) will be used at various points in the lifecycle to identify potential problems. The Framework will be applied to all software, service or data-producing activities within a given SGA. It is a generic method that will be applied to all Platforms, and will be monitored by the Scientific and Technical Coordinators. In some cases, it will be adapted to better suit certain activities. These adaptations will be written into the Project Implementation Proposal (PIP), described on the next page. There are two major types of lifecycle that can be employed: Agile and Co-design. The relevant Project Implementation Team will choose which type of lifecycle to use. The most important factor in determining the type is the expected length of the development cycle. Co-design closely involves target users, ensuring alignment of projects with longer development cycles. The Agile variant allows looser coupling of the development team and target users. Agile variants should be used for short development cycles, so that re- alignment with target users can happen on regular cycle boundaries. Figure 6: Software, Service or Data Development lifecycle The Agile Project Lifecycle Framework requires:
Sample 1
AutoNDA by SimpleDocs

Related to Project Lifecycle Framework

  • NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.

  • Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.

  • Project Implementation 2. The Borrower shall:

  • Master Contract Sales Reporting System Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile.

  • Instructional Framework The District and the Association have agreed to the adopted research-based instructional framework developed by Xxxxxxxxx Xxxxxxxxx and approved by OSPI. The Association and District have also agreed to Xxxxxxxxx Xxxxxxxxx’x frameworks for specialists for use with other certificated educators.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Course Curriculum, Instruction, and Grading X. Xxxx College courses offered as dual credit, regardless of where they are taught, follow the same syllabus, course outline, textbook, grading method, and other academic policies as the courses outlined in the Hill College catalog.

Time is Money Join Law Insider Premium to draft better contracts faster.