To compete in today's global economy, businesses and governments need agility and the ability to adapt quickly to change. And what about internal adoption to roll out enterprise-grade Business Intelligence (BI) applications? BI change is ongoing; often, many things change concurrently. One element that too often takes a back seat is the impact of changes on the organization's people. Prosci, an independent research company focused on organizational change management (OCM), has developed benchmarks that propose five areas in which change management needs to do better. They all involve the people side of change: better engage the sponsor; begin organizational change management early in the change process; get employees engaged in change activities; secure sufficient personnel resources; and better communicate with employees. Because BI is not a single application — and often not even a single platform — we recommend adding a sixth area: visibility into BI usage and performance management of BI itself, aka BI on BI. Forrester recommends keeping these six areas top of mind as your organization prepares for any kind of change.
Some strategic business events, like mergers, are high-risk initiatives involving major changes over two or more years; others, such as restructuring, must be implemented in six months. In the case of BI, some changes might need to happen within a few weeks or even days. All changes will lead to either achieving or failing to achieve a business. There are seven major categories of business and organizational change:
The Webster Dictionary describes fatigue (also sometimes called exhaustion, tiredness, languor, lassitude or listlessness) as "a subjective feeling of tiredness which is distinct from weakness, and has a gradual onset."
Technology management transformations - and in specific, I&O transformations - suffer from fatigue in many organizations. Some of it is due to the fact that the term "transformation" is more jargon than anything real. Transformation means many things to many people and therfore we never really exit a transformation as we move from project to project, continually transforming.
If I asked you, does I&O transformation mean reshaping your architecture? Streamlining your service management and integration (SIAM) processes? Adjusting your automation strategy? Improving your application performance management to become more proactive? Reducing operational cost? Shifting your infrastructure and applications into the cloud? You would say "yes" to all of them, with all of them being described as some kind of transformation. Eliminating fatigue means following a transformation plan. The plan needs to be supported with details to shift the conversation from costs of the technology “feeds and speeds” to how the technology will enable the business to win, serve, and retain their customers.
Determining which public cloud platforms your company should standardize on is not a matter of marketshare, size or growth rate. What matters most is fit for purpose - yours. And that’s exactly what our latest Forrester Wave of this market helps you determine.
And the key questions to ask have nothing to do with the vendors in question. They are all about you - your team’s skill sets, needs and requirements. Will you mostly be building lightweight web and mobile applications from common web services you’d rather not recreate yourself? What skills do your developers bring to the problem - deep knowledge of Java and C# but light on the infrastructure configuration and middleware management front? Need to ensure data residency in specific geographies? Compliancy top your concerns list? These factors are far more important than feature by feature comparisons. Ultimately your platform selection needs to match your business requirements, and if our surveys can be trusted, you desire agility and developer productivity over most other concerns.
Where Amazon Web Services may best suit your DevOps teams with strong desire to control everything themselves, your web properties team may be far more productive on Mendix or Outsystems.
The Information Governance report is out! Over the last few months I've test-driven my thoughts and data with many vendors and enterprise customers via conference presentations, webinars, and one-on-one discussions. For those who have shared their thoughts with me - thank you! Forrester subscribers can access it here.
Information Governance is red hot right now, and it was time for Forrester contribute a view on how IG helps companies meet their core corporate missions. Of course, better, consistent fulfillment of compliance obligations is essential, but so are objectives such as customer service, revenue growth, and improved agility in oh-so competitive markets. IG is not just about getting rid of junk content, it is - more importantly - about instilling trust in the data and communication we use to run our businesses.
Software is not a silver bullet for information governance. Look beyond vendor hype - IG is not something to go buy so you can say your company has it. Look at IG as an evergreen corporate objective, enabled by programs, policies, people- and yes, a range of technologies.
I'm going to add to the IG definition war this week, by describing information governance as:
Automation drove weavers from their looms in the industrial revolution. The Internet’s and tools facilitated the movement of manufacturing process for most software from the high priced markets in the US to India. So too the digitalization of health records combined with the insight that data yields and embed into work flow engines of care delivery will radically change the healthcare ecosystem.
Since I joined Forrester research, in the fall of 2013, my perceptions of what drives change has changed. I thought that the socio-political forces were driving software to change healthcare. Now I think software is driving changes to the socio-economic fabric. While we pundits are busy noticing:
EMRs being implemented.
Master patient indexes are rolling out.
Capabilities shifting to mobile.
Insurance companies rolling out tools to better track and communicating with consumers.
Startups forging new methods and business models to engage patients.
Large consumer companies making moves to gain access to our healthcare data by offering us free tracking tools.
Telehealth encounters becoming increasingly important to the administration of care.
Big data and cognitive computing changing our understanding of epidemiology and personalized care decisions.
Facebook loves to play and test new things. After a couple of months of rumors, this morning they announced that they're going to play in the enterprise for a while and see if it's fun. And for the first time we have an inkling of what "Facebook at Work" will mean.
First off, we don't know what we don't know because they don't know what they don't know. And they know it. This is truly some early testing. Things like pricing are still down the road to be figured out. They have announced a small number of pilot organizations that have signed on. These organizations will have access to a Facebook instance that will be accessible only to authenticated users. So, essentially that much loved Facebook experience (including mobile) will be available to just the users in your organization or others that have been approved for authenticated access. Facebook hopes that workers will demand the service they love in their personal lives to collaborate, communicate and socialize in the workplace. So, that's where the play begins: testing if we want that user experience we know and love as part of our workday.
Google made the consumer-to-business transition with their email, productivity and file collaboration offerings. Dropbox is making the transition with their file sync and share solution. So, why not Facebook? And like Google and Dropbox, I don't think the challenge will be drumming up demand from workers. The challenge is really below the surface and lives in the requirements that business technology professionals will ultimately present. They will immediately begin to throw out challenges like directory integration, encryption, a host of other security requirements, external application integration and on and on. And all of this stuff is really hard to build.
Roughly a year and a half ago I began a process of measuring the importantance of technologies in the mobile security space. I'm currently beginning that same process for the application security market. Many technologies exist that provide business value to enterprises for the security of their applications, but which ones are better at delivering on the business value that the enterprise really wants? Have any of these technologies outlived their usefullness, falling to innovation and new ideas? Which technologies should the enterprise prioritize spending their limited security budget on? I hope to answer these questions and more!
I've identified nine distinct application security technologies that make up the application security market. (Link to additional details!). I'm sure there are technologies that I've missed and arguments to be made to remove something. As always, my research is significantly improved with your help!
If you are interested in participating in this research or have feedback on the technology list, respond via this web form, in the comments below, or via email / tweet to email@example.com (@txs).
A Continuous Delivery pipeline is a (mostly) automated software tool chain that takes delivered code, builds it, tests it, and deploys it. This simple concept gets complicated by tool chain realities: no one vendor does everything that needs to be done in the pipeline, and new solutions are evolving every day.
To make sense of the CD pipeline tool chain, I have taken a close look at the market and have identified a set of tool categories. I'm sure I've missed something, and you may not agree with my categories, and in either case I would like to hear from you! You can either comment on this blog, reach me on twitter (@ksbittner), or email me (firstname.lastname@example.org). If you think the categories sound right, I'd like to hear that, too. This is your chance to help define the continuous delivery tools market.
Continuous Delivery Tools & Technologies
Continuous Delivery is a process by which source code is built, deployed to testing environments, test, and optionally deployed to production environment using a highly automated pipeline. Many different kinds of tools need to be brought together to automate this process. The tool categories described below provide the building blocks of the automated Continuous Delivery process.
We have just published Forrester's semi-annual global tech market outlook report for 2015 and 2016 (see "The Global Tech Market Outlook For 2015 To 2016 -- Five Themes That Will Define The Tech Market"). In this report, we are projecting growth of 4.1% in 2015 and 6.3% in 2016 business and government purchases of computer and communications equipment, software, and tech consulting and outsourcing services measured in US dollars. These growth rates are distinct improvements over the 2.3% growth in 2014. The strong dollar is a key negative factor in these forecasts; measured in local currency terms, the growth track for the global tech market is higher with a gentler upward slope, from 3.3% in 2014 to 5.3% in 2015 and 5.9% in 2016.
Our global tech market outlook can be defined with five main themes:
Moderate 5% to 6% rates in 2015 and 2016 in local currency terms. While a stronger-than-expected US dollar has resulted in lower dollar-denominated growth rates for 2014 and 2015 than in our August 2014 projections, though a stronger-than-expected US dollar both years caused a downward revision in these growth rates.
The US tech market will set the pace for the rest of the world in 2015 and 2016. Not only does the US have the largest country-level tech market by far, it will have one of the fastest growth rates at 6.3% in 2015 and 6.1% in 2016. US businesses and governments are also leaders in adopting new mobile, cloud, and analytics technologies. Among other large tech markets, China, India, Sweden, and Israel will also have strong tech market growth, while Brazil, Mexico, Japan, and especially Russia will lag.