Technology innovation and business disruption are changing the software market today. Cloud computing is blurring the line between applications and services, and smart solutions are combining hardware with software into new, purpose-engineered solutions. We are happy to announce that we have launched our Forrester Forrsights Software Survey, Q4 2010, to predict and quantify the future of the software market and help IT vendors to tap into the insights from approximately 2,500 IT decision-makers across North America and Western Europe.
The survey will provide insights on the strategic direction and spending plans of enterprises from very small businesses to global enterprises, segmented by industry and country. In comparison with last year’s survey, we significantly boosted the sample size this year for the energy (oil and gas, utilities, and mining) and healthcare industries; we’ll be able to provide an in-depth analysis for these industries along with retail, financial services, high tech, and other industries.
Key themes for this year’s software survey include the following topics:
Cloud computing. Besides a 360-degree overview on current and future adoption rates of software-as-a-service (SaaS) for different software applications, we are going much deeper this year and have asked IT decision-makers about their cloud strategy for application replacement as well as for different data and transaction types.
Integrated information technology. Purpose-engineered solutions combining hardware with software are promising higher performance and faster implementation times. But do IT users really buy into single-vendor strategies?
As someone who has worked in development teams, I take it for granted that not everyone on the team has the same needs and interests. A twenty-something Java developer, fresh out of college, is interested in questions like, "Which emerging framework might be worth learning?" The architect on the team may be interested in the same frameworks, but for entirely different reasons. Unlike the rank-and-file developer, the architect has decision-making power over which framework to adopt. The architect bears responsibility for the long-term consequences of this decision, while the rank-and-file developer is primarily concerned about delivering components written for whatever framework the team selects. Meanwhile, the development manager has to oversee the work of both the developer and architect, ensuring that, collectively, the developers and architects and testers and everyone else deliver their work product on time, at an acceptable level of quality.
Different roles, different questions -- not a hard principle to understand. When applied to developer support, it means that developer conferences, discussion forums, and other resources must tailor their content to a specific audience. Not surprisingly, the material interesting to developers might not be as interesting for architects, and vice-versa. (And if you're still not convinced that the two roles have different needs, take a look at the chart in this earlier blog post, which shows the sources of information and advice to which developers and architects turn.)