Product Backlog Sample Clauses

The Product Backlog clause defines the list of features, enhancements, bug fixes, and requirements that are prioritized for development in a project. It typically outlines how items are added, prioritized, and refined, and may specify the roles responsible for maintaining and updating the backlog, such as the Product Owner. This clause ensures that all project stakeholders have a clear, organized, and evolving set of work items, facilitating transparency and effective planning throughout the development process.
Product Backlog. This term as used herein shall mean a list of County prioritized Project activities and user stories. For the purposes of this SOW, the Product Backlog will be maintained in a JIRA instance, or in another format mutually agreed to by the County and the Contractor.
Product Backlog. The backlog of product orders existing as of the date hereof for the 420 Wideband Noise Generator and the 430 Wideband Noise Generator does not exceed $50,000 in the aggregate, and no price of any such backlog product shall have been discounted by TAS from its standard list prices for such product, except in the ordinary course consistent with past practice since January 1, 1997.
Product Backlog. As of March 31, 2005, the aggregate Product Backlog was Nine Million One Hundred Thousand U.S. Dollars (U.S.$9,100,000). Disclosure Schedule Section 3.25 sets forth, for each order included in Product Backlog, the customer name, product/service description and dollar amount of the revenue associated with such order and the date such order was received. Except as set forth on Disclosure Schedule Section 3.25, all such Product Backlog has been determined on a basis consistent with the Business’s historical practices.
Product Backlog. (a) The initial Product Backlog agreed between the Client and Software Co is set out in annexure A to schedule 2 to this Agreement. (b) The Client Representative, the Software Co Representative and the Development Team will hold a meeting before the commencement of a Sprint to update the Product Backlog by: - (i) amending any PBIs which require amendment; (ii) removing PBIs which no longer meet the Design Brief; (iii) including PBIs which are identified as being necessary to meet the Design Brief; and (iv) reviewing and reprioritising the priority of PBIs.
Product Backlog. The Contractor Team will coordinate with the Department to build a backlog of Application dashboards and other reports in an order of priority as determined by the Department.
Product Backlog. 1. The Product Manager will be responsible during the Term for preparing and maintaining the Product Backlog in the Product Tracking Tool.
Product Backlog. The backlog of product orders existing as of the date hereof for the MP 2700, the UFX-BER Series cellular and non-cellular and the SLE Series products does not exceed $1,000,000 in the aggregate, and no price of any such backlog product shall have been discounted by Neptune from its standard list prices for such product, except in the ordinary course consistent with past practice since January 1, 1997.
Product Backlog. The user stories for the EERA DTOC project were initially established through interviews with offshore wind farm design professionals. The proposed user stories were then appraised via an online questionnaire and requirements workshop to examine their relevance and relative priority. The user stories were then assembled into a Product Backlog which is a simple 'to do' list of requirements ordered in terms of priority. Several requirements initially identified have been excluded from the Product Backlog either because of their overlap with other requirements or their low priority.