Joined devRant on 7/25/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
My company’s upper leadership is sooo focused on the NUMBER of defects that are open on our project and only the number. We give each defect a priority of P0, P1, or P2. You would think this would help prioritize and strategize our plan to fix them. But nope. Every week we have some arbitrary “goal” to hit. A number purely made up by clueless leadership as to what makes a “quality” product.
On Friday’s, managers start harassing devs to merge their fixes and for QA to close out defects. So effectively rushing to hit that arbitrary number or else we’ll have to work Saturday.
Meanwhile they want more test automation coverage to reduce the incoming defect rate. But when the fuck do we have time to develop said tests when all you want is the defect closed to bring down your precious little number?!
They’d rather us close 25 P2 defects to bring the number down rather than 10 P0 or P1 defects. These leaders are so incompetent it kills me! Without any back story, they’re ultimately the reason we’re in this position in the first place! Argghhh!2
Company: lets develop a cutting edge, SaaS software solution that would make our current software obsolete.
Also Company: needs to be fully compatible with IE 11. Oh and also use it as a base for testing performance and UI rendering.