3 ms·

A lot of this blog post assumes that developers have a voice at the table. In my experience at smaller software companies/startups the model can best be describ

• ryandrake 11y ago
  This happens a lot in companies where the CEO drives product decisions. There's nobody to push back on ideas, so you end up with developers implementing every half-baked idea that comes out of one person's mouth. In grownup companies, where you have a product manager and that person has a boss and that person has a boss, the product manager has to justify his decisions to people and has to get feedback, and perhaps has to convince people before he/she's let loose on the engineers, so you get a lot less time wastage on people's whims. In really big-boy companies, engineering and QA has a stake and can push back on harebrained ideas too! The best places have it where there's a product manager, a project manager, an engineering lead, and a QA lead, and they all are empowered to get into a room and have to agree on whether what we're doing provides business value, whether it's feasible, and if can be done by the deadline. Of course, in any case if you've got senior leadership who engage in seagull management, all bets are off.