To make sure the feature contains required level of details for understanding and effective implementation by the team, it's highly recommended prior to committing and pulling the feature in progress to perform a team level exercise and fill in respective responses in the Feature Readiness checklist below. As a final step of the review, team makes a Fist to Five vote and discusses the result. If it's lower than 4, further discussion is needed to address or mitigate discovered issues.
A proposed filled in form should be linked to the feature in Jira. The Wiki page with the form itself should be placed in a centralized space to keep a track of all the business features that FOLIO has. It is proposed to create a Feature Readiness space under the umbrella of https://wiki.folio.org/display/PC/FOLIO+Product+Council or similar one and place feature readiness details of all features there. It is also suggested to use an approach similar to https://wiki.folio.org/display/PC/Decision+log where information about child pages is aggregated as a table. Of the required fields - the name of the feature, a link to its dedicated page, names of PO & development team, status (e.g., draft, in review, ready to pull).
Column 'Key Driver' in the form describes a contact person who is able to provide clarification on the respective item and support the team with necessary level of details (business or technical).
connect with feature life cycle, Jira statuses, teams' place on the roadmap
Documentation
- <Link to feature Jira>
- <Link to other related documentation, e.g. requirements list, architectural and / or technical design etc.>
Feature readiness checklist
| # | Area | Validation question | Key Driver | Status | Comment |
|---|---|---|---|---|---|
| 1 | Business value | Has the feature intent/context been conveyed to the team? | PO | ||
| 2 | Skills | Is the team equipped with the appropriate skills and domain knowledge to succeed in delivering the feature? If not, is the team aligned on necessary consultancy, knowledge transfer, etc. that will need to be accounted for in feature plan? | Triad/Dev Manager/SA order? | Dev Manager - clarification needed Triad - clarify | |
| 3 | Requirements | Is the feature information up to date (applicable when the feature was refined earlier)? | PO | The refinement process should be done before the actual development was started. Refinement should be done under the current release and the feature may be added to the next one. | |
| 4 | Requirements | Are the scope/requirements and acceptance criteria clear and well-understood by the team? | PO | Suggestion to have a list of high-level requirements before the feature is presented to a team as a feature candidate. | |
| 5 | Requirements | Is it clear for team how to test/verify the feature? | PO | PO can provide a list of Draft TC with the basic "happy-path" scenarios and most common negative errors. | |
| 6 | Requirements | Are design/mock-ups for UI finalized and linked/attached to the feature (if required by the feature)? | PO/UX designer | UX guidelines are followed | |
| 7 | Architecture | Are the architectural artifacts finalized and linked/attached to the feature (if required by the feature)? | SA/TL | ||
| 8 | Architecture | Does the team have a firm understanding of the architecture involved to deliver the feature and is the runway in place? | SA/TL | ||
| 9 | Modules | Have the modules that will be added/modified been identified (if applicable)? | SA/TL | ||
| 10 | Modules | Has the team discussed and confirmed the dependent modules interactions with their owners (if applicable)? | Triad/ SA/ Owning team Triad | ||
| 11 | NFRs | Has the current state of NFR compliance of those modules/components been reviewed? | PO/SA | ||
| 12 | NFRs | Is there an adequate plan in place to address all NFR compliance gaps to ensure the components can be released for this feature? | PO/SA | ||
| 13 | Process | Are all pending questions on the feature, assumptions, risks, and follow-up actions documented, resolved? | SM/PO | ||
| 14 | Estimation | Has the team provided T-shirt estimate for the feature (BE/FE/AQA)? | SM | ||
| 15 | Final step | Are the Triad and DEV/QA resources aligned that the feature is "Ready to Pull" in upcoming release cycle? | SM |
...