|
|
|
|
|
by steveBK123
913 days ago
|
|
Exactly. "Oh no, the team doing all the work and covering for the other team is going to get the incremental resource increases". Yes. If a team is incapable of either doing their job or in advocating for needing more resources to do their job, then they do not get to have more resources. Particularly when another team is covering for this gap, typically, engineering. It never goes the other way right? How many times are PMs picking up JIRA tickets, handling bug fixes, joining on-call rotas, etc type tasks that engineering does? If non-engineering roles/orgs are created to take load of engineering, and are incapable of doing so, then they need not exist. This goes for DevOps/CloudOps/SRE/Support/QA/Product/Project Mgmt/etc. You can run a lean startup consisting entirely of 3 engineers. But you can't run a lean startup consisting entirely of 3 SRE/QA/Product/whathaveyou. This is not a knock on these other orgs/roles. In a well functioning shop, they are essential. But when orgs like Product forget that the tail doesn't wag the dog.. bad things follow for everyone. |
|