The bug thing is particularly frustrating because my "team" (which consists of me and another developer) has consistently reduced the bugs assigned to us down to less than five every single sprint, and those left open are ALWAYS because of outside dependencies that make them unresolvable. But the other developers end up with a lot more bugs, and once we are finished with our list we end up working on theirs. I get that at the end of the day we are all in this together, but it's frustrating that we end up fixing their bugs while they are pulling in more stories.

And oh yeah- our velocity is twice what either of the other two pairs of developers are doing. But that is, of course, because all of the back end stories we work on are pointed too high- so I'm told anyway. Never mind that we are doing full TDD and the other teams are not- some are doing test last and others are just not bothering to unit test at all. I guess that's more evidence that our tasks are just to easy . . .

I just spoke with one of my old teammates from before who is paired with a guy who doesn't even try to write modular code or unit tests. It's driving him bonkers because they just approach software development so differently. And that guy is one of those who complains about QA being too tough on the software. For the life of me I'll never get that attitude. I WANT QA to find every bug there is- I'd rather fix this stuff now than when a user comes up against it . . .

I've made my pitch one more time to my boss (who agrees with me, btw, he just can't get the PO to agree)- to split the teams into completely different areas and work more or less independently. I don't think we are ever going to get our "teams" distinct enough when we are working on related stories in the same area of the program.

At least this thread is helping me feel like I'm not crazy . . . Thanks guys.