A product is a combination of rev parts and dev parts. Changes to a part could be in the form of addition, deprecation, or transformation. While the changes are a set of tasks or work for the build teams involved, the outcome of relevance is either a new part, an existing part that's deprecated, or an existing part that's improved or expanded. In the latter case, the enhancement record merges with the part on which this activity is based.
Enhancements may be used to track higher-level groups of user stories or to bundle related work together. This usage of "enhancement" is similar to "epic" in other build approaches. You can perform filtering by stage and add stage attributes for enhancements.
🎥 Video: Epic planning with enhancements
🎥 Video: Enhancement promotion
🎥 Video: Enhancement merging
To create an enhancement, go to Product > Parts, click + Part, and select Enhancement from the menu.
Requests and requirements from various sources–customers, support, tech leads, and product managers–are discussed to form a cohesive idea for a product enhancement. The outcome of this stage is a product requirements document (PRD) that describes the enhancement. The PRD and supporting documents are linked to the ENH item in the Related > PRD field.
The decision-makers have decided to proceed with the enhancement idea and have allocated resources to make it happen. The outcome of this stage is a resourcing plan that may be linked to the ENH item in the Related > Other field.
Technical and UX design is underway. The outcome of this stage is one or more design documents linked to the ENH in the Related > Design field.
Implementation of the enhancement is underway.
Quality assurance and verification of the enhancement are underway.
The enhancement has been made available to a subset of customers. At this stage, the enhancement may be merged with an existing part or promoted to a new part.
The enhancement has been made available to all customers. At this stage, the enhancement should be merged with an existing part or promoted to a new part.
The enhancement has reached the end of its life and is no longer supported for customer use. Customer questions about the enhancement should be addressed by helping them migrate to the part with the replacement functionality or by recommending that they otherwise stop relying on the enhancement.
Due to multiple reasons like bandwidth crunch or new emerging priorities, the decision-makers have decided not to work on the enhancement for the time being and will be inactive. This enhancement may be moved to the In Progress or Prioritized stages in the future to continue development.
The decision-makers have decided not to implement the product enhancement idea.