Acceptance criteria
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Acceptance criteria

on

  • 8,225 views

 

Statistics

Views

Total Views
8,225
Views on SlideShare
7,723
Embed Views
502

Actions

Likes
4
Downloads
84
Comments
0

7 Embeds 502

http://blog.softheme.com 242
http://www.softheme.com 235
http://softheme.com 19
http://www.linkedin.com 3
http://www.softheme.comwww.softheme.com 1
http://www.softheme.com. 1
http://www.softheme.kiev.ua 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Acceptance criteria Presentation Transcript

  • 1. Defining Acceptance criteria in Agile projects + fast documentation within iterations
  • 2. When is the software ready?It was always hard toformalize acceptance.It is easier in Agile project –acceptance takes place at theend of each iteration.Fixing acceptance criteria andthe results of acceptancetesting = simplification + fastdocumentation.
  • 3. Definition of acceptance criteriaSet of statements (result -pass/fail),that specify functionalrequirements (MMF = MinimalMarketable Functionality)and cover non-functional (MQR =Minimal Quality Requirements),applicable at the current stage ofintegration.
  • 4. Acceptance criteria in Agile When 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 risksAll at minimal time spendings as a part of sprint initiation process!
  • 5. Teamwork acceptance Historically acceptanceoccurs on the side of thecustomer, but in Agileteams this function goesto the side of the team asa part of iteration
  • 6. Acceptance criteria and Acceptance testing in Agile iterationsAcceptance 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 ofeither pass or fail).
  • 7. Building the Functionality -> Requirements -> Acceptance criteria chain
  • 8. Optimally all members of the Agile team take part in defining Acceptance criteriaThis 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
  • 9. Acceptance criteria: +1 in development productivity and application stability Help QA Engineers Acceptance Help developers evaluate time fordefine minimal criteria for an development functional coverage iteration faster For all team members: • Rapid documentations • Less time for setting and understanding the tasks
  • 10. Thanks!About Softheme:Softheme provides QA and testing services for desktop, weband mobile applications since 2009.More than 30 mobile applications successfully released.