Creating a Change Review for Requirements of a Baselined Release/Sprint
This section describes how to perform changes on requirements of a baselined release or sprint. The figure below shows the process.
| Process | Description |
|---|---|
| Step 1: Trigger the Change Review of Requirements of a Baselined Release or Sprint |
|
| Review experts complete the CR. | |
| The decision-maker completes decision-making on the CR. | |
| Step 4: Requirement Field Values Changed Automatically upon Approval | After the change review is complete, R&D requirements are automatically moved into or out of the pipeline based on the change review conclusion. |
This practice involves the following project roles, as shown in Table 2.
| Member | Role | Responsibility |
|---|---|---|
| Sarah | Project creator (product owner) | Creates a project and sets up a team. |
| Chris | Product manager | Serves as the decision-maker of the CR. |
| Maggie | Developer | Initiates the CR. |
| Frank | System engineer | Serves as a review expert of the CR. |
| Billy | System engineer | Serves as a review expert of the CR. |
| Susan | System engineer | Serves as a review expert of the CR. |
Step 1: Trigger the Change Review of Requirements of a Baselined Release or Sprint
After several rounds of clarification, the requirements for this phase have been finalized and organized in the delivery pipeline, and the pipeline has been baselined. Maggie, a project team member, needs to update the baseline pipeline by removing some requirements and adding new ones. Maggie adds these R&D requirements in a change review to make necessary adjustments. Maggie can also edit the Release or Sprint field of each requirement of a baselined release or baselined sprint to initiate a change.
- Go to the smart watch project, choose Work Item > Req > Plans, and click the baselined release or sprint that contains requirements to be removed from the pipeline. Figure 2 Release/Sprint requirement list page

- Select the requirements to be changed, click Change at the bottom of the list, and click the confirm button in the displayed dialog box.
- Go to the page for creating a CR. The R&D requirements selected in the previous step are automatically added to the Review Objects list in the review ticket. Figure 3 Creating a CR

- Enter the following information and click Submit. A change review is created.
Table 3 CR information Parameter
Description
Example Value
Title
CR title.
The value can contain letters, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses, and spaces.
The value can contain 1 to 256 characters.
Retain the default value generated by the system in this document.
Description
CR description.
The value can contain images, links, letters, digits, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses, and spaces.
The value can contain 1 to 50,000 characters.
CR background: Requirements have been through multiple rounds of clarification, baselined, and entered the R&D pipeline. However, due to the project timeline, some requirements need to be replaced.
CR value: Some R&D requirements need to be replaced. Remove requirements with a long development cycle and add requirements with a short development cycle.
CR details: Refer to the associated files.
If the change is triggered by editing the Release or Sprint field, the system automatically generates a change description.
Review Objects
Object that needs to be reviewed.
The review objects include RR, SF, IR, SR, AR, task, and bug.
Requirements needed to be moved into the pipeline in the R&D requirement list.
Change types include Move in/out of a baseline release or iteration, Modify, and Delete.
For the Move in/out of a baseline release or iteration change type, the change content is the requirement scope of the baseline release or iteration plan that needs to be reviewed.
- For requirements to be removed from the pipeline, click
and change the Release or Sprint field to another release or sprint. - For requirements to be added to the pipeline, click
and change the Release or Sprint field to the current release or sprint.
Decision-Maker: the decision-maker of the review object, who makes decisions on the review object at the decision-making phase of the review.
- When Require Decision-Making is disabled, this parameter is not displayed. That is, if Decision-Maker is not set in the review ticket, the review process will skip the pending decision-making phase.
- When Require Decision-Making is enabled, Decision-Maker is mandatory. You can configure the options of Decision-Maker by choosing Settings > Work Item > Review > Basic Review Settings. The default options are Project admin and Project manager. You can select only one option.
NOTE:To enable Require Decision-Making, go to Settings > Work Item > Review > Basic Review Settings.
Chris
Review Expert: the review expert of the review object, who reviews the review object in the review phase of the review.
Review expert, who reviews the review object in the review phase of the review.
- When Require Decision-Making is enabled, Review Expert is optional. If Review Expert is not selected, the review phase will be skipped.
- If Require Decision-Making is disabled, Review Expert is mandatory. If Decision-Maker is not set in the review ticket, the review process will skip the pending decision-making phase. You can configure the options of Review Experts by choosing Settings > Work Item > Review > Basic Review Settings. Multiple options can be selected.
Billy, Frank, and Susan
- For requirements to be removed from the pipeline, click
- Check the new CR on the review list page. Figure 4 Review list

Step 2: (Review Experts) Complete Review
After the CR is submitted, review experts Billy, Frank, and Susan receive a to-do notification. Review experts access the review details page through the notification card and review the objects.
If the proportion of review experts whose review comments are Approve or Reject reaches the threshold set in , the review phase of this change object ends.
After the review phase of all change objects ends, all change objects under the CR are automatically transitioned to the decision-making phase.
If the review result of a change object is Rejected, the decision-making result will be automatically set to Rejected.
- Access the service homepage and click To-do Center in the upper right corner, or go to the smart watch project and choose . On the Change Review page, select Pending review to check the CRs that need to be reviewed. Figure 5 List of CRs to be reviewed

- Click the CR title to go to the CR details page. Click
in the Operation column of each review object. Alternatively, select the change objects to be reviewed and click Batch Review in the upper right corner.Figure 6 Change review details
- After filling in the information, click OK. The review is in the To be decided state.
Table 4 Expert review parameters Parameter
Description
Example Value
Result
Select a value as required. When Transfer to others is selected, the Review Expert selection box is displayed and you must set this parameter.
Approve
Comments
This parameter is mandatory when Result is set to Approve or Reject.
Approve
Expert Comments
If multiple review experts participate in the review, their review comments will be displayed here.
--
Figure 7 Expert review page
Step 3: (Decision-Maker) Complete Decision-Making
After all review experts complete the review, the decision-maker Chris will receive a to-do notification. Chris will then go to the project to handle the review.
- Access the service homepage and click To-do Center in the upper right corner, or go to the smart watch project and choose Review > Change Review. On the Change Review page, select Pending decision-making to view the CRs that require your decision. Figure 8 Pending decision-making

- Click the title of a CR to go to the CR details page. Click
in the Operation column of each change object. Alternatively, select the change objects to be decided and click Batch Decision-Making in the upper right corner.Figure 9 Decision-making details of the CR
- After the parameters are set according to Table 5, click OK. The CR status is Completed.
Table 5 Decision-making information of the decision-maker Parameter
Description
Example Value
Result
Select a value as required. When Transfer to others is selected, the Reviewer selection box is displayed and you must set this parameter.
Approve
Comments
This parameter is mandatory when Result is set to Approve or Reject.
Approve
Review Result
This parameter indicates the final result of the review.
Passed
Expert Comments
The review results and comments of review experts are displayed here.
--
Figure 10 Decision-making page
Step 4: Requirement Field Values Changed Automatically upon Approval
After the decision-making process of all change objects is complete, the CR status changes to Completed, indicating that the review is completed. Maggie, the review creator, goes to the project after receiving a notification.
- Access the service homepage and click Messages in the upper right corner, or go to the smart watch project and choose . On the Change Review page, select I created to view the created CRs and their review result in the Status column. Figure 11 CR list page

- Click . On the list of requirements of a baselined release or sprint, you can see that the requirements in the current pipeline have been replaced. The R&D requirement change process is complete. Figure 12 Release/Sprint requirement list page after the change

What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot