{"id":52,"date":"2016-07-19T19:22:02","date_gmt":"2016-07-19T19:22:02","guid":{"rendered":"https:\/\/kenpugh.com\/blog\/?p=52"},"modified":"2016-07-20T16:41:21","modified_gmt":"2016-07-20T16:41:21","slug":"atdd-solves-development-issues","status":"publish","type":"post","link":"https:\/\/kenpugh.com\/blog\/atdd-solves-development-issues\/","title":{"rendered":"ATDD Solves Development Issues"},"content":{"rendered":"<p>\n\u00a0<\/p>\n<p>I&#8217;ve been teaching Acceptance Test-Driven Development (ATDD) for many years.   At the start of every course, I ask the attendees for issues they have with their development processes.    After they have experienced the ATDD process, including creation of acceptance tests, I review their issues to see whether they feel that ATDD will help, hurt, or be neutral in respect to those issues. <!--more--><\/p>\n<p>Here&#8217;s a sampling of the issues in the attendees words.  According to them, ATDD will help in solving:\n<\/p>\n<ul>\n<li>Unclear requirements\n<\/li>\n<li>Missed requirements\n<\/li>\n<li>No detailed requirements\n<\/li>\n<li>Development without requirements\n<\/li>\n<li>Unclear business rules\n<\/li>\n<li>Poorly defined acceptance criteria\n<\/li>\n<li>\n\t\t<\/li>\n<li>Huge user stories\n<\/li>\n<li>Smaller stories leave gaps\n<\/li>\n<li>Not enough detail in stories\n<\/li>\n<li>\n\t\t<\/li>\n<li>Not enough testers\n<\/li>\n<li>Missing test cases\n<\/li>\n<li>Not enough time for testing\n<\/li>\n<li>Stories not verifiable until end of the sprint\n<\/li>\n<li>Test data not available\n<\/li>\n<li>Issues with integration tests\n<\/li>\n<li>\n\t\t<\/li>\n<li>Coding starts before tests are written\n<\/li>\n<li>Development team not understanding business process\n<\/li>\n<li>Acceptance tests written for coding, not testing perspective\n<\/li>\n<li>Communication challenges \u2013 IT is technical, business is not technical\n<\/li>\n<\/ul>\n<p>If you have any of these issues, there&#8217;s a great chance that adopting ATDD will help in solving it.\n<\/p>\n<p>In my book, Lean-Agile Acceptance Test-Driven Development, I have reports from many people on how ATDD has benefited them.   Here&#8217;s a summary of those benefits:\n<\/p>\n<ul>\n<li>Rework Down from 60% to 20%\n<\/li>\n<li>Little Room for Miscommunication\n<\/li>\n<li>Workflows Working First Time\n<\/li>\n<li>Getting Business Rules Right\n<\/li>\n<li>Crisp Visible Story Completion Criteria\n<\/li>\n<li>Tighter Cross-Functional Team Integration\n<\/li>\n<li>Game Changing\n<\/li>\n<li>Saving Time\n<\/li>\n<li>Automation Yields Reduced Testing Time\n<\/li>\n<\/ul>\n<p>As you can see, ATDD can benefit your process in many ways.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u00a0 I&#8217;ve been teaching Acceptance Test-Driven Development (ATDD) for many years. At the start of every course, I ask the attendees for issues they have with their development processes. After they have experienced the ATDD process, including creation of acceptance tests, I review their issues to see whether they feel that ATDD will help, hurt, &hellip; <a href=\"https:\/\/kenpugh.com\/blog\/atdd-solves-development-issues\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">ATDD Solves Development Issues<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-52","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/posts\/52","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/comments?post=52"}],"version-history":[{"count":2,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/posts\/52\/revisions"}],"predecessor-version":[{"id":80,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/posts\/52\/revisions\/80"}],"wp:attachment":[{"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/media?parent=52"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/categories?post=52"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenpugh.com\/blog\/wp-json\/wp\/v2\/tags?post=52"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}