Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Pat Romanski, Elizabeth White, Lori MacVittie, Liz McMillan, XebiaLabs Blog

Related Topics: @MicroservicesE Blog, Java IoT

@MicroservicesE Blog: Article

Business Technology Centers of Excellence - Investing in Your Future

Ensuring the business value of your technology

Now is the time to invest.  As organizations enter the planning stages for their key 2012 initiatives, it is time to invest in the ingenuity that enables companies to continuously strive for the ever-elusive competitive edge.  It is time to invest in innovative processes and insight that creates lasting business value for customers and shareholders.  It is time to invest in the advanced technology that provides the foundation and tools for the people and processes to meet their true potential.  This means investing in the organizational construct known as a business technology Center of Excellence (CoE).

The general concept of a business technology CoE has occasionally been incorporated into everything from a skunkworks-oriented IT research & development team to a full-fledged enterprise architecture organization.  Corporate enterprise IT R&D teams are typically assigned a mission to constantly assess trends in business technology and make recommendations regarding their usage.  These teams can serve a vital purpose in some companies, but are often challenged in making the connection between the new technologies and their immediate benefit to the business’ bottom line.  Similarly,  enterprise architecture teams have been very successful in documenting and establishing governance over the existing business, organizational, and technical constructs of a corporation, but have been challenged in delivering ongoing, proactive, and immediate strategic value to the business.  A well-defined CoE with a specific mission addresses both the tactical and strategic issues associated with implementing new business technology solutions while remaining focused on the value the technology provides to the business.

Begin by considering how the CoE will be staffed.  The core team should consist of experienced professionals who have an understanding of many technology domains as well as a solid grasp of the business.  As with any high profile transformational initiative, it should be staffed by high performers with a proven track record of success.  This initial team will morph into the internal consultants in the organization who will be charged with driving change, so they need to have credibility and influence with both the business and IT departments.  From a practical standpoint, the enterprise architecture team is likely to have the most qualified candidates.  Suggestions for staffing additional roles and responsibilities beyond the CoE leadership will be discussed later.

The graphic below demonstrates both an organizational construct as well as the functional considerations that need to be addressed when introducing new business technology into the enterprise.  As with any enterprise initiative, it all begins with an examination of the business priorities.  This enables the team to understand where the greatest opportunities lie for technology to play a transformative role.  This understanding will then drive the situations, scenarios, and business problems to which the new technology can be applied.  For example, a business initiative focused on expansion into emerging markets with minimal technical expertise can drive the need for rapid provisioning of IT solutions and/or private cloud solutions.  Depending on the technology in question, these two CoE elements can actually drive each other.  For example, an understanding of business analytics technology and the role it can play in transforming organizational decision making can become the foundation that drives ideas for new business initiatives.  It may be considered blasphemous in some organizations, but there is nothing wrong with an emerging technology solution looking for a critical business problem to solve.  The business initiative and technology domain  decisions will in effect become the organizational charter for the CoE and therefore define its mission.

Once the mission is established, there are four areas of consideration that the CoE must address in order for a solution to become enterprise class.  From a timing perspective, some areas must be addressed prior to others, but all must be taken into consideration from the beginning.  Although there is minimal overlap in terms of purpose of any of these, they are complementary and are all required in order to deliver an enterprise class business solution.  The first area is Architecture.  As the saying goes, Architecture establishes the proverbial “rules of the road” that guide decision making and link the actual technical solution back to the business priorities.  Architecture includes the organizational thought leadership and evangelism that will drive adoption of the technology across the enterprise.  Techniques will include proofs of concept and prototypes that address specific business problems, the selection of the technology best suited for the organization, and a detailed understanding of the business value derived from the investment in the technology.  This function should be executed by the CoE leadership described earlier.  A combination of business leaders and architects set the overall direction of the CoE and lead execution.

The second area of consideration is Solution Development.  Even if the bulk of the solution is acquired from vendors rather than built in house, attention has to be paid to ensure that the implementation of the business functionality is done in a consistent and repeatable fashion.  These areas would typically be addressed by the development leads responsible for understanding the deep technical details of the technology, the optimal methods and nuances involved in deploying and reusing its components, and ensuring that the solution is well tested and exercised before it is used by the organization.  If, for example, the CoE is focused on the business process management (BPM) technology domain, these individuals would understand how to use the BPM tooling to map business processes, pass the appropriate business information between systems and humans, and all of the application integration details (service definitions, etc.).

The third area of consideration focuses on the Infrastructure components.  This includes   everything that ensures the establishment of an enterprise class environment upon which the solution can be hosted.  It includes defining and deploying installation and configuration procedures for the hardware and software to provide a highly available, scalable, recoverable, and secure environment.  These responsibilities would be executed by individuals such as systems administrators or engineers who understand capacity planning and all aspects of infrastructure management.  They would ensure that the solution adheres to established enterprise IT standards and reuses existing corporate hardware (servers, network, storage, etc.) and middleware (databases, application servers, etc.) to the greatest extent possible.

The fourth and final area of consideration focuses on post implementation Solution Support.  As critical as the solution is to the achievement of business priorities, systems and personnel need to be in place to ensure that it is functioning optimally.  This includes the ability to monitor the solution from a performance, availability, and functionality perspective as well as ensuring the proactive escalation and resolution of any issues.  Depending on the organization, this function may be performed by the same professionals responsible for the Infrastructure area of concern mentioned previously.  Similarly, any monitoring, service request management, and escalation systems already in place for the existing enterprise IT environment would be utilized for the new technology as well.

Although the graphic does not represent it, there is a cycle involved in each of these areas of consideration.  As the team and the solution evolves, new experiences are introduced that can iteratively drive more business value and efficiency.  However, once the CoE has achieved its initial mission and the solution has been rolled out, the teams focused on Architecture and Solution Development would remain in place and continue to act as internal consultants and evangelists to spread the technology and its business benefits across the enterprise.  The professionals focused on Infrastructure and Solution Support will have successfully integrated the new technology into the enterprise and would take on less of a role in driving further adoption.

As has been proven time and time again, technology itself cannot transform a business nor take it to the next level of success.  As Jim Collins articulates in his perennial best seller, “Good To Great”, however, technology can become the "accelerator" that enables the transformation.  Establishing a Center of Excellence that enables dedicated professionals to focus on applying a specific technology domain to a business problem will better enable the organization to reap greater benefits from its investment in the technology.

More Stories By Douglas Allen

Douglas W. Allen is a husband and father from Des Moines, IA and the owner of the winningtechnicalsales.com blog, dedicated to the sales engineering profession. As a technical sales manager at IBM, his team is dedicated to helping customers design and deploy enterprise-class business technology solutions that enable those customers to make money, save money, or mitigate risk. He is currently on a campaign to convince the world that the past, present, and future of rock and roll recently came out of New Jersey in the form of The Gaslight Anthem. He can be reached at www.linkedin.com/in/douglaswallen.

@MicroservicesExpo Stories
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
SYS-CON Events announced today that JFrog, maker of Artifactory, the popular Binary Repository Manager, will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based in California, Israel and France, founded by longtime field-experts, JFrog, creator of Artifactory and Bintray, has provided the market with the first Binary Repository solution and a software distribution social platform.
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...