- 1 Introduction
- 2 Installation
- 2.1 Choose the right installation
- 2.2 ZenTao Cloud
- 2.3 One-click Installation for Windows
- 2.4 One-click Installation for Linux
- 2.5 Installation with Lampp
- 2.6 Source Code Installation for macOS
- 2.7 XAMPP-VM Installation for macOS
- 2.8 XAMPP Installation for macOS
- 2.9 Source Code Installation (for all systems)
- 2.10 Set up Virtualbox for ZenTao
- 2.11 Softaculous service
- 2.12 Integrate Zdoo
- 2.13 Install Ioncube
- 3 Update
- 3.1 Update ZenTao
- 3.2 Update by source code (for all systems)
- 3.3 Update for one-click installation for Windows (xampp)
- 3.4 Update for one-click installation package for Linux
- 4 Users and Groups
- 5 Quick Start
- 6 Basic Application
- 6.1 Basic Workflow
- 6.2 Agile and Scrum
- 6.3 ZenTao and Scrum
- 6.4 ZenTao Tutorial for Rookies
- 6.5 Create a Product
- 6.6 Create a Story
- 6.7 Create a Project
- 6.8 Confirm a Story
- 6.9 Task Breakdown
- 6.10 Report a Bug
- 6.11 Manage Contacts
- 6.12 Customization
- 6.13 Import Excel, CSV files
- 6.14 Document Management
- 6.15 Operation Mode
- 6.16 Points
- 6.17 Customize Required Field
- 6.18 Access Control
- 7 Advanced Application
- 7.1 Workflow
- 7.1.1 ZenTao Workflow
- 7.2 Individual management
- 7.3 For Product Owner
- 7.3.1 Manage a Product
- 7.3.2 Manage a Product Line
- 7.3.3 Create and Review a Story
- 7.3.4 Change and Review a Story
- 7.3.5 Status and stage
- 7.3.6 Notes for Writing a Story
- 7.3.7 Product Module
- 7.3.8 Release Plan
- 7.3.9 Create a Release
- 7.3.10 Roadmap
- 7.3.11 Documents
- 7.3.12 Planning Meetings
- 7.3.13 Daily Scrum, Review and Retrospective Meetings
- 7.3.14 Story Reports
- 7.4 For Project Manager
- 7.4.1 Create a Project
- 7.4.2 Set up a Team
- 7.4.3 Confirm a Story
- 7.4.4 Story Breakdown
- 7.4.5 Daily Standup Meetings
- 7.4.6 Check Project Progress via Burndown Chart
- 7.4.7 Check Project Progress via Lists
- 7.4.8 Review and Retrospective Meetings
- 7.4.9 Basic reports on tasks
- 7.5 For Development Team
- 7.5.1 Project planning meeting and task breakdown
- 7.5.2 Claim tasks and update efforts
- 7.5.3 Kanban and Tree Diagram
- 7.5.4 Build
- 7.5.5 Test
- 7.5.6 Resolve a Bug
- 7.5.7 Documents
- 7.5.8 Confirm Bugs
- 7.6 For QA Team
- 8 Configuration
- 8.1 Maintain ZenTao
- 8.1.1 Initialize scripts
- 8.1.2 Data Backup
- 8.1.3 Recover the Deleted
- 8.1.4 Update Burndown charts
- 8.1.5 ZenTao remote host
- 8.2 Deploy ZenTao
- 9 Customization
- 9.1 ZenTao customization
- 9.2 ZenTao Directory
- 9.3 Locate and Change Files
- 9.4 ZenTao Database Structure
- 9.5 Common Modules
- 9.6 Add Features to Menu
- 9.7 Set Privileges to Modules
- 9.8 Examples: modify language prompt
- 9.9 Examples: set priority when creating bugs
- 9.10 Web Editor
- 9.11 ZenTao Packaging Standards 1.1
- 10 MIsc
Product owners are used to writing stories or specifications which contains requirements about a product in a Word file. However, we suggest that stories in ZenTao be written by functions. To put it simply, stories are excerpted from the original Word file and recorded in ZenTao as separate stories. According to Scrum, it is a user story which 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
- Log in as a product owner;
- Go the Product->Story.
Click the Add Story button at the right, and the page of Add a Story will pop out.
- The title and module of the Story is required;
- Plan can be left empty temporarily.
- Check "No Review", so the Story that is Active right after you click "Save". Only Active story can be linked to the projects and then to be developed.
- "No reivew" is set by default when 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.
You can also upload images as stories. 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 its content.
2. Story tags: T, B, and C
T: for task, indicating the number of tasks included in this story WBS.
B: for bug, indicating the number of bugs linked to this story.
C: for case, indicating the number of cases created for this story.
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.
Choose the Story that needs to be reviewed, and click the Review button. Make sure you didn't check "No Review" and that a Reviewer has been selected.
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. The reasons include,
- 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.