The last part of the Progressive Elaboration is creating the Feature set for each prioritized Epic and estimating the Feature. This is followed by Backlog Owner creating Stories at the Team level:

When creating a Feature, certain granular information should be captured. Below is what A2F recommends to capture:

  1. Feature Name
  2. Feature Narrative
  3. Feature Description
  4. Feature Acceptance Criteria
  5. Feature Estimation
  6. Feature Cost of Delay
  7. Feature Dependencies
  8. Feature Owner
  9. Feature Domain

The Feature Name, Narrative, and Description helps to describe what the Feature is about and a summary of its intended behavior. The Feature Narrative follows the same format as that of a User Story, but a high level:

Format: As a <ROLE> I want to do <FEATURE> so that I can do <REASON/BENEFIT>

The Feature Acceptance Criteria is a great reference for creating User and Tech Stories to implement the Feature. For example, a specific Acceptance Criteria can be broken into one to many Stories.

Feature Estimation will require to create the high-level Stories with high level estimates using the Fibonacci scale, and then adding all the points across all high-level Stories for that Feature.

Fibonacci Series: 1, 2, 3, 5, 8, 13, 21…

Based on the Business Architecture done earlier in the Progressive Elaboration process, it is important to identify which domain(s) the Feature belong to and which Product Manager should own it. For future planning purposes, dependencies should be called out for each Feature. Feature Cost of Delay is discussed in the Feature backlog section of the A2F Framework.

In this phase of the Progressive Elaboration process, Product Managers and Leads are involved and may require multiple meetings and offline sessions to cover all the attributes for each Feature that you anticipate for next Big Room Planning meeting.

Your teams can download the Agile Cognosco mobile app for your iPhone to do estimation and planning poker.