Building the Right Road Map

By Errin O'Connor

October 27, 2010 — (Page 1 of 3)
Many organizations are either in the process of upgrading to SharePoint 2010, preparing to upgrade, or in the process of developing their “internal road map” for the future due to all the available functionality in SharePoint 2010. In the past couple weeks, I have had conversations around such topics as:

•   Our organization has SharePoint 2007, but we also have LiveLink and want to move away from it to 2010. Where do we start?
•   My healthcare organization has a ton of PII-related data in SharePoint 2007, and we want to clean it out before moving to 2010. How do we do that?
•   SharePoint Designer 2010 blurs the lines of the Information Worker and the Development team, so what do we do about workflows? Should we go with SharePoint Designer, Visual Studio, Visio 2010 or another third-party solution?
•   How do we start to develop our enterprise content types? We have a retention schedule, but it has 600 fields in it. How does that translate into SharePoint?
•   We have had eRoom for five years and want to migrate to SharePoint 2010, but we want to change the navigational hierarchy and clean up our data prior to the move.
•   Our organization has SharePoint 2003 and Project Server 2007. How do we properly implement new SharePoint 2010 sites?
•   We have a ton of SQL Reporting Service reports built with SharePoint 2007, but our executives want reporting with dashboards and KPIs. How best should we implement PerformancePoint 2010?
•   We have Tier 1 and Tier 2 teams, but where does development fit into the equation? How do we set up a support model and what are the true roles and responsibilities we should implement for SharePoint 2010?

These are just a few of the issues facing organizations today. Your IT (SharePoint and Information Architecture Strategy) road map is key. So many organizations out there planned to move off their file shares into SharePoint 2007 but never did... Why is that? Well, there are all sorts of reasons why, but I can tell you from speaking to clients every day that this is going to end up happening all over the country in the next 12–24 months.

Pages 1 2 3

Share this link: https://sptechweb.com/link/34840

Writing the right requirements — Part III Getting your requirements in understandable and actionable statements is a critical step toward implementation

Writing the right requirements — Part II In this installment, Eric Riz explains how to get the most input from everyone involved in the SharePoint deployment

Writing the right requirements — Part I In order to define the right requirements, one must first obtain the proper frame of reference from team members

Add comment

Name*
Email*
Country

Compose

Building the Right Road Map

By Errin O'Connor

Related Articles

Add comment