Forrester Blogs For Business Technology Professionals
This is a roll-up of all Forrester blogs written for Business Technology Professionals. Role-specific blogs are listed below. Visit Forrester.com to learn how we make Business Technology Professionals successful every day.
I get many questions about the usage, pervasiveness, and adaption of mobile BI applications. What's a mobile BI application? Beyond a simple delivery of alerts, URLs, or actual reports via email - functionality that has existed for years - here are a few newer approaches to deliver BI on a mobile device:
The no brainer. In theory any mobile device equipped with a browser can access web based, thin client, HTML only BI applications. Yes, these BI apps will be mostly static, not interactive reports and dashboards. Navigation (scrolling, zooming, etc) will be quite awkward. But, this approach indeed requires no additional effort to deploy.
Customization. The next step up is to render each (or all) reports and dashboards to a format suitable to any mobile device in terms of screen size, usage of screen real estate, and mobile device specific navigation instrumentation. A variation of this approach is to create device specific navigation controls (thumb wheel or thumb button for Blackberries, up/down/left/right arrows for Palms, gestural manipulation for iPhone, etc). This obviously requires more development effort, but still no additional software.
Certain events serve as wake-up calls. In the case of some, the anticipation of these events is enough to spark action or change behavior – maybe even spur technology investment. As technology marketers, we need to recognize the opportunity that these events provide. Obviously, we also need to be ready to exploit them.
Which events could be catalyzing events from a technology purchasing decision? It could be as simple as the approach of a new millennium: Y2K fears spurred major investment. New regulation is an easy one to identify: IT buyers scrambled to upgrade security and implement data archiving and discovery software after the passage of the EU Data Protection Act and subsequent country-level legislation, as was also the case following passage of HIPAA, SOX, Basel II and others. The events of 9/11 certainly spurred concerns about cyber and other types of security. More recently, following last week’s blackouts in Brazil, leaders issued new commitments to energy reform. Natural disaster, crime waves and other negative events also catalyze technology investments.
Recent research undertaken by Forrester across Asia Pacific has indicated that while there is clearly a strong drive to improve the efficiency of IT systems, this will not often be through the implementation of process improvement systems, such as ITIL or CMM.
Major IT Management Themes In Asia Pacific
Source: Enterprise Global Technology Adoption Survey, Asia Pacific, Latin America, Middle East, And Africa, Q1 2009
So why has interest in these processes suddenly plummeted in Asia Pacific? While I have no strong evidence of the answer to the question, the many discussions I have had with IT leaders across the region leads me to believe that a number of factors have lead organizations to delay or put a stop to their ITIL process improvements and their broader ITSM initiatives.
Recently, Forrester surveyed a number of CIOs to collect benchmark data on staffing ratios and spending. This is a new initiative within Forrester and one that is not yet complete. We did this for three reasons:
Benchmark questions (called inquiries at Forrester) on staffing have become relatively common. Examples are “Can you tell us the average share of IT Staff as a % of total staff by organization size” and “Would you have specific spending figures for IT infrastructure?”.
This kind of data in conjunction with other data and analysis can identify problem areas.
Staffing benchmark data along with spending and other data are objective measures of IT organizations.
Though our initial sample size is small a preliminary view of the data shows that:
In its complaint, the SEC alleges that, “Madoff and his lieutenant Frank DiPascali, Jr., routinely asked (Jerome) O'Hara and (George) Perez for their help in creating records that, among other things, combined actual positions and activity from... market-making and proprietary trading businesses with the fictional balances maintained in investor accounts.”
The SEC further alleges that O’Hara and Perez tried to cover their tracks by deleting hundreds of files, withdrew hundreds of thousands of dollars from their investments through the company, told Madoff they wanted to stop helping him, and then accepted larger salaries and substantial bonuses for their promise to keep quiet.
It will be interesting to watch this case unfold. I was hoping it would get into issues of whether the IT professionals were considered just uninvolved support staff or key participants in the scheme. Considering the evidence SEC claims to have, I don’t think we’ll hear those arguments in this case, but keep an eye out for how the defense comes together. Fraud prevention is a growing area of concern for government, health care, insurance, financial services, and other industries... which means we could be seeing more cases questioning the responsibility of IT to identify and/or prevent such issues.
Our latest featured podcast is Bill Band's "The Top 19 Customer Management Technologies To Watch".
In this podcast, BP&A Vice President and Principal Analyst Bill Band describes what technologies comprise the customer management applications ecosystem, and which ones offer the most value based on Forrester’s most recent research.
We look forward to your questions and comments.
Subscribe to Business Process & Applications podcasts through iTunes.
Each year for the past three years I've analyzed and written on the state of enterprise disaster recovery preparedness. I've seen a definite improvement in overall DR preparedness during these past three years. Most enterprises do have some kind of recovery data center, enterprises often use an internal or colocated recovery data center to support advanced DR solutions such as replication and more "active-active" data center configurations and finally, the distance between data centers is increasing. As much as things have improved, there is still a lot more room for improvement not just in advanced technology adoption but also in DR process management. I typically find that very few enterprises are both technically sophisticated and good at managing DR as an on-going process.
When it comes to DR planning and process management, there are a number of standards including the British Standard for IT Service Continuity Management (BS 25777), other country standards and even industry specific standards. British Standards have a history of evolving into ISO standards and there has already been widespread acceptance of BS 25777 as well as BS 25999 (the business continuity version). No matter which standard you follow, I don’t think you can go drastically wrong. DR planning best practices have been well defined for years and there is a lot of commonality in these standards. They will all recommend:
I'd like to drill into some more details on my BI SaaS blog from September 2009. A key critical point to "what differentiates one BI SaaS vendor from another" discussion is what really constitutes multi-tenant architecture. Here are some initiall thoughts to stimulate the discussion:
DBMS. There's got to be back end, DBMS architecture that allows for one of the following:
Automatically generate a separate DBMS instance for each client
Use same DBMS instance for multiple clients, but automatically generate a set of unique tables for each client
Use same DBMS instance and tables for multiple clients, but automatically assign unique keys to to each client so that they can only update and retrieve their own rows
Application. Similar functionality has to exist in the application tier:
Automatically connect to the appropriate, client specific DBMS instance, or
Automatically use views that only point to client specific tables, or
Append "where" clause to each SQL statement to only retrieve client specific rows