Hacker News new | past | comments | ask | show | jobs | submit login

Nothing very automated I am afraid, but we had enough people who cared to do the admin work to make the figures reliable.

We wanted to get a handle on how often work went backwards in our life cycle, and why it went backward.

We had a JIRA lifecycle hook that asked for the reason for moving from SIT state back to Development state, or from UAT state back to Development state etc..

One of which was defect. A defect either being a confirmation that wasn't implemented as per the spec, or an edge case bug.

Test failures were different, we had automated testing so test case failures were picked up before the ticket moved on in the lifecycle.

We could also move completed tickets from Deployed to Review, if a production error was linked to a ticket. This movement could also be tagged as a defect in the same way.

We would then just query the jira database and report on it, by project, by assignee etc..

It wasn't a blame exercise, we were more interested in the % of tickets that moved backwards, and the relative percentages of causes for the move. Another category for example was 'Requirements Changed', we worked with banks, so we had a LOT of these!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: