I identified some general practices to help you steer your solution development. I divide these practices into two lists: developer constraints and developer guidelines.
Defining the roles and responsibilities can make a big difference for SharePoint’s success and stability. Here, I share my standard roles and responsibilities template that I use as a baseline to organize a SharePoint operations team
I’ve found that SharePoint deployment projects just don’t change that dramatically from each other. For a while now, I’ve based new deployment projects on my project plan template I share here.
SharePoint and Project can work together, facilitating a collaborative project team to plan and manage a project. Using SharePoint’s task list along with Project makes it easy to involve the team and communicate task information.
You can use a SharePoint Community Site to provide a place where different people gather to discuss and share knowledge on a topic of interest. One use, as I describe here, can host a new employee onboarding community.
Health rules in SharePoint notify administrators when something is not quite right with a farm. You can also create your own custom rules to monitor some aspect of your farm.
For quick access to common directories on a SharePoint server, I like to add directory shortcuts to the Link area in Wndows Explorer. In this example, I share my PowerShell script for adding the links.
To control the configuration and release management of the managed metadata taxonomy, I’ve created this script you can use as part of a code promotion and release process.
FAST 2010 can be tricky to configure. Here, I’ve scripted the configuration to simplify the process and control the database naming.