Jira Workflow

Owned by Maksud Ul Alam
Last updated: Oct 20, 2020
2 min read

Overview

Currently we are following agile scrum and kanban in Jira. A 2 weeks sprint is declare for scrum and work is done in iterative process. We utilize CE Development board under CommEngine project for scrum and it is use for regular software development process. For customer support we follow Kanban model utilizing Customer Issues board .

Working Process

  • Product owner will create product backlog, epic.

  • Sprint meeting will held before start any new sprint.

  • On each sprint meeting developer will peck the story from product backlog. Must set story point against each story in presence of scrum master.

  • Full team with product owner and scrum master should be participate in the sprint meeting.

  • Task priority should be set by product owner or scrum master.

  • Developer should execute task one by one based on priority. Multitasking is not allow.

  • Highest priority is customer issue fixing, Bug fixing then any task .

  • No story should be added in the sprint after it start. Developer can create new sub task under a story in the running sprint.

  • Release will maintain separately and Jira board tasks will tag by the next release version. Scrum master will manage this process.

Board Column Meaning

  • To Do : Contain the stories/tasks need to finish in this current sprint.

  • In Progress : List all tasks currently in development phase. Only one task should be ongoing at a time for any developer.

  • Testing : Development is finish and developer now testing it locally.

  • In Review : After performing pull request against any task it should be move into Review stage. Tech lead will review the code.

  • In Dev Server : After merge code it should be deploy in development server. for QA team to test.

  • Done : Any task will move to done stage when it pass QA testing.