Learning and Planning

Acceptance Criteria — As part of the definition of done, acceptance criteria lists the main points or business rules to consider when coding and testing a user story. Acceptance criteria is often used as the basis for Acceptance Test Suite. (TBD)
Acceptance Test Suite — Include a set of tests that describe how a feature or story will be used in practice. Acceptance tests often walk through the item's acceptance criteria with hands-on exercises and Sample Feature Data. (TBD)
Actionable KPIs — Key performance indicators measure activity to determine whether a system is achieving it's defined objectives. Not all metrics are KPIs. KPIs should pass the IPA test – Important, Potential for improvement, and Authority (does the system have the means to improve this KPI?). (TBD)
Adoption Analytics — Feature adoption is visible from the business org in the form of dashboards and reports, drawing on usage metrics and the configuration audit logs. (TBD)
Analytics Considered — Actual and projected feature adoption rates are compared and used as input to roadmap planning. (TBD)
Collaborative Requirements — User stories, use cases, wireframes, and other supporting materials, are maintained in a collaborative authoring platform, such as Confluence, or specified directly in a JIRA story or task. (TBD)
Definition of Done — The definition of done is the standing set of acceptance criteria for all work items, in addition to the specific Acceptance Criteria for each item. It is a comprehensive checklist of necessary, value-added activities that assert the quality of any feature and not the functionality of that feature. A DoD often includes unit test coverage, coding to standards, peer review, and passing its own Acceptance Test Suite. (TBD)
Extensibility First — New changes are specified with extensibility for multiple subscribers in mind, including the mock customer. (TBD)
Feature Adoption — Every new feature is a hypothesis, and we track feature adoption to determine whether to pivot or persevere. (TBD)
Ideas Considered — Subscribers Ideas play a strong role in steering the future roadmap, along with a strong internal vision of the product's future. (TBD)
Ideas Solicited — Subscribers are able to post feature enhancement requests ("Ideas") to a forum for peer and product management review. (TBD)
Production Data Subset — Identify a representative subset of production data to extract into development environments. (TBD)
Ready to Develop Checklist — (Help text, error messages, sample data ...) (TBD)
Results Driven Roadmap — Based on adoption feedback, subscriber ideas, prospect needs, and other inputs, additional changes are specified, closing the loop. (TBD)
Sample Feature Data — New features provide new sample data to use with new components when appropriate. (TBD)