Previous
¶ Feature Tree
¶ What it is
A feature tree is a hierarchical feature list that lists the epics and the key features. Usually, a mind map would be used to represent a feature tree.
¶ Why it is useful
A well-written feature tree contains all the critical features in a high-level and structural format, which could ensure all the stakeholders and design and development teams have a common understanding of the requirements. Then the design and development team could perform further actions based on it, including wireframe design, feasibility study, etc.
¶ When to use it
Feature tree creation happens after the initial requirements are received and discussions are held. It acts as a foundation of the wireframe and the user stories. And should be updated once the requirements are more clear and more accurate.
¶ How is it done
- Make sure the high-level scope has already been determined.
- Extract the epics and the main features/subfeatures from the original requirements, and construct them together in a structured way. Mindmap could be a preferred format.
- Add the necessary notes or assumptions to make the feature tree cover good topics that may affect the efforts or timeline.
¶ Do's & Don't
Do's
- Consider the feature tree as the foundation of further actions like IA or user stories.
- Review the feature tree with the stakeholders to ensure everyone is on the same page.
Don't
- Do not expand a feature into details or list the common use cases (like updating the profile) in the feature tree.
¶ Tools needed
¶ Example
