

deleted by creator
My home has windows, but sometimes I play with the penguins in the backyard
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
Dass sie sich damit schaden, halte ich für unwahrscheinlich. Zum Einen bedarf es an technischem Know-How, zu verstehen, was für eine Tragweite das eigentlich hat oder haben kann und zum Anderen zählt am Ende des Tages das Angebot beim Neueinstieg oder der Aufwand, davon weg zu kommen. Ich würde behaupten, in einem halben oder ganzen Jahr spricht da niemand mehr drüber
They are advocating for agile, therefore if you challenge anything about their direction, they will invoke the magic Agile word to silence criticism about their methods.
It should be seen as a method that can be adjusted to the team, but this attitude blocks adjustments and improvements even before they start. Its even worse, people will just do anything “Scrum” tells them and reflecting, especially learning from the previous lessons, gets silently lost since the impression overcomes, that it is not allowed. From management side this is fully approved, I mean these people are expensive Scrum Masters, so they know what they do.
As you mentioned the team is the source of success, not the method itself. The “Don’t” stated previously is on point there:
You’re bending your team/process to fit agile, and not bending agile to fit your team/process
deleted by creator
And this may answers the question, who thought that developers shouldn’t talk about technical stuff in all of this process. Feels like enthusiasts meet up to talk about all but the common things.
deleted by creator