Agile Team Velocity

Target as % of average story points that team completes over multiple sprints/release period.

Learn More

% of Total Story Points

Set target % of Total Story points to members that have limited availability during the reported period. e.g. new starters or team members that fulfill multiple roles.

Learn More

Improve by % vs. period

Set & track target as % of improvement of certain metric vs past period .

Learn More

Personal Velocity

Set personal target based on % of average story points that team achieve and break it down by developers.  For instance Junior devs might be set ~ 40% and Senior ~ 60%.

Learn More

Performance based on complexity

Understand on average time of delivering Stories with certain complexity and evaluate their estimation accuracy.

Learn More

Decrease reopen iterations

Encourage decreasing the number not verified well Stories or Defects: e.g. Max 5% of total issues to exceeding 3 "Reopen iterations".

Learn More

Punctuality of reported defects

Improve QA capability of finding and describing stable reproduce patterns and improve Bug cases content quality. e.g. Max 5% of total Bugs reported by QA team to be closed with resolution 'Not a defect' , 'Duplicate' or 'Can not reproduce'.

Learn More

Decrease time spent in rework

Set objective to decrease time spent in rework e.g. Max 20% of Time Spent to be in bug fixing.

Learn More

Time between events

Track average time spent between any combination of events and break it down to understand more details regarding WIP distribution. e.g. Set target as % of average time from Start Progress to Resolve  for  operations critical issues .

Learn More

Caputure new metrics with simple configurations

Learn how to design and configure objectives aligned with your process. Enhance insights from build-in JIRA metrics.  Capture new metrics like number of specific iterations, time between custom events . Combine them with existing ones and get the picture that fit best to your work flow.