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

The workflow of story change is shown as below,

1. Story Change

ZenTao provides a professional workflow of story change. Any modifications to the title, description, Acceptance standards and attachments of a story must go by the workflow.

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

• Click Edit button can not go to the page to change the titles, descriptions, verification standards or attachments of a story.
• When changing a story, if No Review is checked, the story will be automatically activated and the review process can be skipped.
• The impact scope will be listed when making changes to a story.

2. Story Review

2.1 View History before and after changes by clicking "+" button.

3. Confirm Story Change

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

3.1 Confirm change on the page of Task.

3.2 Confirm change on the page of Bug.

3.3 Confirm change on the page of Case.