Siebel Field Service Guide > Release Management > Process of Managing Release Manager >

Managing Product Marketing Work for Release Manager (End User)

After administrators configure Release Manager, product marketers can record the progress and results of product design efforts in Siebel Field Service. Their managers can monitor the information that they enter.

This topic contains the following related information:

• Creating Features and Subfeatures
• Adding MRDs and Linking Features
• Monitoring Features and MRDs
• Monitoring Release Items

This task is a step in Process of Managing Release Manager.

Creating Features and Subfeatures

Product marketing managers can use Release Manager to enter new product features and, if appropriate, subfeature components of these features.

To create a feature and subfeatures

1. Navigate to the Release screen, then the Features view.
2. Add a new feature record, and complete the fields as appropriate.

   Some fields are described in the following table.

   Field	Comments
   Status	Select the status of the feature. Color values include: Green. Approved for the release. Yellow. Can include in the release. Red. Not included in the release.
   Priority	Select the priority of the feature relative to other features targeted for the same release.
   Release	Select the name or number of the product release for the feature.
   Product Line	Displays the product line. The value in the Subarea field determines this field value.
   Area	Select the product area associated with the feature.
   Subarea	Select the product subarea associated with the feature. The list of subarea values depends on the value in the Area field.
   EAT Completion Date	Select the Engineering Acceptance Test completion date.
   Source	Select the source of the idea for this feature.
   Account	Select the account that requested the feature or the account to which your company is contractually obligated to deliver the feature.
   Associated Parties	Select the individuals associated with the feature. Set the product marketing manager who manages the feature as Primary.
   Revenue	Select the amount of revenue tied to delivering this feature in the targeted release.

3. If you want to add subfeatures to the feature, then complete the following steps:
   1. Drill down on the Feature field, and click the Subfeatures view tab.
   2. Create new subfeature records, and complete the fields as appropriate.

Adding MRDs and Linking Features

Product marketing managers can group similar features together into an MRD and track the development of the MRD in Release Manager. Authors of the MRDs can attach electronic copies to MRD records.

To add an MRD and link features

1. Navigate to the Release screen, then the Marketing Requirement Documents view.
2. Add a new MRD record, and complete the fields as appropriate.

   Some fields are described in the following table.

   Field	Comments
   Associated Parties	Select the individuals associated with the MRD. Set the author as Primary.
   Release	Select the name or number of the product release associated with the MRD.

3. If you want to associate features with the MRD, then complete the following steps:
   1. Drill down on the MRD number (#) field, and click the Features view tab.
   2. Create new feature records, and complete the fields as appropriate.

Monitoring Features and MRDs

As a release progresses, product marketing managers can use Release Manager to track the status of features and the related release items. In addition, product marketing managers can monitor the features to make sure that they do not overlook important features.

Monitoring Release Items

During the release process, product marketing managers can monitor features to make sure they meet the following criteria:

• MRDs properly specify the features.
• Engineering implements the features.
• QA test plans test the features.
• Technical publications documents describe the features.

Product marketing managers can run queries to identify features that do not meet these criteria. The procedures that follow provide examples.

To query for features without corresponding MRDs, perform the following procedure.

NOTE:  You can follow similar procedures to query for features without corresponding engineering tasks, test plans, or technical publications documents.

To identify features without linked MRDs

1. Navigate to the Release screen, then the Marketing Requirement Documents view.
2. Launch a query with the following parameters:
   • In the Release field, select the current release.
   • In the MRD field, enter NOT(EXISTS(LIKE*)).

During the release process, engineering managers can monitor development plans to make sure that their teams are not working on tasks without corresponding features. To query for engineering tasks without linked features, perform the following procedure.

NOTE:  You can follow similar procedures to query for MRDs, test plans, or technical publications documents without corresponding features.

To identify engineering tasks without linked features

1. Navigate to the Release screen, then the Engineering Tasks view.
2. Launch a query with the following parameters:
   • In the Release field, select the current release.
   • In the Related Features field, enter NOT(EXISTS(LIKE*)).