Timeline for "team lead" acting as gatekeeper
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2022 at 20:09 | comment | added | 2rs2ts | @Actorclavilis general rule of thumb: if speaking with your manager isn't an option, try speaking with your manager's manager. | |
| Mar 15, 2022 at 16:24 | comment | added | user3067860 | @Stef In the type of project management the OP is describing (Scrum-like), they are working in set blocks of usually 2 weeks. You're given enough work to fill up that block and expected to complete it all within that block. The OP can't even work on the stuff requiring approval first because all of it requires approval (plus other considerations like often some parts rely on other parts being done first which isn't necessarily the most convenient order). | |
| Mar 15, 2022 at 12:51 | comment | added | Thomas Owens | @BrtH I've been in dual developer/Scrum Master roles before. I can't recommend it. It's less harmful in a team-of-team environments where there's someone in a dedicated coaching role across all the teams and people in a dual role on the individual teams. The biggest problem is facilitation - it's extremely difficult to facilitate events while also fully participating in them, with the retro being the hardest of all of them. Just because it's supported by the Scrum Guide doesn't mean that it's a good idea and I just can't endorse it. | |
| Mar 15, 2022 at 11:15 | comment | added | BrtH | @ThomasOwens "Scrum Masters shouldn't be involved in the development of the product". Hard disagree. Assigning a SM from within the team can work very well, provided he gets enough time (and training) for those responsibilities. This way of working is supported in the Scrum Guide. I agree with all the rest though, and especially "nor should they be managers of anyone on the team". | |
| Mar 15, 2022 at 11:10 | comment | added | Stef | In most settings, the second paragraph would be wrong. I am often in situations where I have a deadline, and I know that what I submit must be reviewed by someone else. In my case, it is always my responsibility to submit things early enough so that the deadline is met, accounting for the reviewing time. In some cases, especially for administrative documents, this often means that if a deadline is in september, I have to submit in june, because administration is particularly slow in the summer. If the deadline is missed, I'm going to be at fault for not anticipating the reviewing time. | |
| Mar 14, 2022 at 20:33 | comment | added | Acccumulation | "First, don't apologize for your work missing the release cut when it's not missed because of your fault." That depends on whether they're apologizing on their own behalf, or as a representative of the team. | |
| Mar 14, 2022 at 1:41 | comment | added | Robin Clower | You should have retro every sprint. If your "scrum master" is also too busy to manage that, they need to have fewer teams they're assigned to. Retros are the most important part of scrum and working as a team, so I would also bring up that they should happen more regularly (and if you don't mind rocking the boat, volunteer to schedule and lead them for your team) | |
| Mar 14, 2022 at 0:35 | comment | added | Thomas Owens | @Actorclavilis Definitely a lot of what I would consider anti-patterns here. Scrum Masters shouldn't be involved in the development of the product nor should they be managers of anyone on the team. Not only is too much being asked of one person, but there are conflicts between these different roles. | |
| Mar 13, 2022 at 23:12 | comment | added | fmt | Well, the worst part with that last bit is, he is my nominal manager. I think we've only had one retrospective since I've been here (yes, I know that's not that often) but I will be sure to specifically mention this during the next one. thank you! | |
| Mar 13, 2022 at 23:01 | history | answered | Thomas Owens | CC BY-SA 4.0 |