Quotes About Collaboration

I can see how a relationship with a writer would be an easy thing.

Working with my dad was such a gas. We approached the work in a similar way. We only made two films together when I was an adult, Tucker, and Blown Away, but it was so much fun to play with your parent like that.

A functioning team is more than just a group of people with a common goal. It's a group of people who can work toward that common goal despite having different opinions about how to reach it. No, not everyone has the same say. No, not everyone's opinion will play a part in the end. The boss makes the final decision and will live or hang by that decision.

How do successful leaders respond when someone congratulates them on a good job? They start talking about the great team they've got working for them. How this person or that person stepped up in the effort. Or how everyone really came together to pull through. Why? Because they know what it takes to succeed. It takes a team.

Two monologues do not make a dialogue.

I love to be directed. They can trust me and go.

Hook up with us and see a quick return on your premiums.' I like it, Sammy. Think we can fit it on a bumper sticker? (Dean)

Hank: As unbelievable as you may find this, Scott, we can do some things without your guidance. Warren: You're right, Hank! Why, did you know I went to the bathroom this morning- Hank: Not without Scott! Warren: Yes!

Design by community is not design by committee…design is never democratic."[

The best solutions come from collaboration between the people with the problems to solve and the people who can solve them.

Shared documents aren't shared understanding.

meeting" is often the euphemism we use for unproductive collaboration.

Stories are the building blocks of communication between developers and those who use their work. Story maps organize and structure these building blocks, and thus enhance this communication process — which is the most critical part of software development itself.

Handing off all the details about the story to someone else to build doesn't work. Don't do that.

Try showing up at your doctor's office and giving her your "requirements." Tell her the prescriptions you'd like written and the operations you'd like scheduled. If she's nice, she'll smile and say, "That's interesting; tell me where it hurts.

Try to make your working relationships much more like a good doctor-patient relationship, and much less like a waiter-diner's.

Stories aren't a written form of requirements; telling stories through collaboration with words and pictures is a mechanism that builds shared understanding. Stories aren't the requirements; they're discussions about solving problems for our organization, our customers, and our users that lead to agreements on what to build. Your job isn't to build more software faster: it's to maximize the outcome and impact you get from what you choose to build.

If you're not getting together to have rich discussions about your stories, then you're not really using stories.

This is a workshop, not in a meeting. Meeting is the word that has become a euphemism for unproductive collaboration.

The real goal of using stories is shared understanding.

Insistence that both lead means there won't be any dance.

This is the way things work sometimes, that good things get ideas from each other, say, well now let's go ahead and let her have it all.

Harmony is produced in ministry when everyone seeks to be a servant.

There is no substitute for the strength that blesses a couple when they work together.