A clear sign of a broken Scrum process is having daily standups with 5+ people who know/care little about what the other team members do.
Teams need to be tight and involved with eachother, otherwise the standup makes no sense.
What makes this a little difficult is that Scrum™ insists on cross-functional teams, i.e. all teams have a UI guy, a backend developer, a tester, etc. So you can end up with some very disjointed teams, like the one mainframe dude who works on stuff no one understands or cares about. Yet you have to hear about it every. morning.
Teams need to be tight and involved with eachother, otherwise the standup makes no sense.
What makes this a little difficult is that Scrum™ insists on cross-functional teams, i.e. all teams have a UI guy, a backend developer, a tester, etc. So you can end up with some very disjointed teams, like the one mainframe dude who works on stuff no one understands or cares about. Yet you have to hear about it every. morning.