3 ms·
We don't have one PM/test per dev, no. My team is currently something like 8 devs, 3 testers, 3 PMs. There was an internal shift to change the test/dev ratio t
by ehaughee 12y ago
We don't have one PM/test per dev, no. My team is currently something like 8 devs, 3 testers, 3 PMs. There was an internal shift to change the test/dev ratio to something like 2/3 or 1/3 (I can't remember exactly) instead of matching it. I don't know of a team in my division that has a 1:1 for PM or test to dev.
- 72deluxe 12y agoThanks for the info. Very informative, considering I work in a tiny company and we have 3 developers, with 1 (me) working on the bit that people actually use daily (the entire GUI bit on multiple platforms). I used to work in a larger team in a different company but we only had 1 PM who frustrated us all, sadly. How do they balance 3 PMs? Do they argue between themselves?
- ehaughee 12y agoI can only speak for my team obviously but our product has quite a bit of complexity from both within (features) and without (partner contracts). There is enough work that the PMs typically own different aspects of the project and don't have many chances to step on each other's toes.
- steve-howard 12y agoMy org merged dev and test. I'd say the jury's still out on the wisdom of that move.
- ehaughee 12y agoThat actually may happen a lot more with this "unified engineering" push from Satya.