Discussions
-
If you could remove one Jira feature tomorrow...
If you could remove one Jira feature tomorrow, what would it be? Maybe, not because it's bad, but because it causes more confusion than value for your teams. For me, it's interesting how some features seem great in theory but end up being rarely used, misunderstood, or creating extra admin overhead. I'm curious what you'd…
-
Who tells your team when another team's ticket slips?
Quick disclosure: I'm a solo developer and I've built a Jira app for exactly this problem (Tripwire). I've lost count of the sprint reviews that went like this. A story didn't ship. Not because anyone dropped it, and not because the estimate was wrong. It was blocked on another team's ticket, and at some point that ticket…
-
What's the ideal length of a standup?
I was part of many teams over the length of my career, and I keep finding 2 extremes when it comes to standups: they either last under 10 minutes or they go on for almost an hours. It's no surprise to anyone, that I prefer the first. Now, what do you think an ideal standup should take? What is your advice for optimizing…
-
Stop running retros until you can answer this one question
Quick disclosure: I'm a solo developer and I've built a Jira app for exactly this problem(Resurface). I've been in many teams where each retro would end with the same action items every time. Everyone agrees they need to be done at the end of the meeting, yet they still come back next time. What's wrong? Are the action…
-
How does your team keep retrospective action items from disappearing?
Our team has been talking about something that seems surprisingly common. Retrospectives usually produce a handful of good action items, but a few sprints later many of them have quietly disappeared. Everyone agreed they were important, but once delivery work takes over, they often lose visibility. I'm curious how other…
-
How do you keep PRs from sitting for days on Bitbucket Cloud?
One of the most common issues with PR is they are stuck in review. Sometimes it takes 3 or 4 days before someone takes a look at them. There is no way to see, like a dashboard of who's waiting, who's reviewing etc. I'm curious how other teams handle this. Do you use anything that nudges people and tracks review turnaround?…
-
At what team size did you feel the need to formalize your Jira workflows?
I've been wondering whether there's a tipping point where "every team does Jira a little differently" stops being sustainable. I'm at a Series D company with around 200 engineers (600+ people overall), and while teams have a lot of autonomy, it also means workflows, issue types, custom fields, and boards can vary quite a…
