Iterative Model Sample Clauses

Iterative Model. CCG uses a staggered iterative model that has evolved as a result of many LDS implementations. Rather than be bound by the constructs of specific methodology we have adopted key aspects to maximize value while maintaining the flexibility necessary to allow the solution to adapt and evolve throughout development. The basis for our framework is ✓ Developing a clear roadmap and priority ✓ Involving members at time of relevance ✓ Releasing meaningful portions of solution sooner in the timeline ✓ Implementing check points to inspect and adapt ✓ Facilitating hands on feedback ✓ Fostering technical innovation A key advantage of a staggered model is the minimized idling of resources. While the LDS is a concerted effort, we recognize that resources participation varies at different points in the cycle. TCG is introduced to drive the initial vision and design. Based on those conversations we will identify what data points will be collected and begin putting in requests for files. As the files are received, a back-end developer will roll on to begin data warehouse design and load. Once a sufficient quantity of data becomes available in the warehouse, a BI developer will be added to begin creating the reporting layer of the LDS. The LDS will be released on a regular basis that coinciding with stakeholder/development team meetups. Usually, on a weekly basis, the meetups are put in place to showcase recent development and xxxxxx feedback. Design, while front-loaded in the timeline, continues throughout the entire development in the meetups. This allows for the team to pivot and make adjustments to the solution as understanding of solution needs grow. Communication and focus are our keys to a successful project. CCG utilizes Azure DevOps to organize our goals and priorities into actionable tasks. We leverage the meetups to align progress and direction with stakeholders to get in front of any obstacles as soon as possible.
AutoNDA by SimpleDocs

Related to Iterative Model

  • License Model The software is licensed under two models: • Perpetual License Model – Under this model, you have licensed the software under perpetual license terms, as code that is installed on your premises or hosted for you by a third party acting as your agent (“Perpetual License Model”).

  • Alternate Work Schedule An alternate work schedule is any work schedule where an employee is regularly scheduled to work five (5) days per week, but the employee’s regularly scheduled two (2) days off are NOT Saturday and Sunday.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • School Improvement Plan As permitted under IC § 20-10.2-3-1.5, the Charter shall serve as the Charter School's strategic and continuous school improvement and achievement plan (hereafter, the "School Improvement Plan"). To the extent that IC § 20-10.2 applies to the Charter in its function as the School Improvement Plan, the Organizer shall comply with the requirements under IC § 20-10.2.

  • Work Schedule A 4/10 work schedule is four (4) ten hour days in a seven (7) day period, for a total of forty (40) hours per week.

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