Deliverable Acceptance Criteria. Contractor, in collaboration with the County development team, shall provide Sprint Status Reports and complete Release Notes, and demonstrate a functional Tally System able to perform all functions described in Task 4, which shall be reviewed and approved by the VSAP Program Manager.
Deliverable Acceptance Criteria. The Deliverable Expectation Document (DED) will be used for Critical Deliverables and for other deliverables at DIR’s discretion to document mutually agreed-upon deliverable descriptions and applicable standards, and to more clearly define acceptance criteria. The Service Provider and DIR will develop and mutually agree upon the DED. Deliverable acceptance will be contingent upon material compliance with the DED and any rejection of a deliverable must be accompanied by a description of the material non-compliance with the DED. Any changes to the DED will be approved through mutual agreement between DIR and the Service Provider. DIR, in its sole discretion, may choose to forgo the creation of the DED. DEDs will not contradict nor alter the contract acceptance criteria requirements set forth in the Agreement. In the absence of a DED, the acceptance criteria for a Milestone/Deliverable would be material compliance with the requirements as set forth in the Agreement. The following requirements will be documented in the DEDs:
1. Format of the Deliverables;
2. Deliverable Requirements;
3. Submission Process and Requirements;
4. Delivery Schedule including Incremental Delivery Dates;
5. Review and Comment Requirements (who, when, how); and
Deliverable Acceptance Criteria. Agile Software development: Provide professional SCRUM Master to bring leadership to the other members of the wider team. The SCRUM Master’s roles will include, but not be limited to: Assisting with the decomposition of potential projects into work packages so that business benefits can be delivered at speed Quality assurance and guidance on producing effective user stories Coaching on effective management of project backlogs Running daily stand-up meetings Organising and running Retrospectives at the end of each sprint Producing planning and other documentation in line with agile methodology for each sprint Provide a development team who are capable of delivering production-level code iteratively. Whilst the team members may typically be only 3-5 in number they will have cross-functional skills and be responsible within each sprint for producing the actual work (aspects of analyse, design, develop, test, communication to architecture teams etc.) Each engagement will be centred on a two-week sprint using SCRUM, Kanban or other methodologies such as scrum-ban depending on the underlying product under development. Where a new product or epic is to be started a development spike/tracer bullet will be delivered as one of the sprints in order to assure that the current architecture, methodology, technology and development frameworks are suitable and will provide quick feedback to the product owner that the approach is sound. Product owners will be sourced directly from the HMCTS business community and will be expected to provide business leadership within the team. Technical Product Owners will be provided from the incumbent technical teams. Output approved by the Business Product Owner and Technical Product Owner Knowledge Transfer: In the event of a change in supplier mid-project or the introduction of new parties to the project (business or delivery side) this should be estimated to provide an appropriate amount of documentation, briefing and knowledge transfer activities on work undertaken Approval of approach and outputs by Project Manager and relevant Technical Lead
Deliverable Acceptance Criteria. Contractor shall carry out the activities described in this task, which shall be reviewed and approved by the VSAP Program Manager.
Deliverable Acceptance Criteria. Contractor and the County will complete and submit deliverables for review and approval according to the Work Plan. The County will review and provide feedback on all Contractor deliverables in a timely manner (within five business days) so as not to affect the project schedule. If resolution cannot be made within the five business days, the County Project Manager will escalate the issue to the appropriate level.
Deliverable Acceptance Criteria. Except for Licensed Services and Application all other Deliverables shall be deemed accepted when the Authorized User determines that such Software and Deliverables successfully operate in accordance with the Requirements and applicable order or SOW. At a minimum, Acceptance Criteria for Software and Deliverables, and for the Solution as a whole, shall ensure that all of the functionality described in the Requirements set forth in Exhibit A and required by the Authorized User in the applicable order or SOW has been delivered to the Authorized User. Acceptance of any one Deliverable shall not imply Authorized User's concurrence that the Deliverable will function properly with or within the Solution. Supplier shall be responsible for ensuring that all Deliverables function properly within the Solution. Should a previously Accepted Deliverable require further modification in order to work properly with or within the Solution, Supplier shall be responsible for all costs associated with such modification. Such Authorized User agrees to commence Acceptance testing within fifteen (15) days, or within such other period as set forth in the applicable order or SOW, after receipt of the Software or Deliverable. Acceptance testing will be no longer than forty-five (45) days, or such longer period as may be agreed in writing between Authorized User and Supplier, for the first instance of each product type set forth in Exhibit B. Supplier agrees to provide to such Authorized User such assistance and advice as such Authorized User may reasonably require, at no additional cost, during such Acceptance testing, other than pre-approved travel expenses for time and materials type orders or SOWs or for fixed price type orders or SOWs in which travel expenses were expressly excluded from the total price of the order or SOW. Any such travel expenses must be pre-approved by the Authorized User and shall be reimbursable by such Authorized User at the then-current per diem amounts as published by the Virginia Department of Accounts (xxxx://xxx.xxx.xxxxxxxx.xxx), or a successor URL(s)). Authorized Users who are not public bodies may have their own per diem amounts applicable to Supplier's pre- approved travel expenses. Authorized User shall provide to Supplier written notice of Acceptance upon completion of successful Acceptance testing. Should Authorized User fail to provide Supplier written notice of successful or unsuccessful Acceptance testing within five (5) days following the ...
Deliverable Acceptance Criteria. All concluded work must be submitted to Covered California for review and approval or rejection. Payment for all tasks performed under this Agreement will be based on hourly rates. It will be Covered California’s sole determination as to whether any tasks have been successfully completed and are acceptable.
Deliverable Acceptance Criteria. Contractor shall develop a Project Control Plan document as described in Task 0, which shall be reviewed and approved by the VSAP Program Manager.
Task 1 Tally System Version 1.2 Implementation
Deliverable Acceptance Criteria. Contractor, in collaboration with the County development team, shall provide Sprint Status Reports and complete Release Notes, and demonstrate a functional VBL Application able to perform all functionality described in Task 14, as prioritized by the County designated Product Owner, which shall be reviewed and approved by the VSAP Program Manager. Xxxx 00 will focus on the continuing collaborative development of the VBL Application. During the period, and utilizing the resources specified in the Project Schedule, Contractor will initiate implementation of the Project utilizing the then-current Product Backlog. Prior to each sprint (typically a two-week implementation cycle), County will prioritize the user stories and activities from the then- current Product Backlog. Using the prioritized Product Backlog, Contractor will assign story points to a set of user stories and activities to be implemented during the upcoming sprint. For this reason, it is possible not all specified user stories will be implemented. Task 14 consists of development activities to produce continuing enhancements to existing features, as well as new epic features listed below: ● Box Card Generation – This epic involves the generation of box cards through VBL. ● Support for Full Face Ballot Vote at Poll – This epic involves adding a full-face ballot type to ballots generated by VBL, so that there is the option to provide the full-face ballot during election day.
Deliverable Acceptance Criteria. Contractor, in collaboration with the County development team, shall provide Knowledge Transfer Status Reports, which shall be reviewed and approved by the VSAP Program Manager.
