Feature
A feature is a unique and desirable property of a computer program, service or hardware that adds value for the customer. The feature is the core element of the MPT schema, it’s the most common term we use to associate customer value with the work we execute internally.
 

It is important that features and all associated work items be associated with an specific AREA and ITERATION. The iteration also called the milestone establishes priorities and timelines for the features necessary to meet the value proposition, vision. Teams need to determine what features will be delivered in what milestones based on the priority of the features.

Required Fields
Title
: Unique title for the Feature

Feature Group: The parent Feature Group that this Feature is associated with.
    NOTE: The Feature Group must be entered prior to this field being updated. In order for the drop down list to be populated the user must hit the (refresh) button and wait 2 minutes.

Assigned to: Individual responsible for the tracking of the Feature

State: The state of the Feature. The workflow for the states is as follows:
    Active: This is the default starting state. Feature has been approved and work is being completed to execute against this release
    Proposed: Feature is opened and not approved
    Closed: Feature is completed, cut or should be ignored

Sub-State: The sub-state of the Feature. When the State field is closed the sub-state has the following values:
    Completed: All work is completed for the Feature
    Cut: Feature was cut and might be addressed at a later date
    Ignore: Feature was entered in error and should be deleted

Optional Fields
Priority: Priority for the Feature Group. Choices are:
1: Must Have
2: Should Have
3: Nice to Have
4: Wish List

Rank: Numeric field individuals can use to sort their task
 

Rollup Fields
The following fields will automatically rollup if they have children work item types associated with them. Note – this rollup will clobber and existing values.

Start Date: The date the work on the deliverable begins. If there are child tasks associated with this deliverable the earliest start date will be placed in this field.

Finish Date: The date the work on the deliverable will be completed. If there are child tasks associated with this deliverable the latest finish date will be placed in this field.

Completed Work: The duration (hours or days) that have been completed on this deliverable. If there are child tasks associated with this deliverable this will be the sum of all completed work.

Remaining Work: The duration (hours or days) that are left to be completed on this deliverable. If there are child tasks associated with this deliverable this will be the sum of all remaining work.
 

Tabs
Description
: Free form text for the description of the Value Proposition

Links: Linking information

File Attachments: Supporting documentation

History: Standard tab to track all changes to the work item.