<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for walmslan</title><link>http://disqus.com/by/walmslan/</link><description></description><atom:link href="http://disqus.com/walmslan/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 16 Jun 2015 01:09:25 -0000</lastBuildDate><item><title>Re: Building Up a Microsoft Intranet in a Box</title><link>http://www.cmswire.com/social-business/building-up-a-microsoft-intranet-in-a-box/#comment-2081353502</link><description>&lt;p&gt;Interesting read. Having been around long enough to have seen several 'intranet in a box' solutions launch from various solution integration partners, and all fail after 2-4 years, I concur with you're final paragraph sentiments.&lt;/p&gt;&lt;p&gt;The fast pace of underlying change in SharePoint or  Office365, make anything based on it a constant moving target of new features customers want you can't commercially driver quick enough or old features they will lose, not being managed properly by said partner, making it commercially difficult to maintain cost effectively.&lt;/p&gt;&lt;p&gt;I've always struggled to see the commercial value proposition in the 'wrap of the solution' in top of the existing underlying cost model (of Office365).&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Tue, 16 Jun 2015 01:09:25 -0000</pubDate></item><item><title>Re: Should Microsoft kill SharePoint? [Gartner]</title><link>https://memeburn.com/2013/09/should-microsoft-kill-sharepoint-gartner/#comment-1052073905</link><description>&lt;p&gt;It's a bit of a headline grabbing article to be blunt, with little substance and arguably some large portions of naivety on the analyst part.&lt;/p&gt;&lt;p&gt;One has to wonder if the analyst thinks of products like Oracle, SAP or other enterprise based platforms. Should these be killed off also?&lt;/p&gt;&lt;p&gt;It by design, does a lot of things for a lot of audiences, and I'd agree it's become a very large product over the last couple of major releases.&lt;/p&gt;&lt;p&gt;But like any large system, good planning, design and overall maintenance coupled with some common sense approaches to customisations will reap rewards.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Thu, 19 Sep 2013 16:56:40 -0000</pubDate></item><item><title>Re: Making the Most of SharePoint AND Yammer</title><link>http://www.cmswire.com/cms/social-business/making-the-most-of-sharepoint-and-yammer-022296.php#comment-1022934023</link><description>&lt;p&gt;Matt, unless I have misunderstood your last point, there are several options for bringing your Yammer content into your SP2010 environment.&lt;/p&gt;&lt;p&gt;I wrote a this up here earlier in the year:&lt;a href="http://www.workshares.co.uk/our-blog/yammer-and-sharepoint-integration-options/" rel="nofollow noopener" target="_blank" title="http://www.workshares.co.uk/our-blog/yammer-and-sharepoint-integration-options/"&gt;http://www.workshares.co.uk...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;The article itself shows to some extent the features that are for both SP2010 and SP2013 (it does get to be a more convoluted story with cloud version, as this is where the monies/focus is)&lt;/p&gt;&lt;p&gt;Unless you mean more than just exposing a rudimentary web part, I.e like the fuller integration offered by the newsgator product you refer too?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Fri, 30 Aug 2013 01:39:23 -0000</pubDate></item><item><title>Re: Will Office 365 Change SharePoint?</title><link>http://www.cmswire.com/cms/information-management/will-office-365-change-sharepoint-022105.php#comment-1007837297</link><description>&lt;p&gt;The decision to go for cloud based offerings, driven arguably by market forces, (read price!), opportunity, supported by advancements in IT to make it possible, have arguably been the reasons many of the SMB have been able to consider (and take up) a move to Office365 platform.&lt;/p&gt;&lt;p&gt;The traditional medium to large enterprise users of SharePoint haven't necessarily go 'all in' to the cloud either as Microsoft would like, but I think this is largely down to a typical reservations aligned with culture, risk, compliance, and in some cases technical constraints. It's happening, but just on a slower burn.&lt;/p&gt;&lt;p&gt;With that in mind, the experience and input from SMB's especially with other drivers such as bringing 'social' engagement capabilities (read, Yammer) will absolutely have an impact on the roadmap of these services. But i think the mix of on-premise, cloud and hybrid options will continue for some time yet as it looks to serve as many customers as possible. The question for me is how much profitability (or lack of?) will impact these offerings and how soon?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Tue, 20 Aug 2013 07:12:33 -0000</pubDate></item><item><title>Re: Top 10 reasons your SharePoint 2013 Migration FAILED</title><link>http://en.share-gate.com/blog/top-10-reasons-sharepoint-2013-migration-failed#comment-843126055</link><description>&lt;p&gt;A great write-up and interesting read. As a relative veteran of the industry and also of migrations, these tips resonate completely; A must read for anyone about to look into migrating from older versions of SharePoint.&lt;/p&gt;&lt;p&gt;I would also add I have found it useful to agree a 'success criteria' for migration that all interested parties know and agree as to what this means for them – it will have different criteria for different stakeholders. Thinks what ‘success’ looks like for IT, as it will be very different for those in communications or the end user communities and it will help ensure your migration to SharePoint 2013 isn’t a failure.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Tue, 26 Mar 2013 14:04:54 -0000</pubDate></item><item><title>Re: Reflecting on Yammer and Office 365: SharePoint is Definitely Dead</title><link>http://www.cmswire.com/cms/social-business/reflecting-on-yammer-and-office-365-sharepoint-is-definitely-dead-020150.php#comment-842954983</link><description>&lt;p&gt;I think I would have to agree with the sentiments made from majority of the others&lt;br&gt;that have commented so far; SharePoint isn’t dead, and is a fundamental core component along with email (Exchange) and IM (Lync) of the Office365 suite.&lt;/p&gt;&lt;p&gt;It will also continue to be sold separately within the Office365 suite for a long time yet and in my view be supported and updated in the on-premise arena for some time to come.&lt;/p&gt;&lt;p&gt;For the simple reason that the majority of organisations we have spoken too, have no plans to move to the cloud, for variety of reasons (legislative, security and culture…) well documented not just for Microsoft products but for others in general in the same space. Hence the standalone SharePoint platform and name will continue, all be it perhaps not on par with its cloud based offerings in terms of features.&lt;/p&gt;&lt;p&gt;This article whilst ‘headline grabbing’ is thought provoking but isn’t really supported with any substantial evidence to support it's intent, but nice try anyway! ;-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Tue, 26 Mar 2013 10:55:09 -0000</pubDate></item><item><title>Re: Why Your Traditional Intranet Is Killing Your Company</title><link>http://www.cmswire.com/cms/social-business/why-your-traditional-intranet-is-killing-your-company-020021.php#comment-828944080</link><description>&lt;p&gt;Great article, as its advice that’s arguably independent of&lt;br&gt;any specific technology and more a way of doing things better.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Thu, 14 Mar 2013 05:20:07 -0000</pubDate></item><item><title>Re: Office 365: Top 10 Upgrades to SharePoint, Exchange, Lync for Business Productivity</title><link>http://www.cmswire.com/cms/information-management/office-365-top-10-upgrades-to-sharepoint-exchange-lync-for-business-productivity-019845.php#comment-818965984</link><description>&lt;p&gt;Hi,&lt;/p&gt;&lt;p&gt;I am surprised you didn't mention the FAST server technologies being built into all of these offerings now by default and powers many wider features of the overall platform.  This was a standalone product previously, and quite an expensive option too, so it's great to see this built into the product by default.&lt;/p&gt;&lt;p&gt;Search is a critical aspect of finding information across all of these platform, not least SharePoint 2013, which has seen big improvement in this space (especially for those who are just used to 'normal' SharePoint search).&lt;/p&gt;&lt;p&gt;Regards&lt;br&gt;Andrew&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Mon, 04 Mar 2013 11:34:19 -0000</pubDate></item><item><title>Re: Successful SharePoint Projects, Myth or Reality?</title><link>http://sharepointmagazine.net/?p=1735#comment-4586653</link><description>&lt;p&gt;CCarter, they vary so differently depending on the needs of the project.&lt;/p&gt;&lt;p&gt;You don't say what type of SharePoint project (The 'sharepoint site development' name unfortunately means very little) it is in terms of scope, (Intrant, extranet or internet), which products you're using - WSS, MOSS, etc.&lt;/p&gt;&lt;p&gt;Hence difficult to respond with specifics as such. Based on what you have said however, use the enterprise one as a starter and strip out the irrelevant stuff that sounds completely out of scope for what you are doing - It's often easier to take out, than put back in so to speak.&lt;/p&gt;&lt;p&gt;Ensure there is a 'design stage/sign off' process, infrastructure ratification step, release cycle(s) planned in, launch/adoption activities.&lt;/p&gt;&lt;p&gt;Some basic PM stuff, make sure you have a scoping document (Project Initiation Document (PID) - this needs to be signed off/monitored regularly, Issues/Actions list reviewed weekly and actioned accordingly.&lt;/p&gt;&lt;p&gt;Finally review your team structure - suggest given your supposed lack of experience, avoid any branding changes, stick with features 'out of the box' for the first couple of phases, bring in bespoke stuff later once you have understood the wide features, constraints and therefore opportunities to add value later!&lt;/p&gt;&lt;p&gt;Hope that brain dump helps...&lt;br&gt;Andy&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Tue, 23 Dec 2008 04:42:03 -0000</pubDate></item><item><title>Re: Successful SharePoint Projects, Myth or Reality?</title><link>http://sharepointmagazine.net/?p=1735#comment-4410221</link><description>&lt;p&gt;Thanks sharepoint_consulting for your comments. Small steps are important, but many businesses don't necessarily have the patience to take this approach!&lt;/p&gt;&lt;p&gt;As for treating SharePoint like 'any other technology project', agreed but at a more granular level they do present different challenges to say a traditional IT development project or email migration project.&lt;/p&gt;&lt;p&gt;In my view they have similarities &amp;amp; approaches that need to be merged as SharePoint can and will cut across such traditional project delivery methods.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Mon, 15 Dec 2008 10:06:13 -0000</pubDate></item><item><title>Re: Successful SharePoint Projects, Myth or Reality?</title><link>http://sharepointmagazine.net/?p=1735#comment-4410170</link><description>&lt;p&gt;Thanks JThake for your feedback. I have found all to often the lines between customisation/configuration/development is blurred and this I think will continue as organisations begin to push the boundaries of how SharePoint can  be leveraged to improve upon current inefficiencies, together with a general lack of good SharePoint resources out there at the moment.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Mon, 15 Dec 2008 10:01:05 -0000</pubDate></item><item><title>Re: Successful SharePoint Projects, Myth or Reality?</title><link>http://sharepointmagazine.net/?p=1735#comment-4410137</link><description>&lt;p&gt;Thanks PCulmsee. It's also worth bearing in mind that the 'cultural mix' of an organisation staff will have a bearing here on user adoption.&lt;/p&gt;&lt;p&gt;For example, traditionally public sector organisations will typically put more effort/budget into training. This is because the transition is often more 'challenging' as employees are often more resistant to change than say private sector businesses in my experience.&lt;/p&gt;&lt;p&gt;All the best,&lt;br&gt;Andrew.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Walmsley</dc:creator><pubDate>Mon, 15 Dec 2008 09:57:40 -0000</pubDate></item></channel></rss>