Quotes About Teamwork

Among males, conflict resolution requires a rapid return to the basics, preferably sports or automotive mechanics.

All right, but if anything happens, I will take Jean. You take Tumen." Fitzwilliam tapped the pommel of his sword. "And Arabella gets the cat," jack said, adding, " hardly a fair fight...poor Bell!

Um exército de ovelhas liderado por um leão derrotaria um exército de leões liderado por uma ovelha". Hooyah.

Passion makes others feel like they are working not for someone but, rather, with others—and working for something bigger than the individuals involved.

Last, you've got to do more leading and less managing. Be a visible and motivating presence.

That's what I have you for," I grinned. "I'm just here to carry the heavy stuff. The union says thinking rolls me into overtime

We spend time as investors thinking about the ability to accelerate or sustain elevated growth, as well as working with management teams to try and minimize the execution risk associated with that growth.

You have any suggestions, make them. I'm in charge but humble. No need to salute when you see me." Fraser said, "Mind if we snicker every once in a while behind your back?" "Hell, no," I said. "Everyone else does.

A week of camp life is worth six months of theoretical teaching in the meeting room.

Robert Baden-Powell

The trick to playing second fiddle is to play it like second Stradivarius.

QA and Development should be working together to ensure the quality of the system. The

Adding manpower to a late project makes it later.

What this team did not realize was that having dirty tests is equivalent to, if not worse than, having no tests.

On the other hand, a system being developed by five different teams, each of which includes seven developers, cannot make progress unless the system is divided into well-defined components with reliably stable interfaces. If no other factors are considered, the architecture of that system will likely evolve into five components—one for each team.

If we really want to spend our days programming, we are going to have to learn to talk to—people.1

The team is working along at a certain productivity. Then new staff is added. Productivity plummets for a few weeks as the new people suck the life out of the old people. Then, hopefully, the new people start to get smart enough to actually contribute.

Professional developers do not prevent others from working in the code. They do not build walls of ownership around code. Rather, they work with each other on as much of the system as they can. They learn from each other by working with each other on other parts of the system.

The most efficient and effective way to review code is to collaborate in writing it.

Professionals work together. You can't work together while you are sitting in corners wearing headphones. So I want you sitting around tables facing each other. I want you to be able to smell each other's fear. I want you to be able to overhear someone's frustrated mutterings. I want serendipitous communication, both verbal and body language. I want you communicating as a unit.

You should choose a set of simple rules that govern the format of your code, and then you should consistently apply those rules. If you are working on a team, then the team should agree to a single set of formatting rules and all members should comply.

Programming is so hard, in fact, that it is beyond the capability of one person to do it well. No matter how skilled you are, you will certainly benefit from another programmer's thoughts and ideas.

Programming is a social activity.

The implication, in the minds of some, was that it certainly appeared that Fletcher wanted to be sure someone else was in change when the fatal blow struck his task force.