Archive for the ‘Portal’ Category

SharePoint Architecture: Centralized or Decentralized?

Monday, October 11th, 2010

 

By Christian Buckley, SDTimes.com

An important question to answer when moving to SharePoint 2010 is how to design the new environment: centralized, with a traditional, top-down managed portal; or a decentralized environment, featuring user-driven collaboration? Many companies struggle with this decision, and for good reason: These decisions determine how the environment will be managed, how customizations will be supported, and the level of difficulty of future upgrades.

Most organizations are familiar with the centralized environments of intranet portals. Some of the benefits within a centralized SharePoint environment include consistent use of content types and workflows, reduced metadata duplication, and documented customizations that make system updates and platform upgrades much easier. This model is easier for supporting and training end users, managing business processes, controlling information policies, and providing metrics and key performance indicators.

But there are downsides to the centralized model. It takes a lot of design and planning; requires more upfront work and maintenance; requires an increased reliance on governance and formal change control boards; and has difficulty managing across site collections and portals.

Most end users prefer a more decentralized environment where they can control when and how they collaborate. From an administrative standpoint, there are definite advantages, such as little or no planning, very little upfront effort to deploy, and low time/cost to train end users.

With decreased emphasis on taxonomy and business process management, most decentralized systems work across site collections and portals. These systems more closely mirror the consumer-based collaboration platforms users are accustomed to using, such as social networks and microblogging sites.

The downsides to this approach are that they decrease consistency, increase metadata duplication, and make taxonomy management complex. Decentralized environments are also hard to update, support and train on, manage information policies with, and upgrade.

One of the primary benefits of SharePoint 2010 as a platform is the use of services. By deploying shared services at the enterprise level, companies can utilize the flexibility and collaborative benefits of the decentralized model, allowing end users to collaborate organically while still maintaining some degree of control over taxonomy and metadata, source data, InfoPath forms and critical business processes. Sites and site collections can consume these services as needed, but retain local control over every other aspect of their environments.

There still remain administrative impacts, such as the need to define roles and service owners, as well as the need to define your governance model for these services, but overall, SharePoint 2010 offers the enterprise much more power and flexibility that more closely mirrors the ways modern teams connect and collaborate.

Did you like this? Share it:

Developer updates key to SharePoint 2010 release

Monday, October 11th, 2010

 

By David Rubinstein, SDTimes.com

A new focus on developers is among the highlights of SharePoint 2010, details of which were released today at the Microsoft SharePoint Conference 2009.

The fourth release of SharePoint—“the Swiss Army knife of collaboration platforms,” according to Microsoft’s Jeff Teper, corporate vice president of the Office SharePoint Server Group—just got a whole lot more knives, and corkscrews, and scissors.

The three big areas of focus in SharePoint 2010, said Teper, are around developer support, running Internet sites on SharePoint, and running sites in the SharePoint Online hosted environment. A public beta of the new software will be available in November, he added.

The new developer scenarios “are among the most exciting areas,” Teper said. “[Microsoft Office SharePoint Server] 2007 was such a successful release for us. Now, companies have said the infrastructure is up and running, and now they want to move up the chain to higher value business processes.”

To help organizations create more robust applications on SharePoint, Teper said Microsoft made SharePoint a “first-class platform” for Visual Studio, with richer API support. Among the updates in this area is the inclusion of Business Connectivity Services design tools. Developers can use Visual Studio now to create richer BCS applications than was possible using SharePoint Designer.

Another key piece for developers is the introduction with SharePoint 2010 of Sandbox Solutions. If you’re building a custom Web Part, you can run it first in a sandbox to protect your live SharePoint implementation. “This was a big thing developers asked for,” Teper said. “The next step is to run that custom Web Part in the cloud.”

A new Developer Dashboard component that can be added to any SharePoint page provides detailed analytics about timing, requests, resource usage and more, facilitating development and debugging.

For end users, productivity and collaboration enhancements include “a lot of new social networking capabilities,” Teper said, including the ability to tag content for review, search for people, and infer interests from data.

Further, the FAST search technology now built into SharePoint 2010 gives greater relevance to navigational experiences, and the Gemini in-memory database enables “amazing” dashboards to be created via integrations with Excel and SharePoint, Teper said.

Companies using SharePoint for their websites will find a new Ribbon-style page-editing model and one-click editing, as well as support for AJAX, Silverlight and other streaming media, enabling users to more easily bring different sorts of data into SharePoint Internet mashups.

Did you like this? Share it:

Microsoft SharePoint: Three deployment challenges

Saturday, October 9th, 2010

 

by Shane O’Neill, CIO

Enterprise adoption of SharePoint is rapidly on the rise: A new survey from document management company Global 360 reveals that 90 per cent of the survey’s 886 respondents currently use SharePoint, with eight per cent using SharePoint 2010.

Moreover, 67 per cent of those that use SharePoint spread it out enterprise-wide, indicating that SharePoint is not just for the IT department — it’s for all departments.

The survey also highlights how SharePoint is used at organizations. It commonly starts out as a content repository but then transitions to something more dynamic. Sixty-seven percent of survey respondents have extended SharePoint’s use to manage document workflows; 66 per cent use it for portal and web content management; and 56 per cent use it to support business processes.

The idea of using content in SharePoint to improve the business is a major theme of the survey. Of the organizations surveyed, 27 per cent say that over half of the documents stored in SharePoint are used to support mission-critical parts of the business.

But despite widespread adoption as well as improvements in search, workflow and social networking in SharePoint 2010, the SharePoint platform does come with its own set of challenges, according to the survey results.

Out-of-the-Box User Experience Not Great

Only 17.6 per cent of survey respondents feel SharePoint delivers a great out-of-the-box user experience and adequately meets their needs. Conversely, 78 per cent describe SharePoint as somewhat adequate to inadequate, and that it requires additional in-house design and development.

When asked what was the biggest challenge with their SharePoint implementations, 21 per cent of survey respondents said, "lack of an intuitive, easy-to-use interface for business users."

And an inadequate user interface usually means trouble, according to the Global 360 report: "Generic user experiences often lead to slower user adoption, lower productivity by users seeking workarounds to applications that do not meet their needs, and higher costs to rollback and customize applications."

Building Business Applications Takes Time and Effort

SharePoint, particularly SharePoint 2010, has made advances in areas such as social media, offline access and better CRM and ERP integration. But according to the Global 360 report, "the gap between what has been delivered and what can be achieved is still dramatic."

Of the 60 per cent of respondents who noted the SharePoint user experience as inadequate, 47 per cent are building custom applications within their SharePoint environments. And this takes time. Thirty percent of survey respondents cited "development time and effort required to build business applications" as the top challenge when implementing SharePoint.

The report concludes that many organizations hoping to reduce the time, resources and expertise needed to integrate custom apps into SharePoint are considering third-party applications to add business process management, business intelligence and content management features to SharePoint.

Getting IT and Business Users on the Same Page

Employees are exposed to more and more interactive Web apps outside of work, such as Google’s various apps and Facebook, and have come to expect more from their enterprise applications. For this reason, IT needs to involve users in the planning of SharePoint deployments, according to the Global 360 report.

This not always easy, since there can be a disconnect between IT and the business users of an organization. But early user feedback will ultimately speed adoption and reduce the costs of a SharePoint deployment, according to the Global 360 report.

"While planning, purchasing or customizing SharePoint business applications, IT organizations should make a concerted effort to liaison with the business users targeted for the application," notes the report. "Involving users upfront in the design of and experience delivered by SharePoint will improve user adoption, improve productivity and reduce maintenance costs."

Survey Methodology

The Global 360 survey was taken between March and August 2010 by 886 individuals representing 50 industries. The most common were services (24 per cent), public sector (19 per cent) and financial services (12 per cent). Survey respondents represented organizations of all sizes, with 67 per cent of individuals representing firms with over 1,000 employees. 72 per cent of the participants were based in North America, while most of the other participants came from Europe (17 per cent).

Did you like this? Share it:

How one company made SharePoint 2010 more social

Saturday, October 9th, 2010

 

by Shane O’Neill, CIO

The IT group at tech services company Unisys has been thinking about a social networking platform for two years now.

But some recent factors finally put a plan into action: the arrival of a new CEO two years ago who believed strongly in social networking technology and the arrival of Microsoft’s SharePoint 2010 with new social features.

Another motivator for Unisys, which provides various IT services for large corporations and government agencies and has over 25,000 employees worldwide, is that employees and clients have come to expect a "Facebook for the enterprise" as more people use social media outside of work.

"Employees are expecting these social tools in the workplace," says John Knab, director of IT applications at Unisys. "Our senior leadership recognized this, and wanted to apply social tools in a way that could help the business."

Indeed, Facebook-esque features like status updates, microblogs, wikis, community pages, and the ability to tag and share content are spilling into the enterprise. It can be done through corporate microblogging site Yammer and "enterprise 2.0" social software suites from vendors such as SocialText, Jive, Atlassian and NewsGator.

All of these companies’ suites stand on their own but they are also compatible with Microsoft’s sprawling content management platform, SharePoint.

SharePoint 2010 Better, But Not Social Enough

Microsoft, well aware that nimbler enterprise 2.0 companies are selling social software to enterprises, added more social networking features such as wikis, blogs and tagging into SharePoint 2010, released in May.

These enhancements caught Unisys’s eye, a SharePoint customer for six years, and inspired an early upgrade from SharePoint 2007 to SharePoint 2010 through Microsoft’s Rapid Deployment Program that began in January and wrapped up in June.

Yet although the social enhancements in SharePoint 2010 are an improvement, Unisys felt that SharePoint’s MySites — profile pages that include social networking features — were not quite Facebookish enough, and called on enterprise 2.0 vendor and Microsoft partner, NewsGator, to fill in the gaps with more dynamic microblogging, tagging and RSS feeds.

A True Microblogging Platform

"When you get SharePoint 2010 out of the box, it does not create real microblogging. It’s just a wall that doesn’t broadcast out," says Unisys Community Manager Gary Liu.

NewsGator’s Social Sites create a "true Microblogging platform" similar to Twitter and Facebook, adds Liu.

Also, Social Sites distributes a user’s posts more widely and it doesn’t matter where a user does the posting. In SharePoint 2010 only content that is posted on your profile page gets distributed, but if you post something on a community page, that post would not get distributed.

Social Sites in SharePoint 2010 also offer a Web page that aggregates everyone’s RSS feeds where people can tag, rate and comment on sites.

Baking Social Networking into the Workflow

All of this adds up to give Unisys employees what Liu calls "a real Facebook-like experience." Liu is counting on Social Sites features to improve productivity by letting employees easily share what projects they are working on and stop relying on sluggish e-mail correspondence.

Unisys layered the NewsGator Social Sites 1.0 on top of the SharePoint 2010 social components in August and is in the process of upgrading to the just-released Social Sites 1.1. Integrating Social Sites into SharePoint’s MySites costs in the range of $10-$100 per user depending on the size of the implementation and includes a 22 percent annual maintenance fee.

Though Unisys employees are just starting to use Social Sites within SharePoint 2010, Knab and Liu envision that the social tools will soon be part of the daily workflow of all employees.

"We want everyone to arrive for work and go to their personalized news feeds. We want them to have everything in front of them," says Knab, adding that getting social tools on mobile phones and available to partners through an extranet are also on the roadmap.

Knab predicts all of this will come together quickly because employees are accustomed to social media.

"Of course microblogging and social networking are not new to employees," he says. "What’s new is they’ll be doing it for work."

Did you like this? Share it:

Sharing the love–and data–through SharePoint

Thursday, September 30th, 2010

 

By David Becker, CNET News.com

Microsoft wants you to start paying more attention to the "Save As" command.

Instead of the usual habit of saving documents to a hard drive, Microsoft wants you to place them in server-based collaborative "work spaces" that can be accessed by multiple people. Such document sharing is one of the main ideas behind SharePoint, a critical part of Microsoft’s strategy to unite business applications and processes. It’s also viewed as a major motivator for getting businesses to upgrade to current versions of key Microsoft products.

SharePoint began life several years ago as a tool for creating corporate portals that serve as entryways to documents such as human resources forms, but more recently, it has expanded functionality and split.

Windows SharePoint Services, a collection of tools for creating document work spaces and other basic collaboration tasks, is now a free add-on for Windows Server 2003, the latest edition of Microsoft’s server operating systems. Support for SharePoint sites, including the ability to save documents to a public work space with a flick of the Save As command, is built into Office 2003, the latest version of Microsoft’s productivity software.

More elaborate collaboration tasks are handled by SharePoint Portal Server, a collection of tools for managing portals and other jobs. It sells for US$5,619 and currently has about 10 percent of the nascent and highly fractured portal market, in which home-built solutions still predominate, according to research company Nemertes.

SharePoint is part of the foundation of a broad rethinking of the way office workers use computers, Nemertes analyst Melanie Turek said. The idea is to get people to think beyond their desktop and use environments that allow real-time communication such as instant messaging, document collaboration and other tasks.

"I really think Microsoft sees collaboration as kind of underpinning for the way people work together in the future," Turek said. "They’re putting a lot of work behind real-time collaboration. They very much want to make it something that’s easy to deploy."

Nancy McSharry Jensen, Microsoft’s group product manager for collaboration marketing, said SharePoint is a key element of a broader plan for changing the way people work.

"We’ve really set SharePoint up to be this collaboration hub for the Windows desktop," she said. "This is a really integral part of Microsoft’s future strategy."

Jensen added that information "pops up in islands" throughout corporations, but people can’t find it, rendering some business decisions guesswork. "That’s the problem we’re tying to solve," she said.

Further down the road, SharePoint’s role is likely to morph again, said Peter Pawlak, an analyst at research firm Directions on Microsoft. That will occur, as functions for managing common documents and other types of content are embedded into the WinFS file management system used by Longhorn, the next version of Windows.

"The idea of being able to manage access to other types of documents, whether it’s Web content or links to other sites–stuff that SharePoint does today–will partly be handled by the file system in the future," he said. "The file system will be able to search and index documents much better; to make information findable in a sort of standardized and centralized manner."

The combination of WinFS and SharePoint can then become a small-business version of the complex content management software companies such as Documentum and Interwoven sell to Fortune 500 buyers.

"For companies that don’t do structured content publishing, they don’t need the whole content management smorgasbord to take care of their relatively modest needs," Pawlak said. "They’ll be fine with the Microsoft approach."

A shared environment
When it split SharePoint into two products a year ago, Microsoft also folded the line into Office System, a growing family of applications built around its market-leading productivity package. The move wasn’t just a branding exercise, either: Office support is viewed as crucial for the broad adoption of collaboration tools.

Providing a single, unified environment is one of the most important factors in determining the success of a collaboration system, said Jonathan Spira, CEO of research firm Basex. By integrating collaboration tools with the environment office workers spend most of their day in, Microsoft comes closer to meeting this "one-environment rule" than most collaboration systems, he said.

"Given the ubiquity of tools like Word and Outlook, having that as the opening point makes a lot of sense," Spira said. "It’s not yet fully compliant with the one-environment rule, but it’s a good step toward it." He said getting everything talking to everything within the software package is a starting point, because most office work involves components such as Word, Outlook or Excel.

Microsoft’s Jensen agreed, saying any collaboration system that requires office workers to learn a new set of tools is likely to meet resistance. "The end user is saying, ‘I just want to use Office; I just want to use Outlook; I don’t want to learn something new. Let me use what I know how to use,’" she said.

For people already accustomed to using Office, SharePoint makes it easy to start working in a collaborative way, Jensen said. "It gives you a place to put a document. It gives you these collaboration services–document check-in and check-out–and you can share calendars and task lists."

Corillian, an online banking services company, began using current SharePoint technologies shortly after Office 2003 was released last year. Greg Hughes, the company’s corporate technology manager, said integration with Office has been a key factor in enabling workers to quickly get up to speed with collaboration features such as team work spaces and meeting planning.

"One of the nice things about SharePoint is that it’s relatively intuitive; you don’t have to do a lot of training," he said. "And the fact that it integrates so well with the Office suite is a big advantage. Information from SharePoint sites can be leveraged into Office applications, so it’s there, where people are used to doing their work."

Relying on a familiar set of tools is particularly useful with collaboration, Nemertes’ Turek said, because there are bound to be other worker issues with using a collaboration system. Routinely saving documents on a shared server rather than an individual hard drive not only requires fundamental behavioral changes but a shift in attitude.

First, you get people comfortable with tools. Then, you get them to expand their notions of what they should share and whom to share it with, she said.

"Most Americans are a little bit reluctant to share all their information," Turek added. "They don’t want to lose ownership of their ideas."

But the approach can be valuable, because "if everything I do is available for everyone else to see, then everything I do has to meet some standard of excellence," she said. "Management really has to lead people into this style of working."

Getting office workers used to collaboration is one thing, but information technology folks also have to support the idea. Building basic SharePoint functionality into Windows Server 2003 means that companies can employ collaboration gradually, starting with basic tools built into the operating system and Office–and adding applications, as their needs increase.

"In the portal space, you’re typically told, ‘You need an army of consultants to get these things deployed,’" Microsoft’s Jensen said. SharePoint "really gives people the ability to provision a self-service site right out of the box…They start using it as a simple file share replacement, and then, they see there are these other services–like discussion groups and shared calendars–that they can ease into."

Competitive advantage
Gradual, piecemeal employment of SharePoint functions helps distinguish Microsoft from its main competitor in the collaboration/portal/productivity market, IBM’s Lotus division, which has made collaboration the centerpiece of its Workplace family of office software.

"IBM–from the time you open the box, they’re trying to deliver an environment that has a tremendous amount of functionality for all the things you need to do," analyst Spira said. By contrast, Microsoft puts different functionalities in different containers, "with the ability to cross over and put things together one piece at a time," he said. The advantage there is that buyers using Office "are already partly down that Microsoft road," so it’s easier to go the rest of the way.

Incorporating SharePoint functions into the operating system and applications like Office also gives businesses a compelling reason to upgrade to the latest versions of what in most cases are very mature products, Pawlak said.

Microsoft "is trying to keep moving higher up the stack," Pawlak said. "Essentially, simple file sharing is becoming commoditized. Microsoft is trying to find ways to add value and stay competitive. They want to keep bumping up the value that comes with Windows, so they can say, ‘You don’t get this stuff when you buy (software from Linux distributor) Red Hat.’"

Having SharePoint as part of the operating system also creates a reliable foundation, on which software partners can build applications and services that extend collaboration functions. And that kind of plumbing role–as opposed to running the whole show–appears to be Microsoft’s intent, according to analysts and partners.

CorasWorks sells an add-on application for SharePoint that creates a unified environment for using multiple SharePoint sites and related applications. CEO William Rogers said Microsoft has been a supportive, reliable partner.

"I believe they’re very much focused on making sure their platform is ubiquitous and that the partners are building the solutions," he said. "Microsoft is not going to sit around and build Web parts–that’s not their job. It’s up to the partner community to make this approach succeed. It’s the solutions the partners sell that are going to drive the deployment of servers."

Turek agreed that Microsoft leaves room for valuable partners in the collaboration stack. "Microsoft has an opportunity here to stake a very big claim in this space," she said. "Part of the way they’re doing that is by partnering with ISVs (independent software vendors). They don’t want to own everything that has to do with collaboration."

Besides, integrating collaborative functionality totally into the operating system has drawbacks, Pawlak said–most notably that businesses may not know it’s there. Even with businesses that have modern versions of Windows Server and Office, SharePoint use is far from a given, he said.

"I don’t think the awareness is as good as it needs to be," Pawlak said. "The Microsoft sales force and channel is trying to get word out about what you can do with these products, but it’s hard, because the level of complexity is increasing. It’s not as simple as saying, ‘We’ve got a spell checker in our application now.’"

Partners help by adding their own efforts to the marketing mix. "That’s the whole problem with collaboration: It sounds great, but getting people to use the tools is a real challenge," Pawlak said.

Did you like this? Share it:

SharePoint the Reality Series 5 – The SharePoint maturity model – Part 5

Tuesday, September 7th, 2010

 

By Marc Solomon, KMWorld

Assets under (knowledge) management

The vast cultural differences from the beginning to advanced stages of the maturity model cannot be overstated. From the tentative first steps away from the file server to SharePoint as the authoritative gateway to enterprise knowledge assets, it’s a long road indeed.

Knowledge assets no longer revert to individual owners but as an interactive set of team-based contributions—a vision based more on top-down control than on “feel good” collaboration. “Why do I need hard drives,” reasons O’Connor, “if I can store everything on SharePoint? A company that “owns its data” does not wish for it to reside in human silos.

The value that SharePoint provides is understood by the majority of the user community, and its use is spearheaded by business users. Non-techie staff isn’t intimidated by the interfaces, functionality or their newfound roles as power users in customizing their own applications free of IT roadblocks or even programmers.

Additionally, investments are being made to increase SharePoint’s capabilities, such as third-party Web parts and the creation of solution-focused SharePoint templates. When has one reached Stage 4 mastery? The technology of SharePoint is fading into the background. The company is focused on corporate information as an asset for addressing the post-Stage 4 business issues that are sure to follow.   

Did you like this? Share it:

SharePoint the Reality Series 5 – The SharePoint maturity model – Part 4

Monday, September 6th, 2010

By Marc Solomon, KMWorld

Stage 4—development platform

Most of the costs associated with SharePoint trials and errors subside by the end of Stage 3. Now enterprises can cycle through upgrades and build on that know-how in the form of best practices and coding libraries across the full enterprise. Reed says, “The time required by these companies to set up a new SharePoint project is minimal and the quality of their deployment scripts is high.” It’s based on tested and proven code.

We saw an inspired example of such centers of excellence in the service bureau and chargeback model crafted by Dutch-based Rabobank in the third article of this series, so business units can factor SharePoint into business plans and budgets. Showcasing best practices, or what O’Connor calls “the gallery model,” allows the breathing room to circle “all of the above” when it comes to roadmapping future directions. But it also means taking the necessary time and deliberation to build out those capabilities and address competencies that may be in short supply.

From the practical matter of maintaining SharePoint, the gallery model steps up to the post-deployment question all project teams face: Aren’t we on the hook for support if we do this? Code sharing makes it feasible.

Did you like this? Share it:

SharePoint the Reality Series 5 – The SharePoint maturity model – Part 3

Friday, September 3rd, 2010

 

By Marc Solomon, KMWorld

 

Stage 3—open innovation

According to Reed, “The first time someone says to you, ‘I wish people external to our company could access SharePoint,’ you know you’re on your way to Stage 3.”

When an enterprise reaches Stage 3, SharePoint is addressing its business requirements. By now, it’s the definitive data source for unstructured information, and function-specific workflows are being triggered by a blend of custom programming and out-of-the-box capabilities.

That describes the use of on-demand extranet sites developed by Fenwick & West for their legal clients (and covered in the fourth article in this series). The SharePoint plumbing is now extending out to the rest of the MS office portfolio through RSS feeds, inbound e-mail addresses, Excel imports, content type templates and departmental analytics via the Business Data Catalog (BDC), including links to backend systems. With executive dashboards and reporting guidelines come metrics for how well the solution supports intended process or other business improvements.

Even from a purely internal perspective those processes are designed with the capabilities of SharePoint in mind. One telltale sign: business units that require SharePoint delivery to honor helpdesk tickets, expense reports and custom reporting for outside members. We saw another winning example of this in the third article in this series, in which accounting giant Grant Thornton  now ties site creation to its backend time and billing system—key to instilling discipline around the collaboration of its account teams.

Did you like this? Share it:

SharePoint the Reality Series 5 – The SharePoint maturity model – Part 2

Thursday, September 2nd, 2010

 

By Marc Solomon, KMWorld

 

Stage 2—encore performance

Where Stage 1 is about finding the intranet on ramp, Stage 2 is about the ECM infrastructure. To O’Connor, that means building out the core metadata foundation and content types—the guidelines for applying it and ultimately managing the explosion of unstructured information waiting to be reckoned with in nearly any ECM.

That reckoning is driven by an unprecedented explosion in unstructured information. If content is distributed haphazardly, then SharePoint is where content goes to R-O-T (redundant, outdated and trivial). Here’s where a centralized approach to information management is critical to laying the groundwork. Indeed, it’s not a stretch to pin the success of your unfolding maturity model to a consistent, firm and well-communicated metadata foundation. That makes SharePoint not just a storage medium but the gateway into enterprise resource planning (ERP) and legacy databases, or what Edelman calls “the defacto portal to unstructured and structured information.”

The other key fork in the road between Stages 1 and 2 is that the architectural team is beginning to identify (if not master) the finer points of creating repeatable backups and restoring them to production. According to Esperanca, Stage 2 companies have found that SharePoint content and configuration can be moved across environments using backup and restore. As such they have a repeatable deployment process.

Did you like this? Share it:

SharePoint the Reality Series 5 – The SharePoint maturity model – Part 1

Wednesday, September 1st, 2010

 

By Marc Solomon, KMWorld

In the adoption of SharePoint, a four-stage maturity model is a great way to determine where knowledge gaps exist, what facets require additional education and how to help people expand their use of SharePoint. According to Lee Reed, a senior SharePoint strategy consultant with Northridge, departments will not progress in lockstep, which elevates the importance of the maturity model as a benchmarking tool for evaluating progress and showcasing the best practices of adoption leaders. The point, counsels Reed, is to include some “stretch goals” within each maturity level to encourage greater use of the platform.

“What is curious,” says Hugo Esperanca, SharePoint solutions architect and partner at Collaboris, “is that all companies adopting SharePoint seem to go through the same evolution path.” A maturity model helps to prioritize the right functions and how to phase them in to fit your business requirements. The goal is not to accessorize every feature.

Yet many enterprises are distracted by the shiny-toy factor. They focus on new product features instead of their own business priorities in which SharePoint solves their specific business problems. Success is not measured by how many features are turned on but what issues get addressed. To Russ Edelman of Corridor Consulting, that means automating key processes, reducing risks, simplifying cross-unit complexities and finding information more rapidly.

Stage 1—stepping back

Errin O’Connor of EPC Group (epcgroup.net) traces all SharePoint deployment roadmaps to one starting point: What’s the organization trying to achieve? Most are smatterings that reflect both wide opportunities and sponsor indecision. O’Connor believes it’s more instructive to point the question inward than to pivot on all the possible answers to where SharePoint can lead, including:

    * intranet,
    * enterprise content management,
    * extranet,
    * business process automation, and
    * Web 2.0.

Chances are it’s either “all” or at least “some” of the above. Hence, O’Connor favors a phased in or hybrid approach that treats SharePoint as a platform that can accommodate an ever-evolving set of business needs. To Edelman, the roadmap is a timetable for testing readiness, developing consensus and translating intent into commitment. Those translations are adjustments to the roadmap that will later trigger the more detailed program and project plans.

For example, a Stage One deployment may roadmap the release of a firmwide intranet. Support for that goal hinges on anticipating future phases. Otherwise, half-baked site hierarchies and navigation schemas will need to be re-architected in future stages. According to Reed, documents are beginning to migrate from network drives, are stored in one location and are searchable. Some initial list creation occurs as task lists, team calendars, project timelines and Excel imports.

A word of caution to our pre-deployment readers: Stage 1 tends to be a learn-as-we-go proposition with many unsuspected detours masquerading as mission-critical decisions. For example, rollouts are often tripped up by the need to recreate their prior environments from scratch rather than reassembling them through a common toolkit and methodology. Call it the temptation to over-engineer. Call it the need to avoid a nightmare scenario: millions of documents with no permission structure or hierarchy.

As we saw in the second part of this SharePoint series, one best practice in Stage 1 is the emphasis that Children’s Hospital Boston (childrenshospital.org) puts on the critical role that training plays in building both SharePoint skills and the awareness of what it can do.

Did you like this? Share it: