Also, when developers have lots of cross-team and cross-skillset coordination that needs to happen, you can spend the majority meeting, documenting, and reviewing.
Case in point; my Cloud team spends a significant chunk of time coordinating between backend and frontend, Ops, Firmware/Hardware team and DevOps.
Product Owner wants a feature, specs how the feature should look in the frontend, and what the device needs to do when used. Backend has to spec the cloud logic and API glue between them. A feature might need support from DevOps if infrastructure needs to be updated, and Ops needs to know how the feature works to support customers.
It’s a whole lot of talk and documentation so that the amount of time we spend coding is as little as possible. That’s a good thing. If you’re spending the majority of your time writing code, you’re probably doing something wrong.
Also, when developers have lots of cross-team and cross-skillset coordination that needs to happen, you can spend the majority meeting, documenting, and reviewing.
Case in point; my Cloud team spends a significant chunk of time coordinating between backend and frontend, Ops, Firmware/Hardware team and DevOps.
Product Owner wants a feature, specs how the feature should look in the frontend, and what the device needs to do when used. Backend has to spec the cloud logic and API glue between them. A feature might need support from DevOps if infrastructure needs to be updated, and Ops needs to know how the feature works to support customers.
It’s a whole lot of talk and documentation so that the amount of time we spend coding is as little as possible. That’s a good thing. If you’re spending the majority of your time writing code, you’re probably doing something wrong.
10000000000000%
Employers should be psyched, not critical, when the time spent in executing is minimal.
I love starting a project that involves multiple groups and none of the other groups are even ready to start. It’s fucking great.