My colleague Margo Visitacion and I are finishing up a new report, Seven Pragmatic Practices To Improve Software Quality, that will publish in a few weeks. We realized that not everyone has the same definition of quality. More often than not application development professionals define software quality as just meaning fewer bugs. But software quality means a whole lot more than just fewer bugs.
Forrester defines software quality as:
Software that meets business requirements, provides a satisfying user experience, and has fewer defects.
What It Means: Quality Is A Team Sport
Quality must move beyond the purview of just QA professionals and must become an integrated part of the entire software development life cycle (SDLC) to reduce schedule-killing rework when business requirements are misunderstood, improve user satisfaction, and reduce the risks of untested nonfunctional requirements such as security and performance.
We are getting many requests for help on iPad strategies for the enterprise. It's clear why. iPads are a tremendously empowering technology that any employee can buy. My colleague Andy Jaquith has a report coming real soon now on the security aspects of iPhones and iPads, and I'm launching research on case studies of iPad in the enterprise.
I am currently hearing about three business scenarios for iPad and tablets, but I'd love hear of your experiences, plans, concerns, or frustrations. Ping me at tschadler(at)forrester(dot)com. Here are the three scenarios:
Sales people out in the field. This is the "Hollywood pitch deck" scenario. The iPad, particularly with a cover that can prop it up a bit, is a great way to scroll through slides to show a customer or demonstrate a Web site. In one situation, I heard that there's a competition brewing for who can manipulate the Web site upside down (so the client across the table sees it right side up) without making any mistakes. Now there's a new skill for sales: upside down Web browsing.
Executives on an overnight trip. No, iPad doesn't replace a laptop (at least not yet; more on this below). But it's great for email, calendar, reviewing documents, and presenting PDF or Keynote decks.
During CScape at Cisco Live, one of the more interesting conversations I had started with a simple question: Is social software (and collaboration software in general) a set of standalone applications or features of other business applications? This sprang from a discussion on the future of the collaboration technology business and really speaks to a couple of important developments in the market:
There has been a lot of negative press and commentary regarding the recent Queensland Health Implementation of Continuity Project (SAP HR and Payroll), which recently experienced a very public failure as many employees were not paid due to multiple points of failure in the project. The recent Auditor-General's Report on the process is damning, spreading the blame across multiple agencies and the systems integration partner, IBM. I make no claims to be familiar with the intricate details of the process, but I have read the report and feel I have a clear understanding of the (many!) points of failure.
While this project did seem to be a monumental failure, I would suggest that we consider two important facts:
VMware today released an incremental upgrade to its core vSphere platform and took the opportunity to do some product repackaging and pricing actions - the latter being a big win for enterprise customers. The vSphere 4.1 enhancements focused on scalability to accommodate larger and larger virtual pools. The number of VMs per pool and number of hosts and VMs per instance of vCenter have been ratcheted up significantly, which will simplify large environments. The new network and storage I/O features and new memory compression and VMotion improvements will help customers pushing the upper limits of resource utilization. Storage vendors will laud the changes to vStorage too, which finally ends the conflict between what storage functions VMware performs versus what arrays do natively.
The company also telegraphed the end of life for ESX in favor of the more modern ESXi hypervisor architecture.
But for the majority of VMware shops the pricing changes are perhaps the most significant. It's been a longstanding pain that in order to use some of the key value add management features such as Site Recovery Manager and AppSpeed you had to license them across the full host even if you only wanted to apply that feature to a few VMs. This led to some unnatural behavior such as grouping business critical applications on the same host - cost optimization that trumps availability best practices. Thankfully that has now been corrected.
As I cruised the pavilion at Cisco Live in Las Vegas last week, the display that held my attention the longest was the Collaboration ROI booth. There, the network infrastructure provider making waves in the collaboration software market was demonstrating calculations it had done on how its various solutions were improving efficiency and productivity for specific jobs in verticals like retail banking. In the example I reviewed, banks using virtual loan officers were able to obtain more small business customers because the bank was able to have someone "there" to answer the prospective customer's questions. Now, with all the activity going on around me, why was this so fascinating? Put simply, it relates to a fundamental issue for all vendors hoping to compete in the collaboration software space: How do you differentiate in this crowded market?
Today we found out our great friend and colleague Andrew Parker passed away. It’s difficult to relay such personal news in a public forum, but so many of you know him and worked with him, that we felt it was important to share this news with you.
Many CIOs, sourcing professionals, vendor strategists and analyst relations executives have told me over the years that Andrew was the key IT services and sourcing analyst to know in EMEA. They valued him because they found in Andrew someone who could challenge their existing ideas and engage them in creating new ideas.
Andrew was a wonderful analyst – always willing to aim for the stars with a controversial or ambitious idea. And he knew how to support those ideas with great insights, deep knowledge of clients’ situations, and a broad perspective on the world. Andrew won many internal Forrester awards for his reports and was justifiably proud of his analysis. He had a genuine love for analyst work and was always excited about his research. Below are some of his personal favorites:
A number of Forrester analysts have been collaborating on a series of Tweet Jams on topics related to data management. The last session was on BI, and the next one up is on MDM. These are very lively sessions involving many points of view on some quite provocative topics. I'm pasting in text from analyst Rob Karel's blog post on the upcoming MDM session on July 20 in case architects who read our EA blog don't read the business process blog where Rob posts. For most of the EA folks I have spoken with lately, information architecture and MDM are very relevant -- not to mention thorny -- topics. I hope you join us for a great discussion!
Rob's description of the session:
Many large organizations have finally “seen the light” and are trying to figure out the best way to treat their critical data as the trusted asset it should be. As a result, master data management (MDM) strategies, and the enabling architectures, organizational and governance models, methodologies and technologies that support the delivery of MDM capabilities are…in a word…HOT! But the concept of MDM - and the homegrown or vendor-enabled technologies that attempt to deliver that elusive “single version of truth”, “golden record”, or “360-degree view” - has been around for decades in one form or another (e.g., data warehousing, BI, data quality, EII, CRM, ERP, etc. have all at one time or another promised to deliver that single version of truth in one form or another).
My colleague Boris Evelson, who covers business intelligence for Forrester and serves business process professionals, recently wrote a great post about the use of spreadsheets for business intelligence. He explains that while many BI vendors initially sought to replace spreadsheets in the corporate environment, it's now clear that they are not going anywhere any time soon.
Sound familiar? While many governance, risk, and compliance professionals and GRC vendors continue to work toward helping customers consolidate data and move away from spreadsheets, they are still basically ubiquitous. In fact, several of the top GRC vendors are now working to improve the way their tools interface with Excel... Not just for exporting reports, but for data input and analysis as well.
I recommend reading Boris' post, where he details three best practices regarding the use of spreadsheets for BI:
Create spreadsheet governance policies.
Monitor and enforce compliance with those policies.
Give preference to vendors that work well with spreadsheets.
Creating clear policies for what information will and will not be managed on spreadsheets is critical here, and extremely important for the GRC universe. Unless you have specially-built controls, spreadsheets do not give you the level of security, access control, change control, or audit trail you should have for data related to compliance or risk management. Knowing Office tools are going to be handling substantial amounts of important information for the foreseeable future, so it's worthwhile to review and update your policies and make sure they are being appropriately enforced.