You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm keen to use JIRA to provide data and insight to plan and measure improvement activity. My background is Development, over the last 5 years I've been leading on integration development activity which has used the Atlassian tool-set for the last 3 or so years. Now I've taken a Quality Assurance post to see how lessons learnt can be shared and to ask better questions sooner.
My current focus area is estimating and Story Points. I know it's not healthy to estimate tickets in time but I feel we're missing something if there isn't correlation between Story points and elapsed time (at the moment 5 point and 2 point tickets look no different on time-in-status charts). So I wonder how others plan story points - do they reflect value to the customer, complexity or effort or something else?
Have you been able to demonstrate improvement in the predictability of software delivery?