CitizenDeveloper.com Terms of Service

A6200 ​​Retainer Services

Last Modified: August 21, 2020

Sales Literature

Sales literature is not applicable for this SKU.

Service Specific Terms

  • Retainer Services are a specific type of Professional Services:
    • This SKU adds additional benefits and restrictions to SKU A6000 Professional Services. Therefore, the terms of SKU A6000 are hereby fully incorporated herein. Where there is a conflict this SKU A6200 takes precedence.
    • Retainer Services very specifically provides a fixed set of hours of time and are used to pursue software development or maintenance activities as determined by the Customer, who may modify or redirect those activities at any time. The Customer may choose to use these Retainer Services for development, testing, remediation, appearance, integrations, data import or any other activity as determined by the Customer in their sole discretion, as may be amended by the Customer from time to time. The Customer may or may not elect to follow any industry standard best practices for use of these Retainer Services; for example the Customer may or may not allow for an appropriate amount of bug testing and remediation time in order to make the software function properly. For this reason, this SKU A6200 Retainer Services explicitly does not offer any assurances, warranties or representations about features, progress or software quality in the final work product, only that the retainer hours expended will be delivered professionally.
    • Retainer Size. Retainer Services are specified using a total of Hours.
    • Minimum Usage Blocks. Retainers Services are provided in minimum amounts of schedulable hours known as a “Block”. Retainer Services hours must be used in these minimum schedulable Blocks, with each Block being scheduled within a single day.
    • Scheduling Priority. Retainer Services, unless designated, do not offer any assurances about how quickly any request for hours can be scheduled. Generally speaking, CitizenDeveloper will work reasonably and in its sole discretion to schedule any Retainer Services hours in the next available time slot.
  • Special Provisions for Retainer Services.
    • From time to time Customer may enter into an agreement whose Scope or SOW identifies it as a “Retainer” or for “Retainer Time” or “Retainer Services”. Customer hereby acknowledge that in a Retainer Agreement, a resource works solely at Customers discretion, and that We are only responsible for providing a quantity of hours of a resource according to Customers direction, which direction may or may not reflect a Scope or a SOW. As such, no other provisions for Warranty, Acceptance, definition of Scope, Statements of Work, or similar provision will apply. All Retainer Agreement services are delivered on a time and materials basis and “as-­is” without exception.
    • Additional Terms for a Team based Retainer. Some Retainer Agreements Specify a Retainer Size as being a “Team”. Unless otherwise specified, CitizenDeveloper defines a Team as the following roles in any combination, as determined by CitizenDeveloper based on the then-current project demands; Application Developer, Senior Developer, Lead Developer, Architect, Business Analyst, Engineer, Sales, Project Manager, Executive, UI Designer, UX Designer, or other as designated by CitizenDeveloper. The same individual may fill multiple roles. Efforts will be made to schedule Team based development in weekly “steps”, with tasks like architectural analysis, QA etc. occurring in the step before or after the development step.
    • Additional Terms for Sprint based Retainers. Some Retainer Agreements name a Retainer SKU as being a “Sprint”. Unless otherwise specified, CitizenDeveloper defines a Sprint as being in the form of an industry standard Agile methodology, and further modified as determined by CitizenDeveloper. Generally speaking, a Sprint is employed to progress against a list features on a Backlog document, and proceeds through a process of Requirements Gathering, Development, Testing and Deployment. Typically a more detailed project plan will be provided for each Sprint, and progress against the provided project plan will be considered as an acknowledgement by CitizenDeveloper and the Client as to the correctness of that project plan. For any given Sprint, CitizenDeveloper may exceed or fall below the maximum hours at its discretion.
    • RETAINER IS DELIVERED AT THE DISCRETION OF THE CLIENT TO PRODUCE FEATURES DETAILED BY THE CLIENT. THEREFORE, FOR ANY DELIVERABLES THAT HAVE BEEN PROVIDED OR MODIFIED USING RETAINER SERVICES, CITIZENDEVELOPER SPECIFICALLY DISCLAIMS ANY AND ALL WARRANTIES WHETHER EXPRESS OR IMPLIED AND ALL OTHER REMEDIES FOR THOSE DELIVERABLES UNLESS OTHERWISE SPECIFIED UNDER THIS AGREEMENT. PUT DIFFERENTLY, THE CLIENT ASSUMES RESPONSIBILITY FOR THE FEATURES AND QUALITY OF THEIR APPLICATION WHEN EMPLOYING RETAINER SERVICES.

Specific Designations

SKU# SKU Name Retainer Size and Minimum Usage Blocks Scheduling Priority
6200.1 One Hour (Priority) One Team Member for up to 1 Hour. Priority Hourly Rate. Scheduled as High Priority – Next Available
6200.2 Quick Sprint One Full Team for up to 11 Hours. Up to 11 Team Hours to support 6 Hours of Feature Development. This is best used for quick turnaround of small iteration or development of a specific feature. Scheduling as agreed upon.
6200.10.x Rate Sheet (as per specified Contracting Vehicle) Large Public-Sector Projects. Enterprise Rate Sheet. Scheduling as agreed upon.
6200.20 Initial Development Sprint One Full Team for up to 266 Hours. Up to 266 Team Hours to support 92 Hours of Feature Development. Every new application starts with one or many of these. Best value for bulk feature development. Scheduling as agreed upon.
6200.21 Standard Sprint One Full Team for up to 166 Hours. Up to 166 Team Hours to support 42 Hours of Feature Development. Best used for substantial iteration of an already existing application. Scheduling as agreed upon.

Technical Documents

Title Link / Definition
Technical documents are not applicable for this SKU.