Timeline for How to deal with half my colleagues overriding development processes under the slightest pressure?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2020 at 20:46 | comment | added | IMSoP | @UncleIroh I think that comes down to micro-management vs macro-management. Micro-management says "please provide a written answer to these three helpdesk tickets in this specific order; please ignore any direct contact"; macro-management says "please spend a day clearing the backlog of helpdesk tickets for client X, here is our technical contact there; please check with me if you're uncertain of priorities or whether something is within the agreed scope". There's also a push/pull distinction: in general, the developer initiates contact with the customer, not vice versa. | |
| Jul 7, 2020 at 23:35 | comment | added | jmathew | This is what I feel the best approach is as well. The dev team should defer questions to their boss. I usually like to preface it with a positive. "Yes absolutely, but I need you to run it by Sam first." Then you can start pressuring your boss to make actual priorities. I would recommend this even if your boss always says yes. It adds a bit of friction that weeds out the more casual requests. | |
| Jul 7, 2020 at 23:01 | comment | added | Bardicer | @UncleIroh you are right. It does depend. Different teams handle things differently, and yes a dev should be talking to a dev. Business people should be kept as far away from the devs as possible. That is what I meant by the gatekeeping. Very painful memories of having business people for customers who wanted direct access to my geeks but didn't want me and my geeks having access to theirs. Also, the agile manifesto is not intended to be a bible - agile is all about flexibility and what works for you. But I think we agree on the principle, just some things got lost in translation. | |
| Jul 7, 2020 at 22:26 | comment | added | Uncle Iroh | I think this depends. I can get way more accomplished integrating with a 3rd party vendor if I skip both BAs on both sides and instead get devs interfacing with devs. According to the agile manifesto this is the preferred approach as well. Face-to-Face communication. | |
| Jul 7, 2020 at 16:20 | history | answered | Bardicer | CC BY-SA 4.0 |