- 1. A Brief Overview of ZenTao
2. Best Practices Comparison: ZenTao VS Jira
- 2.1 Best practices of Project in ZenTao vs Jira
- 2.2 Best practices of Workflow in ZenTao vs Jira
- 2.3 Best practices of Stories in ZenTao vs Jira
- 2.4 Best practices of Roadmap in ZenTao vs Jira
- 2.5 Best practices of Users and Roles in ZenTao vs Jira
- 2.6 Best practices of Reports in ZenTao vs Jira
- 2.7 Best practices of Dashboards in ZenTao vs Jira
- 2.8 Best practices of Search in ZenTao vs Jira
- 2.9 Best Practices of Agile in ZenTao
- 2.10 Best Practices of Waterfall in ZenTao
- 2.11 Best Practices of Automation in ZenTao vs Jira
- 2.12 Best Practices of Requirements & Test case management in ZenTao vs Jira
- 3. Use cases Comparison: ZenTao VS Jira
- 4. Get started with ZenTao
- 5. Import Jira Data to ZenTao Tutorial
- 6. Reference: Glossary of items in ZenTao VS Jira
For Software Development teams
- 2022-08-04 14:33:25
- WANG JING
- Last edited by Yujia Li on 2022-11-14 10:52:30
- Share links
Jira Software provides planning and roadmap tools so teams can manage stakeholders, budgets, and feature requirements from day one. Jira integrates with a variety of CI/CD tools to facilitate transparency throughout the software development life cycle. When it’s ready to deploy, live production code status information is surfaced in the Jira issue. Integrated feature flagging tools allow teams to roll out new features gradually and safely.
You need the following operations to complete：
- Release planning
- Sprint planning
- CI/CD integrations
- Issue management
- Project Backlog
- Jira Service Management integration（It is another charging tool）
- Feature flagging（Better visibility into releases with Jira and LaunchDarkly And manage and coordinate releases with Jira and Split）
- Developer tool integrations（more integrations need to choose）
ZenTao has a complete R&D operation process. 5~9 team members for a Sprint, including developers, testers, designers, etc. Agile development advocates a free and open environment, so the team is self-managed.
1. Iteration Planning Meeting
The Scrum Master and the Development Team decompose stories with the PO.
At this meeting, the team should：
- Fully understand the stories and speak your opinions to ensure that you understand them correctly.
- When decomposing stories, each team member should participate.
- After the task splitting, the team should claim the tasks rather than be assigned to tasks.
2. Development Task
After the task is decomposed and assigned, the Development Team starts the development:
- Daily development > Continuously improve features
- Update task status > Start, Finish, Close, Cancel, and Activate tasks
- Log efforts > Working hours consumed and remained, Work content Daily Stand-up
3. Create Build
After several features have been done, a build can be created. A build is to clarify the test scope and to facilitate the interaction between testers and developers to fix issues among builds and bugs.
4. Submit Request
After a build is created, it should be submitted to the test team for testing. A test request will be created in the Test view. The request specifies the build, duration, owner, etc. Bugs found in the test will be reported for the next round of development tasks.
- ZDOO Cloud
- Request Demo
- Tech Forum
- Private Policy
- Term of Use
- Google Groups
- Leave a Message
- Email: firstname.lastname@example.org