InsefelZhan

@TheOnce-ler so there is a mentality of seeing how much can be stuffed in.

@TheOnce-ler Agile is messy here. It started with the project getting treated as an all you can order buffet, with every department ordering piles of everything without regard to cost because "Agile makes things cheap." An deadline was set and given without regard for what was ordered. We then calculated the project to take about 3.5 years with existing resources, not including deployment. That obviously didn't square with deployment in late 2020. While Agile includes dropping features as a way to meet deadlines, that causes infighting as people protect their own stuff.

@TheOnce-ler I am not necessarily competitive, but rather just extremely sensitive to incentives. Our individual Velocity score seems to be how we are judged. A team member who spent their sprint unblocking people but not completing their own work would hear about it from the project owner.

@Mars haha, true, although I am not a leader at this point and I am not sure if I would be willing to take a management job given the frustrations of my manager.

@JayZ they are trying to implement Scrum in an organization that rewards and organizes absolutely nothing else in teams. You are correct in that it is technically a team goal. But everyone from our product owner (who has a notepad of who's work gets completed and who misses the goal) to our project management software (which keeps track of points completed per person per sprint) doesn't view it that way.

@Shadowzee they honestly just don't want to do it. One guy just doesn't want to write at all. Another views it as job security for bug solutions to reside only in his head. I just gave their official reason as I already come across as not a team player.

@PatriciaShanahan fair point. This experience pushes me away from that management path, but definitely worth considering.