Understanding JIRA Velocity Chart

Problem You might see multiple/difference burn down and velocity charts for the same Sprint. Cause: The most important thing to note about Jira Velocity Chart: It's board-specific, which means it'll only include issues that match your board's saved filter. It's based on your board's column mapping. An issue is considered…

Continue Reading Understanding JIRA Velocity Chart

Tips: JIRA Burndown Chart is missing ideal line (guideline)

Symptoms Assume that you started the Sprint at 12/Apr/21 6:11 AM and the guideline is missing in the JIRA burndown chart Cause There are several possible causes as Atlassian explained: This is expected behavior if the sprint was started before assigning any tasks to the sprint. Hence the guideline is…

Continue Reading Tips: JIRA Burndown Chart is missing ideal line (guideline)

User Story Mapping and Release Plan in Agile

In the previous post, I described levels of Agile planning, and Release planning is a step that we need to have a tactical and actionable plan for a release. In this plan, it might contain product backlog items including user stories and tasks. The question is how to come up…

Continue Reading User Story Mapping and Release Plan in Agile

JIRA filter issues by unique Sprint

Problem Some JIRA items might run across multiple Sprints You want to filter the issues newly added to the Sprint only For example Sprint 1 (ID: 3001): Item1, Item2, Item3 Sprint 2 (ID: 3002): Item3 (due to Item3 is not completed in the Sprint 1), Item4, Item5 Sprint 3 (ID:…

Continue Reading JIRA filter issues by unique Sprint