If this is you, though, are you really a team? Is this really all one group going toward a single goal?
Three simple questions will help figure this out:
- Do you assign tasks to individuals?
- Do developers do test tasks when the team is crunched? Do testers help with system configurations when the team is trying to get set up for new development?
- When a bug is found in the field, who gets yelled at and tries to figure out how to prevent that kind of problem from making it out to customers again? Your testers? Or your team?
If you're still playing "developer" and "tester" roles, then it doesn't matter whether you call yourself one team or two, you're still restricting yourself. You're still saying that you do your bit, the other guy will do his bit, and if we're all good and lucky, then good things will happen. That's not a team. That's a group of people.
A team is a group of people working toward the same goal. Some have more experience than others in different things, but if you're really a team, then each member will happily do whatever is standing between the team and release.
The difference between a group and a team is very simple:
Teams succeed together and teams fail together.
Groups pass or fail, each individual alone.
If you want to be a team, be a team, not a group.