3 ms·
Since a lot of good points have been raised already, I'd though I'd mention something else which have seen happening quite often : Often times development team
by C4stor 6y ago
Since a lot of good points have been raised already, I'd though I'd mention something else which have seen happening quite often :
Often times development teams are applying all kind of processes and reporting
are taken accountable for the bug they make, and are overall held to a high standard of quality. All the company is able to consult the backlog, ask questions, whatever, it seems good, and they're ok with it in general.
But then, the dev team may very well fell like all the other team are basically doing the exact opposite. Maybe the sales team will never admit a single failure to close on its team side, the product one will never admit its specs were flawed, the marketing will never admit its creatives where delivered too late, etc...
And that perceived unfairness may be a deal breaker for engineers in my experience. They don't care for example (or even know) if the sales guys have to go to nightclubs until 1am to land a deal while they clock out a 6.30pm, they value visible equality of treatment.
So to retain certains developers, company wide "fairness" may go a long way. (I use quotes because I'm not 100% sure this is the correct english term).
- ajeet_dhaliwal 6y agoI think this happens often and it’s because of a combination of two things. First the complexity of software development is not well understood by other teams so they can be fairly aggressive when something doesn’t “work” - like how could that happen. and second is that programming types also aren’t as assertive in defending themselves. They take blame and accept responsibility quickly.