Saturday, November 17, 2007

Customer acceptance testing

This is advice on acceptance testing from an article here.

Acceptance Testing


Seventy percent of all software projects fail outright. When considering the other 30% of "successful" projects, you find many cases where the organisations involved merely declared victory and shut everything down.

But why do projects fail? Missing, miscommunicated, or misunderstood requirements are by far the biggest reasons. Hopefully I've given you some tools to help make these problems go away.

A close second to all this? Lack of end-user acceptance. Why? Because rarely are front-line troops—the ones who will use your application—ever invited to stakeholder meetings. They never get to give any input. Their managers or outside consultants are the only ones you ever meet. Unfortunately, these people don't have the kind of visibility actual users of your system have.

Ignore the end user at your own peril! Most of the time, the stakeholders you're dealing with don't know you need to talk to end users at all. You're the expert, not them! Even if they present you with reams of documents in which they've covered every conceivable request from end users, request a tour of the office or plant floor. Meet some end users. Take them out to lunch. Talk to them early, see what's bugging them.

Spend an afternoon just hanging out watching what happens. How do their processes get them through the day? Where do their processes get in the way? Where do they put in short cuts to avoid bureaucratic nightmares? Does person A from this department do small favours for person B in finance to expedite work orders?

If you ignore the end user at the beginning of the process, if you don't talk to them upstream, you certainly will be talking to them at the end of the process, when you deliver the final application for acceptance testing and/or training.

Guess what? Those stakeholders who didn't give you access to the end users early on will be asking those end users at the end of the project what they think of the new application, and you'll be judged by what they say. Fair? No. But you didn't ask, and they didn't have that kind of visibility into your expertise.

Remember, no one can verify you're on the right track more than an end-user who is an expert on a particular procedure or workflow.

Customer acceptance testing UK

Saturday, November 03, 2007

Guidelines on acceptance testing

From GCN.com

The Election Assistance Commission has issued six new sets of guidelines for election officials to help them with the chores of managing local elections.

The guidelines, several of which address technical issues, are part of a series of Quick Start Management Guides being produced by the commission. They are available online and also are being distributed as brochures to election officials. The commission plans to issue two new Quick Start brochures by the end of the year on military and overseas voting, and developing an audit trail.

The guide on acceptance testing explains what an acceptance test is and covers how to conduct a test for optical-scan ballot scanners, touch-screen voting stations and election management systems. A guide for contingency and disaster planning includes information on developing a management plan to address emergency and crisis response. It also covers developing a continuity-of-operations plan for elections and contingency planning for countywide events and internal operations.

Other guidelines cover absentee voting and voting by mail, managing change in an election office, media and public relations, and selection and preparation of polling places and vote centers.

To request copies or for more information on Quick Start Management Guides, call EAC at (866) 747-1471 or e-mail HAVAinfo@eac.gov. For information on EAC's voting system certification program, including test labs, registered voting system manufacturers, voting systems that have been submitted for testing, test plans, notices of clarification and other program-related information, visit http://www.eac.gov.