Pulse Retroactive View
Pulse Retroactive View. Clicking on the iteration filter at the top of your Pulse page will allow you to select previous iterations and receive a detailed report of your activity in that week or spri…
Pulse Retroactive View
Clicking on the iteration filter at the top of your Pulse page will allow you to select previous iterations and receive a detailed report of your activity in that week or sprint.
Planning Accuracy (Scrum)
Planning accuracy measures the ratio between planned issues or story points and what were in fact delivered from that list. Accuracy < 70% indicates potential over-commit. Accuracy > 95% indicates potential under-commit. This percentage is calculated using your Delivery metrics. The number of completed (not including added) issues/story points is divided by the number of planned issue/story points.
Capacity Accuracy (Scrum)
Capacity accuracy measures how many issues/story points your team completed in an iteration (planned and unplanned) compared to the planned amount. Capacity accuracy answers the question: “Is my team taking on an amount of work that they can reasonably accomplish?”
Velocity (Kanban)
Velocity measures the number of issues that were completed on average per week, as well as a weekly breakdown of the number of issues completed in each week.
Delivery
The delivery section breaks down
- Completed - Planned story points or issues completed in a sprint.
- Unplanned - Story points or issues added and completed after the sprint begins. Note that this does not take into account unplanned issues which were not completed.
- Uncompleted - Planned but not completed story points or issues.
- Planned - Story points or issues added before or within 24 hours of a sprint beginning.
Investment Profile
The investment profile page uses data from your project management platform to visualize the investment being made by issue type. LinearB will display all issue types found within the boards connected to your team.
People Effort
This percentage of team members who have completed issues in this iteration or week. A team member will be counted in this metric if they are assigned to an issue when it is moved to "done" status. This number of "active" contributors will be divided by the number of developers in your team.
Delivery Breakdown
Listed on the right of your page are all issues collected for your team in this past iteration. Issues are divided by their status as listed in the Delivery row. Click the "View more" link next to any segment in order to see all issues. Clicking on any issue will take you to your Jira or Shortcut platform to
How did we do?
Pulse Alerts
Pulse naming conventions - Jira