Project Team Quotes

#1. To middle-class parents, the project team may have seemed unfit for children, but it was exactly what I needed.

Willie Stargell

#2. Software projects fail for one of two general reasons: the project team lacks the knowledge to conduct a software project successfully, or the project team lacks the resolve to conduct a project effectively.

Steve McConnell

#3. Agile Project Management focuses on selecting the right skills for project team members and molding them into productive teams.

Jim Highsmith

#4. To think that we as a publisher (i.e. people who have never actually MADE a game) can have a realistic impact on a project that a team of experts is slaving away on full time for 2 years is a bit arrogant.

Mike Wilson

#5. Even when you have skilled, motivated, hard-working people, the wrong team structure can undercut their efforts instead of catapulting them to success. A poor team structure can increase development time, reduce quality, damage morale, increase turnover, and ultimately lead to project cancellation.

Steve McConnell

#6. This is only one step in a much larger project. I discovered (no, not me: my team) the function of sugar nucleotides in cell metabolism. I want others to understood this, but it is not easy to explain: this is not a very noteworthy deed, and we hardly know even a little.

Luis Federico Leloir

#7. become deeply engaged in their team's project, and

Laura Vanderkam

#8. We need a leader able to project his or her personality and present our policies in today's media environment. All this is true - but we also need a leader capable of building a team, inspiring loyalty from colleagues, and one genuinely open to ideas.

Bob Ainsworth

#9. One of the pieces of advice that we give at YC is: try to work together on a project rather than just doing an interview.

Sam Altman

#10. Cards on a wall is a way of practicing transparency, valuing and respecting the input of each team member. The project manager has the task of translating the cards into whatever format is expected by the rest of the organization.

Kent Beck

#11. McLaren was a risky project because they were completely new, but we are one team - we win and we lose together.

Fernando Alonso

#12. Your team may be called "quality assurance." Don't let that go to your head. Your test results and bug reports provide information that facilitates the assurance of quality on the project, but that assurance results from the effort of the entire team.

Cem Kaner

#13. Jocelyn Bell joined the project as a graduate student in 1965, helping as a member of the construction team and then analysing the paper charts of the sky survey.

Antony Hewish

#14. Admiring remarks of my team as I track down the latest obscure but in the Project Mercury Monitor System.

Gerald M. Weinberg

#15. At this time, my work on the SPS power supplies had just come to an end; I joined a study group on the pp project and an experimental team studying cooling in a small ring (ICE).

Simon Van Der Meer

#16. At least twice a week, I pause in the rush of work and have a meeting with myself. (If I were part of a team, I'd call a team meeting.) I ask myself, again, of the project: "What is this damn thing about?" Keep refining your understanding of the theme; keep narrowing it down.

Steven Pressfield

#17. With film, I have to be a team player; it's a whole different thing. I can't just be a one-man show. I have to learn how to use people to the best of their ability and motivate them to be as passionate about the project as I am.

Ice Cube

#18. I will say that the lead cosmonaut trainer - I mean, we were working with professional cosmonaut trainers outside of Moscow. And the lead one, at the end of the project, announced to the entire group that he wanted Trish [Sie] to be on his team forevermore.

Damian Kulash

#19. It's not that introverts aren't good team players. We just don't need to be in the same room as the rest of the team at all times. We would much prefer to have part of the project carved out for us to squirrel away with it in our offices, consulting as necessary but working independently.

Sophia Dembling

#20. I'm always interested in working with people who are good team players - that are selfless that way in their interests and dedication to the project.

Diane Paulus

#21. 'The chef on duty will constantly point out the time, name the next project, and finish with 'push!' The entire team then calls it back. It is a simple one, but it gives me goosebumps every time.

Jorge Hernandez

#22. A well-functioning team of adequate people will complete a project almost regardless of the process or technology they are asked to use (although the process and technology may help or hinder them along the way).

Alistair Cockburn

#23. team factors for agile project success: the dedicated team and the cross-functional team.

Mark C. Layton

#24. Nobody knows how Honda is organized, except that it uses lots of project teams and is quite flexible.

Kenichi Ohmae

#25. I like the team effort of everyone pulling together to make one good project.

Gregg Sulkin

#26. At the end of the day, though, there are a huge number of considerations that our management team go through before accepting any project - checking out the license is just one of them.

Andrew Oliver

#27. Give your product a personality. 37signals may not sell the best project management software in the world, but it has personality. The 37signals team stands for something: uncompromising simplicity. Want an extra feature? Tough. If you want features, buy something else.

Neil Davidson

#28. But typically for a project like the Mac, the size we had was pretty good. And it has different stages. The team grows as you have to write manuals and do testing ... though the Mac had no formal testing.

Andy Hertzfeld

#29. Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redefined. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down.

Robert C. Martin

#30. In an agile project the team takes care of the tasks and the project leader takes care of the team.

Jim Highsmith

#31. Agile project leaders help their team balance at the edge of chaos - some structure, but not too much; adequate documentation, but not too much; some up-front architecture work, but not too much. Finding these balance points is the "art" of agile leadership.

Jim Highsmith