Timeline for Erratic behavior by an internal employee against an external employee
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2019 at 18:49 | comment | added | HenryM | @Mars added a disclaimer | |
| Aug 12, 2019 at 15:50 | history | edited | HenryM | CC BY-SA 4.0 |
Adding disclaimer suggested by @Mars
|
| Aug 12, 2019 at 6:33 | comment | added | Mars | Hopefully theres a senior guy on the team you can involve in any future discussions about this topic. Loop him in on emails or whatever The sudden change in mailing pattern may not go over well, especially if there isn't a culture for CCing in the first place. I agree that it's probably the right move, but it kind of needs a disclaimer | |
| Aug 9, 2019 at 18:27 | comment | added | HenryM | @Mars, a consultant can be working with people senior to themselves and also people at their own level or below. Where did I say to go over the internal guy's head? I don't think he should say one word about it in scrum ever. Ha. Unless you think filing a bug report is going over someone's head. | |
| Aug 9, 2019 at 5:07 | comment | added | Mars | cont. (But it may help provide a shield if things worsen. It's throwing the internal guy under the bus) | |
| Aug 9, 2019 at 5:06 | comment | added | Mars | I don't think you're grasping the relationships here. 1) Sounds like OP is a dev. External isn't only consulting, especially in other countries. 2) The guy is senior by the fact that he is Internal. That's how these situations work. 3) Reporting it to your own supervisor is fine--typically your voice holds more weight than some stranger who belongs to a client's company. 4) From the comments, it sounds like the internal guy isn't very happy about OP bringing speaking about the bug during scrum already. Going over their head again is NOT going to help the relationship | |
| Aug 9, 2019 at 0:52 | comment | added | HenryM | @Anirudh it sounds to me like you're competent and did your job well. I'd guess that the guy who is so butt hurt is actually responsible for the bug you found or at the very least he was supposed to have found it long before you did. Stop second guessing yourself. Have confidence and don't give any space for that guy to blame you. So the team is asking you why they can't commit? They should read the bug report you made. And if you didn't make one, make it asap. Then you just point them to that. As George says, not really your problem! | |
| Aug 8, 2019 at 21:36 | comment | added | user90842 | Your duty as a consultant is to report the bug. Whatever happens afterwards is not any of your business. But of course you can cover yourself by reporting the bug in writing, and saving that email so that you can show it if you get accused of not doing your job properly. | |
| Aug 8, 2019 at 19:58 | comment | added | Anirudh | Puh! But I want to know if the big got fixed or not...or else my smoke tests were failing and the whole engineering team was upon me asking why they can't commit to master anymore. | |
| Aug 8, 2019 at 19:48 | history | answered | HenryM | CC BY-SA 4.0 |