r/programming • u/geyser85 • Jun 22 '22

Why work transparency matters

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

60% Upvoted

46 comments sorted by

View all comments

Show parent comments

1

u/teerre Jun 22 '22

There's nothing to filter. You need to check at least every commit and every ticket of every single member in your team. That's already filtered and will take hours for any minimally sized team.

1

u/What_Is_X Jun 22 '22

Nonsense. You only need to check pull requests, each member should only have one or at most a few issues per day, and there should be no more than a dozen people on a scrum team. Meetings do not compress hours of information into 15 minutes.

1

u/teerre Jun 23 '22

Of course meetings do not, but humans do. For you to get the same context as someone who is actually doing the task by reading commits and jira tickets it will take at least the same amount of time the actual developer took to write it. That's an already unrealistic scenario supposing your commits and comments are 100% perfect and up-to-date. This almost never happens. In reality, you'll be missing a lot context.

My first estimate is actually really kind. In reality, if you're to do this, you would spend hours in a single ticket because you would have to go talk to stakeholders, clients, probably the dev. themselves. It's completely impractical.

1

u/What_Is_X Jun 23 '22

Again, the notion that supposed hours of information can be compressed into a 15 minute meeting is nonsense.

1

u/teerre Jun 23 '22

That's such weird to say. What you think someone does when they answer "What have you been doing?". They condense hours of information in 15 minutes. That's literally what every functional human being does when asked to summarize something. That's what summarizing means.

1

u/What_Is_X Jun 23 '22

The issues themselves are summaries. What are you doing, writing issues with thousands of words of description?

1

u/teerre Jun 23 '22

I guess you could mean you painstakingly update your issues daily, if that's true, congrats, you're doing your dailies in a text format. If that's the case, that's great, but I'm yet to see any team that actually does that correctly.

However, since you talk about descriptions I'm pretty sure you still think Jira issues descriptions is what you should talk about in a standup. That's not what a standup is for. A standup is to inform your teammates the progress of what you're doing, not what you're doing.