Skip to main content


Showing posts from 2014

Webinars, Summits, Awards, Conferences, Testing Like an Olympian, and More!

The analysts at voke are embarking on a busy time of year! Join voke founder, Theresa Lanowitz, on October 28, 2014 at 8:30AM Pacific / 11:30AM Eastern to discuss “ The Hidden Cost of Rework ”. Each and every software project has defects – that is just a fact. However, the longer the defect is ignored, the more expensive it is to remediate. Join Theresa Lanowitz of voke and Jon Jarboe of Coverity to learn how to identify defects earlier and reduce the cost of rework involved with every software project. Register here to learn about “The Hidden Cost of Rework”  Next up, voke founder, Theresa Lanowitz, will be the keynote presenter at the Cognizant Quality Engineering and Assurance Summit in Sydney, Australia! The theme of the event is “The Future of Quality: Challenge the Conventional Status Quo”. The event is Thursday, November 6. If you are in the ANZ region, register here .  Theresa’s keynote will discuss “Software Quality in the Sound Bite Era”. Join Theresa to

Opinions Wanted – Service Virtualization

We are running a market survey on service virtualization and really want to know what you think of service virtualization . Are you using it, have you evaluated it, or is the technology brand new to you? We want to hear from you! Take the voke survey on service virtualization.   Service virtualization is one of those technologies that comes along once in a generation and makes a real difference on many levels. Service virtualization helps remove the constraints associated with the classic cost, quality, schedule timeline. Please let us know why you like service virtualization, what the benefits of service virtualization are, how you are using service virtualization across your software supply chain. Let us know by taking the survey.     This survey consists of a combination of multiple choice and optional short answer questions to provide you the opportunity to influence our research and the overall market based on your experiences. The areas of focus for the sur

Do You Know Your Cost of Rework? voke Publishes New Research on Reducing the Cost of Rework

Are you aware of what your cost of rework is for your software? Yes, the very software that runs your business and is an integral part of your brand promise. Most organizations are either not aware or not interested in what the cost of rework means. However, this cavalier stance to the cost of rework is dangerous. Each and every software project has an associated cost of rework – that is the cost involved with removing defects. The later in the lifecycle a defect is discovered, the more expensive it is to remediate. Defects create the hidden cost of rework in every software project. The new voke Strategic Brief TM Report: Reducing the Cost of Rework highlights: The business impact of defect leakage with real-world use cases The cost of rework models for both Agile and non-Agile projects Ways to test earlier to reduce rework and its costs The Strategic BriefTM Report: Reducing the Cost of Rework is available here or at for su

voke Research on Virtual and Cloud-based Labs Published!

In my last post I asked for your opinions on virtual and cloud-based labs.   Thank you so much for letting us know what you think of virtual and cloud-based labs! On August 21, 2014 voke officially published its Market Snapshot TM Report: Virtual and Cloud-based Labs. The full report is available here  or at to subscribers. While virtual and cloud-based lab technology has been widely available since 2005, we still see development and test teams wait for protracted periods of time to gain access to the physical environments needed. From our research, we now know that on average, teams wait for 18 days to gain access to the required physical environments needed for development or testing. And, these teams that wait to access physical environments also have restrictions on environment access time. This type of lost productivity is easily remedied with virtual or cloud-based labs. The full report contains an abundance of data to help make the ca

Looking for Opinions on Virtual Labs or Dev/Test Clouds

One of the most frustrating hurdles to overcome in the software lifecycle is the availability of a lab for testing. Physical test labs are expensive to build and expensive to maintain. To use a physical test lab, teams must schedule time well in advance, wait for access, and hurry up and get out of the lab for the next team. There has to be a better way of testing in a production-like environment. Well, there is. Virtualization helped us solve this problem. By using a virtual lab or a dev/test cloud, testing teams have an environment as close to production for use at any time for as long as needed. These virtual labs or dev/test clouds remove provisioning bottlenecks associated with physical labs, give testers an affordable production-like environment, and eliminate the phrase “it works on my machine”. Yes, virtual labs or dev/test clouds bring about peace between developers and testers. With virtual labs or dev/test clouds, developers are able to easily re-create a defect

Is HP Getting Serious About Lifecycle Virtualization?

HP Announces Intent to Acquire Network Virtualization Business and Technology of Shunra  I s HP Getting Serious About Lifecycle Virtualization? In a quiet blog post on the evening of March 4, 2014, HP announced that it had signed a definitive agreement to acquire the network virtualization business and technology of Shunra , a current HP partner. The HP blog post continues to outline the benefits the Shunra technology will bring to its mobile software testing business. The blog post ends with an almost cryptic mention of expanding the use of the Shunra technology to other HP products and services such as service virtualization . Service virtualization, indeed, is where the Shunra technology will mesh well with HP offferings. Service virtualization is defined by voke as: Enabling development and test teams to simulate and model their dependencies of unavailable or limited services. Removes constraints and wait times frequently experienced by development and test teams to