3 ms·

So, it sounds like you hate your team, and agile just makes it more obvious. So, here are the few quick fixes I see: 1. point out in retro that standups as cu

So, it sounds like you hate your team, and agile just makes it more obvious. So, here are the few quick fixes I see: 1. point out in retro that standups as currently constructed are a waste of time. Tell them you will utilize the law of two feet if they can't be tightened up. 2. Suggest a definition of done. If the product owner doesn't agree it meets requirements, code quality isn't high, and tests aren't there then it's' not fucking done. That means your sprints are implementing too much. 3. Don't pull in more work if other members are struggling to finish something. How can you help them out to make sure their code quality doesn't suffer? If your piece is adjacent to another that is in desperate need of refactoring/code quality improvement, just say that you needed to clean that up to implement your solution. Use that time to de-hackify.

arenaninja 10y ago
'Hate your team' is a little too strong, I think. I may dislike some of their working habits, and I think our code quality would be higher if we took code review seriously (I've been told to not hold back PR approval even on issues like not putting braces on single line if statements - if it runs, it's "good enough"; I'm also the only one to ever write tests). Implementing less isn't an option because we have a hard deadline I see what you're saying in your last point, but on that particular sprint, someone didn't want to do something they had assigned to themselves and pulled in a different story/ticket. I have no issues picking up anything that is still unassigned, and I had mentioned during the daily that I was available if anyone needed help with anything. No one got back to me and I honestly didn't know until later that day that the other story/ticket hadn't even been started. I don't think I should have to talk to individual developers to see if they need help; we're adults and if you can't manage your workload or can't communicate that then I don't have a solution for you

arenaninja 10y ago

'Hate your team' is a little too strong, I think. I may dislike some of their working habits, and I think our code quality would be higher if we took code review seriously (I've been told to not hold back PR approval even on issues like not putting braces on single line if statements - if it runs, it's "good enough"; I'm also the only one to ever write tests). Implementing less isn't an option because we have a hard deadline I see what you're saying in your last point, but on that particular sprint, someone didn't want to do something they had assigned to themselves and pulled in a different story/ticket. I have no issues picking up anything that is still unassigned, and I had mentioned during the daily that I was available if anyone needed help with anything. No one got back to me and I honestly didn't know until later that day that the other story/ticket hadn't even been started. I don't think I should have to talk to individual developers to see if they need help; we're adults and if you can't manage your workload or can't communicate that then I don't have a solution for you