Here are three sources of general information on team structure:
Larson, Carl E., and Frank M. J. LaFasto. Teamwork: What Must Go Right; What Can Go Wrong. Newbury Park, Calif.: Sage, 1989. Chapter 3 of this book describes the relationship between project objectives and effective team structures.
Communications of the ACM, October 1993. This issue is devoted to the topic of project organization and management and contains several articles on team structure.
Constantine, Larry L. Constantine on Peopleware. Englewood Cliffs, N.J.: Yourdon Press, 1995. Part 3 of this book describes team structures. Constantine uses Larson and LaFasto's theory as a jumping off point for defining four of his own kinds of teams.
Here are some sources of information on specific team structures:
Brooks, Frederick P., Jr. The Mythical Man-Month, Anniversary Edition. Reading, Mass.: Addison-Wesley, 1995. Chapter 3 of this book describes the chief-programmer team.
Thomsett, Rob. "When the Rubber Hits the Road: A Guide to Implementing Self-Managing Teams," American Programmer, December 1994, 37–45. This article contains a description of self-managed teams and some practical tips on overcoming initial problems with them.
McCarthy, Jim. Dynamics of Software Development. Redmond, Wash.: Microsoft Press, 1995. Rule #7 in this book is "Use Feature Teams." McCarthy explains the ins and outs of feature teams at Microsoft.
Heckel, Paul. The Elements of Friendly Software Design. New York: Warner Books, 1984. Chapter 11 of this book explores the relationship between animated film making and software development. It goes in a different direction than the theater model described in this chapter, but it's in the same spirit.
Martin, James. Rapid Application Development. New York: MacMillan Publishing Company, 1991. Chapter 10 of this book describes the use of SWAT teams within RAD projects.
Peters, Tomas J., and Robert H. Waterman, Jr. In Search of Excellence. New York: Warner Books, 1982. This book contains discussions of several skunkworks projects.
DeMarco, Tom. Why Does Software Cost So Much? New York: Dorset House, 1995. Chapter 13, "The Choir and the Team," proposes that the best way to think about a software-development group is as a choir in which the success of the choir depends at least as much on cooperation as on individual performance.