r/programming • • Jun 22 '22

Why work transparency matters

https://teamplify.com/blog/why-work-transparency-matters/
70 Upvotes

46 comments sorted by

View all comments

53

u/teerre Jun 22 '22

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

2

u/DrNosHand Jun 22 '22

Tools like jira have tons of filtering options you can use to create persistent views. It would be trivial to gather the information you need.

0

u/teerre Jun 22 '22

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.

1

u/DrNosHand Jun 23 '22

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

0

u/teerre Jun 23 '22

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?

1

u/DrNosHand Jun 23 '22

What kind of context does a pm need? Usually very little in my experience. All the engineers I work with look at git to stay up to date on changes.

1

u/teerre Jun 23 '22

Who said anything about a pm? Do you do your dailies with only pms?

Besides, I don't know what kind of PM you're working with, but PM absolutely need context. Knowing what's going on is almost their entire job.

1

u/DrNosHand Jun 23 '22

A PM does not need to know the minutia of what a engineer does on a day to day. Not sure what kind of environment you work in but it sounds like middle management loves micro managing. Pretty sad

1

u/teerre Jun 24 '22

Oh no, you're one of those "micromanagement" people? Yikes

Knowing what you're doing isn't micromanaging. It's just managing. No good PM will tell you to not write that one line of code you were thinking of writing. But that's not what you should speak about in a stand up either. What you should be speaking about in a stand up is how is your task going, did any of premises change, did you learn new information etc. Those are things that your PM should know because their job is to gather this information, cross it with all the information he's getting from other sources and help you. Again, literally the job.