Defining Acceptance criteria in Agile projects

+ fast documentation within iterations

When is the software ready?

It was always hard to formalize acceptance.

It is easier in Agile project – acceptance takes place at the end of each iteration.

Fixing acceptance criteria and the results of acceptance testing = simplification + fast documentation.

Definition of acceptance criteria

Set of statements (result - pass/fail), that specify functional requirements (MMF = Minimal Marketable Functionality) and cover non-functional (MQR = Minimal Quality Requirements), applicable at the current stage of integration.

Acceptance criteria in AgileWhen clearly stated, they allow:• define functional requirements at the

beginning of each sprint• create fast version of documented

functionality• synchronize vision of tasks by developers

and testers• estimate timings for each task• get extended picture of risks

All at minimal time spendings as a part of sprint initiation process!

Teamwork acceptance

Historically acceptance occurs on the side of the customer, but in Agile teams this function goes to the side of the team as a part of iteration

Acceptance criteria and Acceptance testing in Agile iterations

Acceptance criteria are defined after division of tasks from the back-log, before code design and test case creation.

They are used in the process of build smoke-testing (take the value of either pass or fail).

Building the Functionality -> Requirements -> Acceptance criteria chain

Optimally all members of the Agile team take part in defining Acceptance criteria

This allows to:• Define the оptimal way of

implementation in terms of customer expectations

• Move on from division of functions for iteration to code development/creating test cases

• Better understand the product on the stage of bug-fixing

Acceptance criteria: +1 in development productivity and application stability

Acceptance criteria for an

iteration

Help QA Engineers

define minimal functional coverage

Help developersevaluate time for

development faster

For all team members:• Rapid documentations• Less time for setting and understanding the tasks

Thanks!

About Softheme: Softheme provides QA and testing services for desktop, web and mobile applications since 2009.More than 30 mobile applications successfully released.