1 Introduction
1.1  About ZenTao
1.2  How to get support
2 How to Install ZenTao
2.1  Choose the best installation
2.2  ZenTao Cloud
2.3  One-click Installation Package for Windows (Recommended)
2.4  One-click Installation Package for Linux
2.5  Source Code Installation Package (for all Systems)
2.6  Set up Virtualbox for ZenTao
2.7  Softaculous service
3 Upgrade ZenTao
3.1  Choose Upgrade
3.2  Upgrade by source codes (General for all systems)
3.3  Upgrade for one-click installation package for windows users (xampp)
3.4  Upgrade for one-click installation package for Linux
4 Users and Groups
5 Simple Application
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 Stories
6.9  Decompose Tasks
6.10  Report a Bug
6.11  Manage Contacts
6.12  Customization
7 Advanced Application
7.1 Workflow
7.1.1  ZenTao Workflow
7.2 Personal management
7.2.1  My To-dos
7.2.2  My Task, Story and Bug
7.2.3  My Profile
7.3 Product Manager
7.3.1  Manage a Product
7.3.2  Create and Review a Story
7.3.3  Change and Review a Story
7.3.4  Story Status
7.3.5  Notes for Writing a Story
7.3.6  Product Module
7.3.7  Release Plan
7.3.8  Create a Release
7.3.9  Roadmap
7.3.10  Manage Documents
7.3.11  Product Meetings
7.3.12  Project Management, Presentation and Summary
7.3.13  Story Reports
7.4 Project Manager
7.5 Development Team
7.5.1  Project planning meeting and decompose tasks
7.5.2  Claim and update Tasks
7.5.3  Create a Build
7.5.4  Test Task
7.5.5  Resolve a Bug
7.5.6  Manage Documents
7.5.7  Confirm Bugs
7.6 Testing Team
7.6.1  Bug Management
7.6.2  Submit a Bug
7.6.3  Confim and Close a Bug
7.6.4  Activate a Bug
7.6.5  Find a Bug
7.6.6  Test Case
7.6.7  Create a Test Case
7.6.8  Manage a Test Task
7.6.9  Execute Cases and Report Bugs
7.6.10  Reports
8 Configuration
8.1 Maintain ZenTao
8.1.1  Initialize scripts
8.1.2  Back up ZenTao
8.1.3  Recover the deleted
8.1.4  Update Burndown charts
8.2 Deploy ZenTao
8.2.1  Guest Login
8.2.2  Cnfigure Email
8.2.3  Set Super Admin
8.2.4  Configure Static Access
8.2.5  Delete "zentao" from your address
8.2.6  Integrate ZenTao with SVN
8.2.7  Integrate ZenTao with Git
9 Custom Development
9.1  ZenTao Mechanism of Developing
9.2  ZenTao Directory
9.3  Modify files
9.4  ZenTao Database
9.5  Common Modules
9.6  Add features to navigation bar
9.7  Examples: Modify Language Prompt
9.8  Examples: set priority when creating bugs
9.9  Web Editor
9.10  Packaging Standards of ZenTao 1.1
10 Other Relevant Issues
10.1  About third-party code
10.2  ZenTao FAQ
10.3  How to Help ZenTao
10.4  ZenTao Business Service
10.5  Acknowledgement

Claim and update Tasks

2015-09-11 14:21:23
Last edited by xiying guan on 2018-12-06 10:09:57
After task decomposition, all the team members can voluntarily claim the tasks and start to develop. In addition to coding, they should also take some time to update the task status and the time consumed.

1. Claim tasks

According to the principles of Scrum, it works best if everyone can claim the tasks they like to do, which will boost the morale of the teams to a larger extent. Some people may ask what if nobody claims the tasks or only easy tasks are claimed? What if a green hand claims a key task, or the tasks claimed are not balanced? In fact, these are such not problems. Since all the information is open and transparent in ZenTao, you cannot always claim an easy and simple task. Meanwhile, project managers should manange and balance at a macro level, especially for some key tasks which have to be assigned with consideration.

Go to Project-> Task and select the task you want to claim. There are two ways to claim tasks.One is to Assign tasks and the other one is to Edit.

2. Update task status

When the tasks are started, everyone should update the status daily. ZenTao provides some shortcut buttons.

The meaning of Start, Finish and Cancel are self explained. Let's look at Close and Activate.

In ZenTao, there is an optional process, which is the task will be automatically reassigned to the one who created it to verify, once a task is finished. If it is completed, the task will be closed. If not, it will be activated. This is optional rather than required. This is for the traditional management. For of Agile teams, the process can be skipped.

3. Update man-hour consumed

Team members should also update the man hours consumed daily.

  • Estimation is made when the tasks are created. Once the task is started, the field can not be changed. When the task is completed, initial estimation can be  used to compare with the time cosumed to rectify the estimation.
  • Consumed is the man hours that have been consumed in the task.
  • Remained is the hours needed to complete remaining task. If the estimation is zero, it means the task is completed. Please note that I initial estimation time consumed + time remained.
  • All the team members should update their tasks everyday since the Burndown chart is made based on the field of estimated remained time.
Write a Comment
Comment will be posted after it is reviewed.