A detailed discussion of these questions can be found in the "Appendix A" section on page 533.
Why write software in teams? What are the real advantages over writing a system on your own?
Describe the telltale signs of good and bad teamwork. What are the prerequisites for good teamwork, and what characterizes bad teamwork?
Compare software teamwork with the construction metaphor (see "DO WE REALLY BUILD SOFTWARE?" on page 177). Does it reveal insights into our teamwork?
Will external or internal factors do the most to ruin the effectiveness of a software development team?
How does a team's size affect the team dynamics?
How can you insulate a team from problems caused by inexperienced members?
What kind of team ...