Sprint Planning Sample Clauses

Sprint Planning. The Contractor will conduct Sprint Planning sessions, so the business and technical teams collaborate and discuss the Sprint Goal and the next priority of work for the Sprint. The Contractor’s Scrum Master will facilitate the Sprint Planning meetings. The CDPH Product Owner describes and confirms the Sprint objective and answers questions from the Development Team about execution and acceptance criteria. The Contractor’s development team will determine how much of the high priority work they will commit to for the upcoming Sprint.
Sample 1Sample 2
AutoNDA by SimpleDocs
Sprint Planning. As detailed above we run a Sprint every two weeks for a fixed duration of two weeks. It is imperative for successful delivery that the sprint goals do not change during the course of the Sprint else it is likely that ISL would be unable to deliver on the agreed sprint backlog tasks, for this reason Sprint Planning is a very important part of this process and occurs on the last day of the prior sprint/first day of the new sprint. Sprint planning involves the following steps. • Select what work is to be done from the prioritised Product Backlog • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team • Identify and communicate how much of the work is likely to be done during the current sprint • Entire team: dialog for prioritizing the Product Backlog • DevOps Team: hashing out a plan for the Sprint, resulting in the Sprint Backlog Sprint Execution For the fortnightly Sprint Planning to potentially include an ISL clients desired development tasks it is vital that the following timescales are adhered to, diagram 1.2 below shows the Sprint Execution Timescales. Diagram 1.2 – ISL – Sprint Execution Timescales Submit Change Request (1 Working Week Before Sprint Planning) • The client has submitted a formal Change Request detailing their requirements. • The ISL Product Owner will work with the client to identify the scope of the work and help them to prioritise it within their own Project Plan*. • The ISL Product Owner will clarify any technical questions (if necessary) with the ISL DevOps Team, this is not however a detailed planning of the work, merely a ball park estimate. Sprint Planning (Start Of The Sprint) See the ‘Sprint Planning’ section above. Release To Test (Friday Prior To Release To Live) To give ISL and the client time to sign-­‐off the User Acceptance Testing (UAT) phase ISL will release the changes in to their publicly available Test environment the Friday before the planned release to Live. Client Sign Off In Test (Monday Prior Release To Live) To allow ISL to successfully plan a release in to the Live environment it is necessary for the client to complete UAT sign-­‐off by 4pm on the Monday prior to the Release to Live. This involves sign-­‐off of the original Change Request document.
Sample 1
Sprint Planning. [SOWG-180] The Contractor shall after each Sprint Planning Meeting produce a Sprint Work Plan that shall be provided to the Purchaser. [SOWG-181] The Sprint Work Plan shall include:
Sample 1
Sprint Planning. The team will choose what features will be developed during the sprint. In addition, the team will ensure the user story and acceptance criteria are understood and clear, and break feature development into tasks to be taken on by team members.
Sample 1
Sprint Planning. 8.1 A sprint planning meeting is held at the start of each sprint. The implementation team and the Agile Coach are required to attend this meeting, as is the Product Owner in accordance with Sections 8.3 and 8.4. The Product Owner invites the Contractors involved in the Agile Team to the meeting via their representatives.
Sample 1

Related to Sprint Planning

  • Business Continuity Planning Supplier shall prepare and maintain at no additional cost to Buyer a Business Continuity Plan (“BCP”). Upon written request of Buyer, Supplier shall provide a copy of Supplier’s BCP. The BCP shall be designed to ensure that Supplier can continue to provide the goods and/or services in accordance with this Order in the event of a disaster or other BCP-triggering event (as such events are defined in the applicable BCP). Supplier’s BCP shall, at a minimum, provide for: (a) the retention and retrieval of data and files; (b) obtaining resources necessary for recovery, (c) appropriate continuity plans to maintain adequate levels of staffing required to provide the goods and services during a disruptive event; (d) procedures to activate an immediate, orderly response to emergency situations; (e) procedures to address potential disruptions to Supplier’s supply chain; (f) a defined escalation process for notification of Buyer, within two (2) business days, in the event of a BCP-triggering event; and (g) training for key Supplier Personnel who are responsible for monitoring and maintaining Supplier’s continuity plans and records. Supplier shall maintain the BCP and test it at least annually or whenever there are material changes in Supplier’s operations, risks or business practices. Upon Xxxxx’s written and reasonable request, Supplier shall provide Buyer an executive summary of test results and a report of corrective actions (including the timing for implementation) to be taken to remedy any deficiencies identified by such testing. Upon Xxxxx’s request and with reasonable advance notice and conducted in such a manner as not to unduly interfere with Supplier’s operations, Supplier shall give Buyer and its designated agents access to Supplier’s designated representative(s) with detailed functional knowledge of Supplier’s BCP and relevant subject matter.

  • Cloud Services You will not intentionally (a) interfere with other customers’ access to, or use of, the Cloud Service, or with its security; (b) facilitate the attack or disruption of the Cloud Service, including a denial of service attack, unauthorized access, penetration testing, crawling, or distribution of malware (including viruses, trojan horses, worms, time bombs, spyware, adware, and cancelbots); (c) cause an unusual spike or increase in Your use of the Cloud Service that negatively impacts the Cloud Service’s operation; or (d) submit any information that is not contemplated in the applicable Documentation.

  • Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are in the SLA. The remedies above are Customer’s sole remedies for breach of the warranties in this section. Customer waives any breach of warranty claims not made during the warranty period.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

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