Lean-Agile
Coaching and Training
Other
-
- Also some Useful Tools
Note that we have some Incomplete Pages That Require Work on this site:-)
Note that we have some Incomplete Pages That Require Work on this site:-)
SAFe describes a hierarchy of artifacts that describe systems behavior: Epics, Features and Stories.
A feature is a description of a desired service of behavior of a system that addresses one or more user needs. The development of business features is the responsibility of the Product Manager. Assistance is available from train level business analysts and teams. A feature should be sized such that it could be completed within a Program Increment.
Enabler Features are meant to enable and support the development of business initiatives. These are generally created by system architects.
Features and enablers are prioritized and sized using Cost of Delay and WSJF techniques; and are the primary input to Program Increment Planning. A feature is only used through the end of the PI in which it is completed.
The goal is to have sufficient detail in the feature to enable the agile team to break it down into stories. The following information is typically captured for a feature as well as for recommendations for capturing and working with features:
Additional considerations to include in the description field:
There is a cadence to feature development that aligns with the program increment schedule. Here is a view of the order you will typically see: