Change management is an essential process in story management. Story change is not complicated, but it can be complicated when the scope that a change can impact is not clear. In traditional project management, a project manager cannot define the impact due to the lack of software. In ZenTao, stories, tasks, bugs, and cases are integrated, so the impact scope can be defined.

The workflow of story change is shown as below,

1. Change Request

ZenTao provides a professional workflow of change request. Any changes to the requirement Title, Description, Acceptance Criteria and attachments of a story must go through the change workflow. After the change, the requirement status is Changed.

• You cannot change the titles, descriptions, acceptance criteria or files of a story by clicking the Edit button on the page.
• When changing a story, if you checked "No Review", the story will be automatically activated and the review process can be skipped.
• When a story is changed, the scope of impact of that requirement change is listed.
• You can view the change before and after on the detailed page of the story.

Click the Change button in Actions of the Story to change.

2. Review Story

• You can Pass, To Be Clarified, or Revert the story change. If Pass, the status of the story will be changed from Changed to Active.
• If you select the Revert, the change will be canceled and the story will be the same as the previous version.
• If you select the To Be Clarified, the reason should be provided.
• Impact of change will be displayed for review as well.

3. Confirm Change Request

When the story change is done, the development teams and QA team should confirm the changes.

You can check the project tasks, bugs and use cases affected by the changed requirement in the Change > Influence. Once the change has passed the review, you need to do the corresponding confirmation.