PDA

View Full Version : webMethods Ezine The webMethods Proof of Concept


dgreen
03-12-2003, 14:13
Questions or comments about this webMethods Ezine article?

Click here (http://www.wmusers.com/ezine/2003mar_dgreen_1.shtml) to read the original text.

mcarlson
03-12-2003, 14:18
Dan,

In many cases, proof of concept projects are used to help
evaluate competing vendor solutions. In others, POC
projects are used to perform a "fit analysis" to confirm, in
a hands-on manner, the findings of a software selection
project.

I would suggest that a POC conducted during (or just
following) a software evaluation has a narrower definition
and goal than an organizations first "live" webMethods
project.

The result of this type of POC is to select or to confirm
the selection of webMethods rather than to be the initial
demonstration of webMethods value.

Would you agree and if so would you change any of your
recommendations to fit this type of POC?

Mark

dgreen
03-12-2003, 14:18
I agree with your assessment, Mark. Drawing on experience,
the term "Proof of Concept" has been used interchangeably
with the product demonstration you describe and the first
"live" webMethods project to which article refers.

For clarity's sake, the ezine article could have referenced
the first enterprise webMethods-based project; it is just a
matter of semantics.

The POC to which you refer is generally consultant-driven
and fixed on technical details as opposed to business
process. It is used to help potential (or new) webMethods
customers understand the processing power and logical
limitations of the software platform. With respect to
projects like this, my article is moot -- this type of
project is more of a Suitability Study than anything else.

Would you agree?

mcarlson
03-12-2003, 14:18
Actually, I do think that proper planning and project
structure is needed for a suitability or fit analysis
project as well.

And the proper use of consultants during this stage can
really help to accelerate the internal team's learning curve
or to avoid some incorrect conclusions drawn based on
inadequate training or experience.

One approach is to get the vendor to pony up a resource or
two to do the suitability study at no or little cost.
However, that approach can tend not to uncover any real
issues as the vendor's resources often know all of the
workarounds well enough to disguise any shortcomings.

Using experienced (and objective) and consultant during
either the suitability study or the POC can help achieve the
goal of confirming the fit of a product or confirming the
value via a carefully planned initial project.