The best collaboration happens when the team members are each mindful of the global context, the product objectives, while implementing their part of the work. Collaboration fails when "not my job" is the prevailing mind-set.
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
Really it depends upon the project, scope of the project , size of the team members,although all these factors are considerable the Source code versioning and the documentation part is important among the all types of the projects.
Really it depends upon the project, scope of the project , size of the team members,although all these factors are considerable the Source code versioning is important among the all types of the projects.
The best projects where I worked with others were when I could depend on the others to hand me working code to be integrated with mine.
The worse were when a person would hand me code they swore they had tested and then it failed immediately, no chance that it ever worked.
A great experience I had once was with a programmer I had worked together before with, but not as integrated as this particular project was. He and I sat down, decided what was going to be done, divided the labor, and made clear the interface points between our work and then we went our own directions and when we zipped our code together, it worked fantastically!
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
Some of these tools really aren't very useful in small projects. The development methodology of the project also makes a difference. In older methodologies such as Waterfall, instant messaging and discussions aren't quite as important as in Agile since the requirements are basically written in stone.
In Agile, the requirement process is much more flexible and developers need to have more contact with the customer. Therefore, being able to have contact is much more important.
Without defining what kind of project they were looking to get data on, the results of the poll are somewhat meaningless. Perhaps this poll should have been more specific to the type and size of project it was looking for.
My experience has been that lone wolves are more of a hindrance than a help. They don't collaborate. They go their own way, and pay little attention to the needs of the project or their coworkers. You end up working around them. The net result is project failure, or at best unnecessary delays.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.