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. Story Change

ZenTao provides a professional workflow of story change. Any changes to the Title, Description, Acceptance Criteria and Files of a story must go by the workflow.

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

• 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 No Review is checked, the story will be automatically activated and the review process can be skipped.
• The impact of Change will be listed when changing a story.
• You can view the change before and after on the detailed page of the story.

2. Story Review

• 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 Revert, the change will be canceled and the story will be the same as the previous version.
• If To Be Clarified, the reason should be provided.
• Impact of change will be displayed for review as well.

3. Confirm Story Change

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