feature_definition_template
| Feature name | Title summarizing the functionality you want to build |
| Overview / summary | a) Work package; b) Description of what the feature will entail — you can also include any background information that will help the team; Is this a use-oriented feature or a capability (as per SAFe definition)? |
| Timing | When you plan to ship the new customer experience; Obviously this is related to the milestone for which we are freezing the scope; However, the features may have dependencies / relations that need to be taken into account; |
| Status | a) Not started / on track / at risk b) short explanation |
| Team | Product manager, development team, designers, QA, etc. |
| Strategic alignment | Explanation of how this supports business and product goals — why are you building this feature now? |
| Who it benefits | Who will benefit from the feature — link to any personas you have |
| User challenge | The problem the user is trying to solve and ways they may be attempting to solve it |
| Value score | The value estimate for the feature (feature / capability score) |
| Design | _ a) Query to related issues on gitlab; b) Relations to related design discussions / decisions; _ |
| Impacted functionality | Take note of any other functionality that this feature may affect (features in this milestone or further) |
| Open questions | Important aspects that still have to be solved in order to fully include the defined scope of the issue into the release |
| Notes | Additional background information and anything else that the team may need quick access to |