Vision = re­al­ity

User Acceptance Testing

User Acceptance Testing is the key qual­ity as­sur­ance process as­signed to Product Owners. It’s an op­por­tu­nity to con­firm or de­cline that the it­er­a­tion was com­pleted to the Product Owner’s sat­is­fac­tion against the de­fined scope. User Acceptance Tests should be per­formed against all tick­ets com­pleted dur­ing an it­er­a­tion and com­pared against the agreed upon ac­cep­tance cri­te­ria.

Performing these can be done in two ways: the first in­volves the Product Owner com­plet­ing them in their own time and sub­mit­ting de­ci­sions re­motely. The al­ter­na­tive is for the Product Owner to join a mem­ber of the de­liv­ery team in a fo­cused walk­through ses­sion. This al­lows an in­ter­nal de­vel­oper to wit­ness any is­sues as they oc­cur, which can be very valu­able for rec­ti­fy­ing prob­lems. This is the pre­ferred method, as it en­sures that the tests are com­pleted thor­oughly, and the team can be sure that any is­sues which oc­cur are truly is­sues, and not user er­ror. 

UAT Kickback

In the soft­ware world, it is not un­com­mon for a Product Owner to pro­vide feed­back which needs to be ad­dressed af­ter UATs. Depending on the ur­gency of the change, there are three rec­om­mended meth­ods to han­dle it:

  • Urgent: This re­quires an ur­gent res­o­lu­tion which must be re­solved in the next re­lease. In this sit­u­a­tion the de­liv­ery team should in­clude the ticket into the cur­rent it­er­a­tion and ei­ther de­lay its com­ple­tion or re­move a ticket of the same size.

  • Next Iteration: The res­o­lu­tion is a high pri­or­ity but does­n’t need to be re­solved im­me­di­ately. The ticket should be marked as a con­tender for the next it­er­a­tions back­log.

  • Backlog: The dis­cov­ered prob­lem is deemed a low pri­or­ity and as a re­sult should be placed in the back­log for later con­sid­er­a­tion.

Iteration backlog infographic

Discover Software

Get cu­rated con­tent on soft­ware de­vel­op­ment, straight to your in­box.