Blog Archive

October 2013

There has been a lot of buzz in the industry around Risk Based Testing. Before we talk about this, let’s agree on why we do testing. Testing is basically a component of a risk mitigation strategy for any project, regardless of the size. The objective of testing is to uncover defects that may lead to undesirable results for the system users and for the organization. The potential for undesirable results are generally referred to as risk.

The concept of a crystal ball has always bothered me a little bit… I mean, it seems like it would be good idea to know what’s to come in the future, but doesn’t knowing change everything??? Being unable to ‘know the unknown’ presents most people with two options to consider: 1) accept that one can only solve today’s challenges and face them as they appear; or 2) prepare for everything and hope for the best.

In this Guidewire Smart Approach Blog post, I am going to attempt to answer one of the most common questions I get as a Professional Services Director at Guidewire. That question comes very early in the project lifecycle, sometimes even before a project is approved to move forward.  The question I hear repeatedly from a majority of our customers is, “What should we be doing to get ready for our Guidewire project?”