ZenTao vs. Jira 1 : Basics

2018-03-24 14:35:00
Amber
Original
161

As you might not know that ZenTao back home in China beats Jira according to the Developer Survey China 2017, a survey conducted by Coding Life which is a developer community run by Aliyun which is a cloud product of Alibaba.



37.3% of the respondents claim they use an internally developed tool. In China, there are management tools that are designed for companies. However, they have to use the internally developed tool, due to the special types of some jobs and business. 21% of them claim they use ZenTao as the project management and collaboration Scrum tool. ZenTao is favored by more and more Chinese developers for its open source and professional features.


Introduction

>Jira

Project and issue tracking

Jira is the most popular project management tool worldwide. Its whole process revolves around issues.


>ZenTao

All Lifecycle Management

The main difference between Jira and ZenTao is whether it covers the whole process of software development. The complicated project management in ZenTao is divided into four parts, story management, bug management, task management and case management. Those four parts interrelate with each other in software project management,


Concepts

>Jira


  • Issue: Every task, bug, enhancement request; basically anything to be created and tracked via JIRA is considered an Issue.
  • Project: a collection of issues
  • Workflow: A workflow is simply the series of steps an issue goes through starting from creation to completion.


>ZenTao

ZenTao divides the complex project management into four major items: story, task, bug, and case.Through managing those four, software development project is under monitor and guide.


  • Story: It is the user story in Scrum and describes the requirements from the customer.
  • Task: Decomposed parts of a story.
  • Bug: Defects in Scrum and will be resolved.
  • Case: Test cases that used in test tasks.


Workflow


>Jira

A JIRA workflow is a set of statuses and transitions that an issue moves through during its lifecycle and typically represents processes within your organization. There are default built-in workflows that cannot be edited; however, you can copy and use these workflows to create your own.


>ZenTao

ZenTao has more elaborated workflow, involving all roles in Scrum. Product Owner collects and writes user stories, prioritizing them and making release plans for the whole team. Scrum masters hold various meetings to make sure that the progress of development is on track. Development team complete each sprint and deliver products. QA team test and feedback to Dev teams. The interaction among those roles is explained in the flowchart below.


Now you have a picture of what ZenTao is for. In the following articles, the features of ZenTao and Jira will be compared.


Reference

1. http://www.softwaretestinghelp.com/atlassian-jira-tutorial-1/

2. https://www.quora.com/Why-is-Jira-so-popular

3. https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html

Write a Comment
Comment will be posted once reviewed.