Go here for details about the Work Item Selector.

As the PO, ScrumMaster, or Team Lead,

I want to efficient plan the Features assigned to the Team by being able to view both the planned and unplanned child User Stories,

So that, we can quickly make decisions during planning to ensure the Feature work can be completed in this PI; based on capacity, outstanding backlog [work items] still to be scheduled, in addition to all the other variables or priorities that go into planning.

Automatically the Team-level work items view is updated to filter the child work items that are linked to that Feature and still unplanned (in the connected ALM tools backlog area), AND also highlights the existing planned child work items that are linked to the Feature.

Everyone now has an understanding on the remaining scope of work, the time range of the child items that are already planned, and a system view of how the rest of the Teams PI plan is shaping up based on capacity and other priorities. You can now make quick decisions or facilitate creative conversations by using the visual representation of all those variables in order to find the best way to sequence the rest of that Feature work.

As the PO, ScrumMaster, Team Lead, RTE, Business Stakeholder,

I want to quickly verify that all linked child work items for an ART-level Feature are planned into this PI,

So that, we can be assured that all the work related to the scope of a Feature is planned, so that we have a high confidence rate that we will complete that Feature work in this PI timebox. This will ensure we live by the lean-agile principles that make the ART more predictable, and ensure flow. Principles like: 'Stop starting, and start finishing' the work with the highest value, that we deliver value by completing the Feature in this PI timebox and do not leave Features unfinished which increases cycle time, causes delays and context switching.

You have quickly identified outstanding work related to delivering this Feature within the PI timebox.