Background on One of Many Similar Situations EPC Group Has Come Across in the Past 24 Months
In working with clients and gathering their business requirements as well as their detailed functional requirements as well as listening to their past experiences in working with SharePoint consultants on previous versions such as SharePoint 2010 or SharePoint 2007, I continue to hear an opinion and small pattern for which I thought I should address.
As an example, a few months ago I was asked to assist in scoping out a full eRoom to SharePoint 2013 migration initiative. There was no existing metadata, the security of eRoom was outdated and not aligned with the business, and the users could not get off of eRoom and into SharePoint 2013 fast enough; a department within the firm had implemented their own small SharePoint 2013 implementation and a number of staff members in this company had seen its capabilities and wanted in, and wanted in yesterday.
Trying to be politically correct here as much as possible, a 15 day SharePoint Deployment Services engagement, for which EPC Group shies away from as we tend to not see the value in it for our Enterprise clients, was not going to resolve this Enterprise Content Management (ECM) initiative and there was several months of hard work ahead for not only the company but for which ever firm they selected to trust and engage with on this undertaking. To my surprise the CIO called me and said he had 5 quotes on his desk that ranged from $56,000 to $310,000. Let’s just say for conversation sake, the Statement of Work I developed was not on the cheaper side as myself and my team who worked on this proposal with me for several days understood the level of effort, had gone back into Project Server and pulled out 3 similar project plans to verify tasks, etc. and in no way was any firm in the world going to accomplish this initiative for $56,000 or anything near that number. It’s important the client understand what the SharePoint firm is delivering, what is the engagement model, what type of project management are they expecting, how much face to face knowledge transfer should they expect, etc… (As I could go on and on but i believe this is a point that many in the SharePoint arena to not like to address).
Note: Not a whole lot can be accomplished in a 15 day initiative, especially if you are looking for knowledge transfer, which I believe is the absolutely key to long-term SharePoint success.
The Clients Perspective
I don’t envy the client situation when going out to select a SharePoint Consulting partner to take on this task and there can be the route for which they do their own due diligence and come up with a list of 3 or 4 of the top firms in the US with 300 or 400+ or more of these projects under their belt or depending on the organization, put out an RFP and let the masses try and prove their prowess or expertise. Personally I don’t have huge preference when working with clients to win their business based on my firm EPC Group’s past performance and reputation and I am probably speaking for several other SharePoint firms out there but I would also caution clients to truly look into who they are receiving quotes from…
When selecting a SharePoint Consulting firm\partner, consider the proposal’s numbers (cost) vs. the quality and experience of the delivery team. With the 20 or so firms that have been founded in the past 24-36 months which I track (along with the other firms in the US), many of them are trying to underbid the project to win it to build a past performance or reference base, but in many cases firms who have been in the SharePoint consulting arena for 10 years end up getting a follow-up call from the client asking for a health check and assessment as well as a quote for a new initiative as they found out they need to throw-out the past few months of work and start over due to the disaster they have just experienced.
This is sometimes due to the SharePoint roadmap that was never developed, the experience level of the consultants, possibly the “1099 subcontracted for this job consultants” this original firm hired when signing up for a Dice.com account shortly after winning the project to hire a few “Senior SharePoint Consultants” that did not live up to the SharePoint Senior Architects \ Consultants for which they were “billed” at and pitched during the sales and project scoping process.
The Other “Big Vendors” in the Room
SharePoint is the most powerful and flexible enterprise solution who has taken on the past 800 pound giants and in its forth release (SharePoint 2010) as made EMC, OpenText, and others “call a bit of uncle, or there have been some board meetings in which the saying, “If you can’t beat em’, joint em’..” or “we have to open up our APIs to be SharePoint (seamlessly) friendly” just may have been uttered (my personal opinion of course).
Doing Due Diligence for Yourself and Your Firm When Selecting a Consulting Firm
It is critical that you look at not only certifications, experience, any beta testing or TAP program experience from those that were there at the pre-release, authoring of SharePoint publications, real-world experience, and those that talk about making mistakes and learning from them. Sometimes it important to not talk about SharePoint at all but listen to the business problem and ensure the consultants do not have blinders on and make it everything in the project just about SharePoint, SharePoint, SharePoint….
- What defines a Senior SharePoint Architect \ Consultant vs. a consultant who has been subcontracted to work on 1 or 2 deployments?
- Remember that just because a consulting firm may have the product vendor “or something similar” in their name, that doesn’t mean they necessarily know what they are doing or have the rock stars at the table to successfully complete your project (yes, even if they want to bid twice as much as the others who proposed a statement of work or hourly rate, etc.).
State of SharePoint
A large number SharePoint firms have been founded in the past 2-3 years (as I mentioned above) and at least 5 seasoned firm I know of have been purchased in the past 18-24 months by larger firms. I have been asked at conferences, “what about outsourcing SharePoint development and using a few information architects to control the face time”? Outsourcing SharePoint development overseas doesn’t not work on a large scale unless you have months and months to near ‘fingerprint in stone’ every single possible detail (business and functional requirement). If a change is needed, it will take several weeks to turn around, update, and receive it back to implement in your dev farm to test. You must ensure all your development environments are synchronized. Your developers must have experience in 2007 as well as 2010 to ensure you understand the issues in upgrading because SharePoint 15 is coming out sometime in 2014. (Note: we may get a sneak peak from the SharePoint product team in the very near future).
The External “Cloud” versus your own Internal “Private” Cloud
In my opinion, and with concerns of the recent outages of several of the large clouds, companies who must connect to external business data or have developed custom applications in house (web parts, workflows, master pages, using the BCS, etc.) are not going to jump on the bandwagon of an external cloud in the near future (especially with the negative press of day or two long outages) but rather implement and “Internal or Private Cloud” (no matter how many other expert bloggers may work for or own Cloud Computing organizations, again this is my opinion from sitting with prominent CIOs from the private and government sector). I believe there is value to the cloud for SMB type businesses but Fortune 500\1000 and major Government organizations need 24/7, 365 uptime and the ability to manage custom code, connect to external data sources, federate security seamlessly, and a whole lot more, and do it yesterday.
SharePoint Trainers vs. Consultants
Trainers who blog are not always experts in, “in the trenches” consulting and you may get a robotic or rehearsed answer; ensure the blogs and experts you follow are actual consultants who have sat in “war rooms” hours on end to whiteboard and solve real world problems where there are budgetary and political considerations as well as timelines, resources, and peoples jobs from the client on the line.
3rd Party Vendors \ ISVs
There are a large number of SharePoint 3rd party solutions (ISVs) who offer amazing solutions that can help you to lower your internal maintenance costs and almost act like another full-time employee (FTE) for your firm. On the other hand, ensure you are only buying what you need as some ISVs have moved to the model of bundling up their entire suite of products that not only cause a massive footprint on your servers but also cause you to possibly spend budget that you do not need to spend.
A Recent Area of Concern – Internal Politics and SharePoint 2010’s Massive Functionality
Internal politics can absolutely be the death of a project and the firm you select must be able to tell you the hard truth about this and you should take it in stride. I have witnessed the application (SharePoint) teams literally fighting tooth and nail with the development, legal, or legacy solutions (Portal, ECM, etc.) and vice versa. SharePoint Server 2010 has an unbelievable amount of functionality (i.e. ECM\ERM, Portal, Collaboration, Social\Professional Networking, Business Intelligence, etc.). It is bound to cause political issues and find some people concerned about job security with their legacy systems.
Microsoft is adding 20,000 new users a day or 7+ million new users a year (for the past 5 years) so resolving issues and understanding SharePoint’s capabilities to provide ROI to your firm is in your best interest.