Jon Strickler triggered a great discussion about team charters and the items a team needs to be successful from the start. He focused on things like the why, what, who, and when questions.
I had to contribute a few Agile specific items to the list. I feel it is important that the team not only have a charter that governs it from above, but also a contract that governs it from within. For example:
"How will they handle failed tests or failed builds? Are they committed to pair programming or TDD? Are customer demo’s done at sprint review or throughout the iteration? Do standing meetings start on time or when everyone is present? Without these agreements, the team won’t be in sync with one another."