I found this very interesting article that discusses how to do development in the SharePoint/MOSS 2007 Environment from a team perspective. I've never seen anyone approach team-based development from a SharePoint perspective and although I personally work solo, I thought that some of you might find this article useful in your development teams.
↑ Grab this Headline Animator
Description from the article:
Organizations that select Microsoft Office SharePoint Server 2007 to meet the needs of collaboration and Web presentation business solutions often must supplement the built-in functionality of SharePoint Server. These modifications can take the form of feature enhancements and can include development of Web Parts, custom workflow's (designed using Microsoft Visual Studio and based on Windows Workflow Foundation), Web controls, and custom list and site templates. Alternatively, other types of modifications can include branding—a process by which the organization changes the visual appearance of the SharePoint Server Web application and implements custom navigation, modified look and feel elements (by using custom master page design and style sheets), and images—and integration with back-end line-of-business (LOB) applications, and implementation of custom workflow's designed by using Microsoft Office SharePoint Designer 2007. These two types of development tasks are differentiated by classifying the former as assembly-based development and the latter as artifact-based development; however, the method a single developer uses to approach his or her development is much different from the approach a team takes to collaborate and develop a SharePoint Server solution.
Similar to traditional ASP.NET or Windows Forms development, a single developer often has the flexibility to control all aspects of the project. While a single developer can employ source control as a best practice, the team dimension of development is not present. When attempting to conduct team development, however, you require a valid source control system, along with coping and an understanding of locking, versioning, workspaces, and other concepts related to shared development. Enterprise source control products, such as Microsoft Visual Studio Team System and Microsoft Visual Studio 2005 Team Foundation Server, provide an excellent and scalable environment that allows for the holistic coordination of team development efforts.
However, with solution development in SharePoint Server, the aforementioned types of development often are outside the normal considerations for a team's traditional application development. Enterprises must consider and attempt to construct a team-environment model that accommodates the requirements for SharePoint Server application development.
Here's the link to the article: Click here
~ Robert Shelton