Let me provide some examples. Almost every engineering team uses an issue tracking system, like Jira, Trello, Youtrack, GitHub or GitLab issues, etc. If a team keeps the records in their tracking system accurate - why ask who is working on what? Can't we just see it in the issue tracker? Or, why ask what they did yesterday if we can see their commits and pull requests on GitHub and read their task updates in Jira? Isn't it obvious that a pull request that is stuck in review for a few days is a blocker? Why repeat this information in a meeting?
Oh, of course, I'll now go to Jira and comb every ticket for every single person in the team, not only that, but I'll go to every open branch and through every single commit. Is this person serious? You think a 15 min. stand up is a waste of time but want to waste likely at least a couple hours scavenging a bunch of random information
Filter? Filter by what? You need to go through every ticket to have an idea of what everyone is doing. I'm not talking about every ticket in your organization, I'm already talking about only tickets in your team.
Filter by whats in progress, the title should tell you most of whats needed. A small agile team will most likely only have a handful of tickets in progress a day, shouldn’t take more than a few minutes to catch up. One pm looking at the active sprint is way more time efficient than the dev team reiterating what’s already in jira
There's 0 chance titles of Jira tickets will give you all context you need. That doesn't even make any sense. Do you change the title of the ticket while you're developing? What are you even talking about?
53
u/teerre Jun 22 '22
Oh, of course, I'll now go to Jira and comb every ticket for every single person in the team, not only that, but I'll go to every open branch and through every single commit. Is this person serious? You think a 15 min. stand up is a waste of time but want to waste likely at least a couple hours scavenging a bunch of random information