Feature Trees are high-level models organizing features into feature groups, capturing the entire scope of a project into a single model. Features are listed into three separate levels of detail. The highest level features are shown on Level 1 (L1), mid-level features are shown on Level 2 (L2), and low-level features are shown on Level 3 (L3). Typically, your High-Level Features in your Business Objectives Model become your L1 Features.

This model is typically a one-page view of all the features within a system and its purpose is multifaceted.  First, it helps us see relationships within our system.  It also acts as a roadmap, allowing us to see which key features need to be built out first and which features should be addressed later in the project.  In addition, this model helps ensure that all of the necessary features within our system are being considered.

As mentioned above, this model is used to define and deliver a clear snapshot of the scope of the project.  It is also used as an organizational and planning tool.  For these reasons, a Feature Tree should be created early in a project.

For more information on Feature Trees, visit Visual Models in Agile – Feature Trees.

Learn more about requirements models in our book Visual Models for Software Requirements (Microsoft Press, 2012) Joy Beatty and Anthony Chen. (See Chapter 6 for Feature Trees)