2. My team is 90% contractors. They've been here for years, but constantly complain about the legacy codebase they've been working on. We fail to hit our estimates/deadlines and the response is "we don't understand the codebase".
3. PM complains about our velocity, but nothing changes when I mention that epics need full product requirements and designs so that we can architect things and actually improve the codebase.
4. Sprints are just buckets of random tickets. Sprint goals are for losers.
For 1, I've brought up to my boss that we need more enablement teams and pointed to issues across many different teams that they would solve. Their answer was "hiring freeze, talk with the other managers to solve this".
For 2, I can see how shit the codebase is. I get it. But I've been here half as long and have been explaining how things work to them. I'm exhausted from having to handhold people who are making no effort to learn. I also think there's a significant technical skill gap where these contractors don't know how to architect solutions, but just create code bandaids.
For 3, I've talked with them about it and things change in the near term, but the next feature we work on will be a surprise, dumped on us last minute in sprint planning.
For 4, I talk about focusing on feature delivery, but I guess scrum is just buckets of random tickets???
I'm a pretty experienced manager and I don't know what to do. I want to point to a weak team of contractors and shitty legacy code as reasons, but these things feel like areas I should be able to improve.
