3 ms·

Your team needs excellent JIRA hygiene for that to actually work. I’ve been on and managed teams where it’s expected and demanded and others where it was an aft

by tbrock 7y ago

Your team needs excellent JIRA hygiene for that to actually work. I’ve been on and managed teams where it’s expected and demanded and others where it was an afterthought.

hrktb 7y ago
I think parent’s point stands: if JIRA is hard and requires excellent discipline, why bother in the firth place, and why not go with a rougher board and the micro status checks only ?
skgoa 7y ago
And if you don't use the tools the way they are meant to, you are just wasting massive amounts of time.
systemtest 7y ago
Our JIRA board is being gamed for management. Our sprint burndown chart always looked terrible because management changed things around mid-sprint by adding issues or swapping them around. So we have a fake JIRA board that has a perfect linear downwards progression because we keep changing the story points. For actually tracking the progression of the sprint we have a secret Slack channel that management can't see. This way we don't have to explain to a spreadsheet monkey why the burndown chart looks like a skyline.
- verinus 7y ago
  this is so anti-agile but well...if management does not understand how developing software works what can you do...
- perlgeek 7y ago
  > Our JIRA board is being gamed for management. Our sprint burndown chart always looked terrible because management changed things around mid-sprint by adding issues or swapping them around. So we have a fake JIRA board that has a perfect linear downwards progression because we keep changing the story points. This makes me so sad. The jagged burndown chart should be the perfect tool to explain management that you didn't finish the sprint BECAUSE MANAGEMENT CHANGED OR ADDED THINGS, and so visualize the cost of such actions.
camgunz 7y ago
Yeah but tools almost always provide automation hooks. You can configure status to update on branch creation, PR creation, merge, deploy, etc. Always be automating.

by tbrock 7y ago

Your team needs excellent JIRA hygiene for that to actually work. I’ve been on and managed teams where it’s expected and demanded and others where it was an afterthought.

hrktb 7y ago

I think parent’s point stands: if JIRA is hard and requires excellent discipline, why bother in the firth place, and why not go with a rougher board and the micro status checks only ?

skgoa 7y ago

And if you don't use the tools the way they are meant to, you are just wasting massive amounts of time.

systemtest 7y ago

Our JIRA board is being gamed for management. Our sprint burndown chart always looked terrible because management changed things around mid-sprint by adding issues or swapping them around. So we have a fake JIRA board that has a perfect linear downwards progression because we keep changing the story points. For actually tracking the progression of the sprint we have a secret Slack channel that management can't see. This way we don't have to explain to a spreadsheet monkey why the burndown chart looks like a skyline.

verinus 7y ago
this is so anti-agile but well...if management does not understand how developing software works what can you do...
perlgeek 7y ago
> Our JIRA board is being gamed for management. Our sprint burndown chart always looked terrible because management changed things around mid-sprint by adding issues or swapping them around. So we have a fake JIRA board that has a perfect linear downwards progression because we keep changing the story points. This makes me so sad. The jagged burndown chart should be the perfect tool to explain management that you didn't finish the sprint BECAUSE MANAGEMENT CHANGED OR ADDED THINGS, and so visualize the cost of such actions.

camgunz 7y ago

Yeah but tools almost always provide automation hooks. You can configure status to update on branch creation, PR creation, merge, deploy, etc. Always be automating.