New answers tagged

1

Just to add one component to the mix: Try something, then fix it when it doesn't work. This depends pretty heavily on Sarov's answer (if the team doesn't talk, they can't fix stuff), but this is another important component of making Scrum work. For any Scrum team, its first few Sprints are likely to go askew in some way - too much work, not enough work, too ...


3

Think deeply about when and where the team members need to collaborate and build your approach based on that. If the individual disciplines are on separate work streams and rarely need to coordinate then your solution is likely to be less like a traditional Scrum team. Possibly a Kanban framework would be more appropriate and knowledge sharing where it may ...


3

Talk. (I was so tempted to end my answer at just that one word.) Seriously, though - your problem is that you don't have a single, cross-functional Team. You have four teams that call themselves/are called one team. Your developers (and they are all called 'developers' in Scrum parlance) don't need to be generalists, but the goal is still for them to become ...


Top 50 recent answers are included