Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
N - no
Y - yes
NA - not applicable
| Criteria | N/Y/NA |
|---|
| 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) |
|