4 ms·
Well, I’d say the first thing to fix is to talk to them and ask them why they find value in being in a separate building and why they don’t want to talk to thei
by scarejunba 8y ago
Well, I’d say the first thing to fix is to talk to them and ask them why they find value in being in a separate building and why they don’t want to talk to their customers. Without strong management, it’s possible it’s because their customers aren’t correctly handled. As for the application, it’s the same thing.
Your engineering team has poor management (though I’d be surprised if it were just them). If you have a Product team, they need to all go.
Assuming that the problem is as stated and I can’t talk to anyone to get a gauge of the situation, here’s what I’d do:
* get rid of Product
* optionally reorganize around conceptual product lines, optionally with separate core services teams if required whose customers are the product developers
* ask engineering to move to some rapid iteration cycle process with demos at every sprint or unit of development cycle
* ask customer teams to send representatives to review demos
* hire the minimal number of PMs to mediate those interactions and to sell engineers on the problems the customers have, providing insight into what their ‘market’ wants, and show how well they’re doing it. They have to believe in the fact that the product is providing someone somewhere value
* make an engineer the ruler of every engineering team’s backlog. prioritization is done with the assistance of the PM’s expertise.
* only production showstoppers go to the OC queue for hotfix, the rest go into the backlog and are prioritized or left to remain in the software
* hire engineers with experience at high salaries and use them as role models
* if you can collocate engineers with non-engineers that would be great. Everyone has to be respectful of each other’s environment, though, so if you have a problem with self-awareness this is not great. (E.g. chatty teams aren’t good next to quiet teams, phone calls are not great near engineers, etc.)
You have a product ownership problem and an interaction problem. Your management is likely crap.
Weak diagnosis but imperfect information so just consider that a low probability Bayesian estimate.
- thrwwyngnr 8y ago> * get rid of Product > You have a product ownership problem and an interaction problem. This is very surprising to hear, but it aligns with other replies here. Your rationale is also sound. I indeed believe that most of our problems around complexity stem from our product team. --- > * ask engineering to move to some rapid iteration cycle process with demos at every sprint or unit of development cycle This is what half of engineering is trying to do. The other half is a bit more cautious, though. Others posters have made a point that we can't have both. --- > * if you can collocate engineers with non-engineers that would be great. Everyone has to be respectful of each other’s environment, though, so if you have a problem with self-awareness this is not great. (E.g. chatty teams aren’t good next to quiet teams, phone calls are not great near engineers, etc.) Sounds like a nice strategy to change everyone else's perception of engineering.