Problem i see too often is that a developer in in more then one scrum team eg. in 3 leads to 3 dailys 3 plannngs ... for this Splithead. So move people to the wor instead of work to the people on a personal NOT Team base . I Find this very very toxic, so a developer is in only ONE team. Rootcause Project Stuffing and understanding that Scrum is an agile project management method. .... What Du you think?
I've been lucky: every Agile (Scrum and other) team I've worked in had "dedicated" developers. Not sure if the Scrum Guide disallows sharing (fo Developers)... but I agree with you that it's bad form.
Today I got PSD I certificate. It was a nice video. But I think the neelxt video should be about mechanical scrum vs Professional Scrum and how to achieve professional scrum
@@Developmentthatpays Not at all, I am afraid. In fact there is not really much interaction as everybody is rather working in isolation and mentally checking out after they presented their progress in the daily scrum, which is obviously too long in in the first place (due to team size). There is no team spirit and we don't have the feeling of working together on the same product. All the developers and managers have waterfall background. But as I am the most junior developer of the team, I am not really heard when making suggestions. Very frustrating situation.
@@rwj_dk - me too! There are a lot of things that have to come together to get to "Scrum Guide compliance"... so I understand why teams would thing that when they get there they are "done". Alas, that's only the beginning.
My main point is that the Scrum framework (and others; especially SAFe) sort of have become too much "in focus" and an "excuse" to not focus on problem solving and improving.... Aka common sense is thrown out the window 😔
