Workflow for Features

Feature States and their Definitions:

As we streamline our backlog management across pods, it is pivotal to align on the life cycle of feature development. Below is a breakdown of different states that our ADO features will go through. We need to ensure that all product and pod leads adhere to this SOP to ensure the features backlogs reflect their true states.

STATE	DETAILS
New	This state indicates that the feature has just been created by Product lead and still under requirements gathering, ideation, and prioritization stage. Design team is likely engaged. Once initial product definition and requirements are completed, it moves to the "Product Review" state.
Product Review	At this point, the feature is discussed and reviewed amongst members of the Product team. The product team may reach out and ask questions of pod leads for feedback, who may provide technical and architectural advice. Design team is engaged and rough mocks are ready. Product and engineering align on a t-shirt estimate. It is now ready for “Engineering Review” discussion.
Engineering Review	Features that are in this stage are awaiting cross pod review. The feature is discussed among engineering pod leads in their regular cadence and t-shirt size estimate is validated. Feature may be accepted as-is OR advised to do further breakdown. Once cross-pod alignment is done, pod leads will breakdown necessary stories. Cross-team dependencies are solidified. Designs should be completed OR near completion. The feature cannot move to ready for development until the final designs are delivered. Once all pod leads are aligned, stories are broken down, then the feature status moves to “Ready for Development”
Ready for Development	In this state, feature is awaiting prioritization and sprint allocation. All stories within the features are in ‘Groomed’ state. Requirements are locked down. No more story additions. Release target is assigned based on capacity. When the work on any of the stories start, then the feature is moved to “Active” state.
Active	At least one story in the feature is in active development and part of sprint. Feature has a target release identified. No new stories should be added to it anymore. When the work on all of the stories are closed and the feature meets acceptance criteria, then the feature move to “Resolved”
Resolved	When the work on all of the stories are closed and the feature meets acceptance criteria, then the feature move to “Resolved”. Feature is now awaiting production release
Closed	Feature is now released in production and marked as 'Closed'
Removed	Features in this state were removed at any stage of the product life cycle. There is no active work happening in this feature.
Deferred	The feature has been deprioritized after going thru refinement and possibly spiking. This feature may be picked up at a later point in time.