Folijet. Feature Readiness Checklist

Owned by Taisiya Trunova
Jun 29, 2021
2 min read

1. Requirements are clearly expressed by PO or any other reporter

Criteria

N/Y/NA

(N - no, Y - yes, NA - not applicable)
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?
Has the feature context  been conveyed to the team? 
Are the scope/requirements and acceptance criteria clear and well-understood by the team?
Is the design documentation finalized and linked/attached to the feature, (if required by the feature)?
Is design/mockups for FE finalized and linked/attached to the feature (if required by the feature)?
Have the modules that will be added/modified been identified? 
Are the module dependencies understood by the team? 
Has the team defined the functionality/business processes that should be covered by integration tests (Karate), Jest/RTL, E2E (Cypress+BigTest).

Is feature implementation flow (use stories implementation order/BEvsFE dependences, etc) defined? 


Is it clear how to test the feature? (TBD)
Is the feature information is up to date (applicable when a feature was groomed earlier)

2. Feature is linked to the appropriate Epic

3. Estimation in T-shirt is added

4. Level of confidence is marked

5. There are no blockers, dependencies, prerequisites preventing the team from completion of the feature; any dependencies must be clearly identified via linked issues (has to be done before, has to be done after, has to be done together with, is blocked by).

6. Feature should conform to INVEST requirements (if possible):

    • Independent

    • Negotiable

    • Valuable

    • Estimable

    • Small 

    • Testable

7. Additional requirements/details appeared after the feature was taken to development should be included in "Out of scope" section in description; additional features are created to the missing parts, than groomed and estimated. 

Instructions: 

PO: pull the feature to "Dev Ready (PO analysis complete) to start feature grooming by development team

PO: review checklist with team to ensure Team Review exit criteria is met and update this checklist.

  • Use checklist to ensure team is able to validate their understanding of the feature
  • Attach/link the copy of the Feature Readiness Checklist to the Feature
  • Pull the Feature to "Development (in progress)" when exit criteria and checklist complete