|By Christian Buckley||
|January 21, 2013 03:15 PM EST||
For many companies, the business benefits that cloud computing promises are too compelling too ignore: improved agility, lower costs, better resource allocation, and fewer operational issues. As a result, organizations have been moving commodity infrastructure and services to cloud-based services managed by some of the world's leading technology companies - including Office 365, Microsoft's primary offering for business productivity in the cloud.
Several new developments are making Office 365 even more enticing:
- New release of SharePoint: Extranets and public-facing websites are expensive in SharePoint 2010. However, with pricing changes and new web content management (WCM) functionality for SharePoint 2013, many organizations are beginning to take a second look at the cloud for some work streams as Office 365 gets updated in early 2013 with the latest SharePoint version.
- Broad Office 365 adoption: According to Kurt DelBene, President of the Office Division at Microsoft, Office 365 is on target to become the fastest-selling server product in Microsoft's history, outpacing all analyst expectations.
- Additional cost savings: With Office 365, organizations pay a monthly fee per user and gain access to ongoing maintenance and expertise to manage servers. That saves them from a huge, upfront operating expense. (We should point out, however, that because SharePoint Online is more of a product and service than a platform, it has more limited capabilities than the on-premises version, so long-term cost implications are not yet known.)
Given these gains, no company should ignore a move to the cloud. However, a full jump to the public cloud without careful consideration is ill advised. Some companies can't move everything to the cloud because they have compliance, regulatory, or government restrictions that limit where data can be stored and who can have access to it. But many companies shouldn't move everything to the cloud, because there is simply not parity between online and on-premise versions of SharePoint. What makes SharePoint compelling for many enterprises is the ability to extend, customize, and integrate with other enterprise systems, much of which is impossible with the Office 365 platform. Until there is parity, certain workstreams should stay in their current environments.
What's needed now is a thoughtful, strategic approach to cloud computing that is based on the needs of your business. Understanding which aspects of your organization's business systems can be moved, and should be moved, to the cloud is an important discussion that leaders must undertake. Although some work streams can be moved easily, many others require customization and management that only an on-premise deployment can support. That's why a hybrid model - comprising on-premise, private, and/or public cloud components - offers organizations the best way to ease into the cloud computing paradigm and leverage the promise of SharePoint Online.
Where to start? As part of readiness planning for cloud services adoption, companies must address seven critical success factors:
1. What are the business requirements?
As a first step, organizations must get their arms around the underlying business requirements of the environment, the key use cases, and the key work streams. For example, it may be possible to build out a lightweight customer relationship management solution, acting as a portal for sales, marketing, and support to connect with customers. But it may not make sense to move development team activities to the cloud due to integration issues with case management or configuration management systems. Outline your key workstreams, and then begin to map each workstream to your on-premise and online models to see which activities can be improved upon.
2. What are the business implications?
Companies must understand the implications of moving each use case and each work stream into the cloud. You must know the answers to these key questions: Can current functionality, security, audits, and reporting be replicated in the cloud? If key functions cannot be offered and supported, what are the risks? Say you have a ticketing system, with SharePoint acting as the front end. Without a full understanding of the architecture of the solution and how data is shared between the ticketing platform and SharePoint it may be difficult to understand the true cost implications of moving to the cloud. You also need an understanding of the performance and cost impacts to the large number of web service calls the platform may make within a pure cloud environment. Depending on the volume of data moved, how it is moved, and the timeframe for moving this important business system to the cloud, it may make financial sense to maintain an on-premise version of SharePoint for your product and support organizations.
3. What are the management ramifications?
Companies must understand the management implications of each work stream. It's not just a matter of "can we move it?" but "should we move it?" In some instances, a move to the cloud may result in added administrative effort and costs. Case in point: In one of the most common hybrid scenarios, a business that uses Office 365 as its extranet while maintaining an on-premise or dedicated cloud SharePoint environment may find that managing permissions, storage, and usage/activity is an extremely manual and time-consuming process. That's because there are no native tools for managing these functions across disparate SharePoint environments. Therefore, it's critical to look at your current metrics and KPIs for managing SharePoint, and understand the implications of duplicating these metrics within a new cloud environment - as well as combining and normalizing this data across all systems.
4. What about the end user experience?
We can't state this strongly enough: Companies must understand what the end-user experience will look like. If a hybrid environment adds effort or decreases productivity for end users, what is the cost? Consider these factors: Access to your enterprise platforms probably begins with a single sign-on experience - you log in once to get to all the tools and systems you need to do your business tasks. Your organization may have made significant investments to brand your internal platforms and put processes in place to maintain consistency across team sites and business unit portals. But, if you add another external system to the mix, what happens to the end-user experience? If permissions are separate, how does that affect end-user productivity? Your imperative is to understand how your primary users will conduct their business, thinking about the end-to-end experience, not just whether key functionality is being met through the new system. Remember: the more difficult a system is to use, the less likely people will be to use it.
5. How will we move?
If part of your organization, and key work streams, are moved to the cloud, what is the plan for the move? Will you move all at once? In waves? What about training? Migration and onboarding strategies vary widely. Your strategy should be based on critical path business use cases, helping those who rely on the new system before the masses. One strategy is to follow the 80/20 rule: concentrate your planning around the 20% of the users who use SharePoint most heavily, giving them 80% of your time, while spending 20% of your time with the remaining (mostly casual) users. However you decide to time moving end users and work streams, you must involve end users as you formulate and communicate your plan. The more you involve people in the process, the more likely they are to support that process.
6. How will we measure success?
Companies must have the right metrics in place to track performance across the entire environment. Companies also need to think about whether or not content needs to be synchronized between environments, or if these use cases can be maintained separately. Most companies fail at this today - because they don't have sufficient visibility into their SharePoint environment to generate and track adequate metrics. Moving to a hybrid model is a great opportunity to correct this trend. One strategy is to begin by identifying three key metrics across both systems, and build from there. An example might be Top 10 Most Active Sites, Top 10 Most Active Users, and Most Active Content Databases. Based on this data, you will gain a much better understanding of who is actually using SharePoint and where, allowing you to better allocate your time and resources to support the sites and users who are most active on the platform.
7. How will we enforce governance?
Ask yourself: Do we have a defined change management process? Do we have our roles and accountabilities defined? Are we actively reviewing and taking action on new requests? Are we giving end users and admins visibility into the changes being made and the priorities of those requirements? Having a governance body in place is crucial. Without automation, manual governance practices (policies, documentation, metrics) need to be extended or duplicated, with appropriate roles defined and assigned. Best practices include running through the document lifecycle across environments and identifying where current policies break. Focus your attention on the governance policies that manage risk - compliance, regulations, retention, or any other legal requirements of a hybrid system. Then define what it will take to maintain minimum security levels, and create a plan for automating and simplifying.
Despite the risks, some companies may be drawn into the cloud by the perceived cost savings, despite their customization or integration needs. This is a recipe for failure. Companies that successfully make the move to a hybrid model are those that understand the business activities that can be offloaded to the cloud, benefiting from its scale and cost benefits.
The beauty of a strategic, hybrid model is that it's not "all or nothing." By addressing the seven critical success factors outlined above, companies will be taking a holistic approach versus making a blind technology decision. By focusing on specific workstreams, and only building out those workstreams that can be supported, your company will end up with a strategic, hybrid model that supports the needs of your business.
For more information:
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
May. 6, 2016 07:00 AM EDT Reads: 1,217
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
May. 6, 2016 07:00 AM EDT Reads: 259
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
May. 6, 2016 05:30 AM EDT Reads: 1,051
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
May. 6, 2016 04:15 AM EDT Reads: 2,091
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
May. 6, 2016 03:00 AM EDT Reads: 947
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
May. 6, 2016 02:45 AM EDT Reads: 545
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
May. 6, 2016 01:30 AM EDT Reads: 1,167
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
May. 6, 2016 12:30 AM EDT Reads: 781
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
May. 5, 2016 11:30 PM EDT Reads: 1,084
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
May. 5, 2016 07:45 PM EDT Reads: 1,647
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
May. 5, 2016 05:15 PM EDT Reads: 1,743
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
May. 5, 2016 05:00 PM EDT Reads: 620
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
May. 5, 2016 05:00 PM EDT Reads: 1,387
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
May. 5, 2016 02:30 PM EDT Reads: 1,496
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
May. 5, 2016 01:30 PM EDT Reads: 1,158
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
May. 5, 2016 03:15 AM EDT Reads: 1,521
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
May. 4, 2016 09:00 PM EDT Reads: 2,273
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
May. 3, 2016 07:30 PM EDT Reads: 1,964
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
May. 3, 2016 04:45 PM EDT Reads: 1,173
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
May. 3, 2016 12:15 PM EDT Reads: 1,667