Product owners are probably used to writing the product design requirement document (PRD) or the specification sheets which define the requirements of a product in a very complete word document. But in ZenTao, we advocate a function point approach to identifying requirements. In brief, we extract each function point from the PRD and record it in the ZenTao as an individual function point, which is called user story according to the Scrum methodology. And the user story is to describe user types, user objectives or values of the objectives. With all the information, it’s very convenient to communicate and cooperate with the team.

1. Create a Story

As a product owner, you can edit products'

• The title and module of the Story is required;
• Plan can be left empty temporarily.
• If we check "No Review", the status of this story is active. Only active story can be linked to the projects and then to be developed.
• The 3 cases of "No reivew" by default: a) the story is added by a PO; b) the story is added on Project-Story; 3) Set "No review" in Admin-Custom-Story-Review Required.
• Mailto can be set, so relevant members can be notified about all changes of the story by emails.
• Tags can help you search.

Support multiple image uploads when batch adding requirements.

Click Batch Add. Then click Upload->Add Files.

Images in .jpg, .jpeg, .gif, and .png can be uploaded.

After the images are uploaded, ZenTao will take the name of the image as the title of the story and the image as the content of the requirement.

2. Story tags: T, B, and C

T: for task, indicating the number of tasks broke-down in this story.

B: for bug, indicating the number of bugs linked to this story.

C: for case, indicating the number of cases created for this story.

Tips: Hover your mouse over the letter label and you will see the text description.

3. Review a Story

When creating a story, there is a checkbox "No Review". If checked, the status of the Story is Active. But in most cases, the story needs to be reviewed. Even if there is an assigned person who is in charge of the product, you can also save your ideas as a draft for further actions. The review process of the added story is shown as below.

Here is the specific requirements review process:

• The Review Result includes Pass, Clarify, Reject . If passed, the status of the story will be changed to Active and then it can be linked to a project for development.
• If Clarify, the story will be kept as a draft and reassigned to the one who created it for improvements.
• If rejected, rejection reasons will be provided.
• Reviewed By is the user involved in the review and can be automatically screened by usernames. Generally speaking, story review can be an off-line meeting, and people involved in the review should be recorded in ZenTao.