Timeline for How to handle a Software Architect who doesn't seem competent
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2017 at 11:04 | comment | added | mutt | @Jon If management is siding with the back end team, then you have to focus on the impact on you/your teams work instead of the lack of production from the other team. If they perform really badly, it should show up over time and cause change, but be sure that your work and your teams work is fully on track and any slips caused by the other team are fully documented to show the exact cause for each delay in detail. | |
| Apr 27, 2017 at 5:11 | comment | added | Jon | The problem is that the "management" is siding with the back end team. They trust them more than the front end team | |
| Apr 27, 2017 at 4:55 | comment | added | Wesley Long | This is an "All hands on deck" emergency. Your management needs to send in an audit team to the backend devs IMMEDIATELY. Something tells me you're going to have a lot of disappointment very soon. | |
| Apr 27, 2017 at 4:30 | history | answered | mutt | CC BY-SA 3.0 |