For Software Development teams

2022-08-04 14:33:25
Last edited by Yujia Li on 2022-11-14 10:52:30
Share links
Summary : Introduce the Agile workflow for Dev Team in ZenTao and Jira.

In Jira

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:

  1. Release planning
  2. Sprint planning
  3. CI/CD integrations
  4. Issue management
  5. Project Backlog
  6. Jira Service Management integration(It is another charging tool)
  7. Feature flagging(Better visibility into releases with Jira and LaunchDarkly And manage and coordinate releases with Jira and Split)
  8. Developer tool integrations(more integrations need to choose)


In ZenTao

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.


Write a Comment
Comment will be posted after it is reviewed.