As most of you already know, Microsoft has released a new version of its IDE, with a public beta program. This version has a new graphic style (following the famous “metro style”) and a lot of new capabilities for developers. You can read about them directly from the public beta SDK.
One of the great things about traveling for my job is that I get more time to catch up on reading while traveling than I often have sitting at home. On a recent trip from Seattle to New York City, I was reading through a Harvard Business Review article on our current recession, and the impact on the technology sector. The article presented an interesting idea which correlates, I believe, to patterns in many SharePoint deployments: increasing productivity without increasing demand leads to resource disparities, to which many companies compensate by decreasing headcount – instead of retooling and reusing those people. That is my theory, anyway.
We’re not talking about the cost of migration tools. We’re not talking about the servers that you’ll have to buy or even the licensing. The true cost of changing to SharePoint is the people costs.
The costs are in the cost of the change itself. They don’t change from product-to-product, but the cost of change is real. Let’s take a look at what it takes to keep from being a victim of the trough of reduced productivity.
Sometimes, you just have to stop trying to fix what is so broken that the cost of fixing doesn’t warrant the benefit. This is especially true of SharePoint governance.
During recent months, my work has focused heavily on helping organizations across all verticals and sizes tackle governance.
As we learned in last Wednesday’s Social Business TweetJam, creating a social business requires a unique combination of people, process and technology. For SharePoint users, the technology is the easy part, but getting the people and process in place can be challenging.
In my inaugural post for the SharePoint Gone Wild blog series, focusing on when governance lacks accountability, I introduced the key business drivers for governance. Now that we’ve addressed that major pain point, to continue this discussion on another challenge: governance lacking in quality.
To truly realize your investment in SharePoint, it is recommended for all organizations to utilize Microsoft SharePoint Designer 2010 (SPD) in at least some capacity. Just like the browser, SPD will let you build SharePoint site components like subsites, lists, libraries, pages, site columns and content types.
The processes surrounding a database driven website like SharePoint can so different than those of a static site, that if you don’t understand it and fail to make the leap, you will be missing out on a lot of ROI.
Static web sites operate on a similar process as files on file shares that most of us are very used to.
There are many ways to get SharePoint 2010 in your school, whether you’re using it as part of a package from a supplier, using a hosting company to host your own SharePoint or using your EES license to host your SharePoint internally.
Earlier this year, Microsoft released the next iteration of its cloud offering for customers: Microsoft Office 365 -including Exchange 2010, SharePoint 2010, Office Web Apps, and Lync 2010. This is a compelling set of cloud-based applications, compared with industry competitors such as Google.
