It’s not enough to be busy, so are the ants. The question is, what are we busy about?
I've noticed many scrum teams that are just starting out focus on keeping everyone busy--is there enough work for all of the developers? All of the testers? UX? Business analysts? And so on. Unfortunately, it often means that the team commits to too much work in its iterations, and in-progress stories roll over from one sprint to the next. How does a Scrum Master help his team get stories to Done? Stop keeping people busy.
Harvard Business Review recently had an article about busyness that highlights the issue:
busyness seems to be most productive when the tasks we busy ourselves with are also meaningful.
Is the Scrum Master or a manager trying to keep team members' plates full, or is the team doing it themselves? Often the behavior the team can be traced back to external influences, so listen to the messages that the team is hearing. Important work shouldn't be left to be done during slack time, so help the team to commit to a realistic amount of work each iteration and have time for learning, improving, and refactoring.