{"id":2529,"date":"2016-12-19T08:00:57","date_gmt":"2016-12-19T08:00:57","guid":{"rendered":"http:\/\/www.diogonunes.com\/blog\/?p=2529"},"modified":"2020-05-15T14:23:23","modified_gmt":"2020-05-15T13:23:23","slug":"10-principles-agile-testers","status":"publish","type":"post","link":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/","title":{"rendered":"Testing for agile teams: 10 principles for agile testers (#2)"},"content":{"rendered":"<p><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?resize=489%2C340\" alt=\"Agile Testing Book Part 2\" width=\"489\" height=\"340\" class=\"aligncenter size-full wp-image-2670\" srcset=\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?w=489&amp;ssl=1 489w, https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?resize=400%2C278&amp;ssl=1 400w\" sizes=\"auto, (max-width: 489px) 100vw, 489px\" \/><\/p>\n<p><em>This post is part of the <a href=\"http:\/\/www.diogonunes.com\/blog\/?s=Testing+for+Agile+Teams\">&#8220;Testing for Agile Teams&#8221; series<\/a><\/em>.<\/p>\n<p><!--more--><\/p>\n<blockquote>\n<p>What&#8217;s special about being an agile tester?<\/p>\n<\/blockquote>\n<ul>\n<li><strong>Collaborates<\/strong> well with both technical and business people.<\/li>\n<li><strong>Uses tests to document<\/strong> requirements and drive development.<\/li>\n<li><strong>Learns what customers do<\/strong> in order to fully understand the customers\u2019 requirements.<\/li>\n<li>Tends to see the <strong>big picture<\/strong> (according to the customers perspective).<\/li>\n<li>Good testers have an instinct and understanding for where and how software might fail.<\/li>\n<li>They should also be creative, eager to learn, willing to take on any task or role.<\/li>\n<\/ul>\n<h2>Provide continuous feedback<\/h2>\n<ul>\n<li><strong>Help the customer<\/strong> articulate requirements for each story as examples or tests.<\/li>\n<li>The development team works to fulfill these tests, guided by feedback.<\/li>\n<li>Make the tests progress visual (percentage written, run, passing).<\/li>\n<\/ul>\n<h2>Deliver value to the customer<\/h2>\n<ul>\n<li><strong>Make sure the &#8220;happy path&#8221; works<\/strong> (the right way to use the SW).<\/li>\n<li>Consider what adds the most value to the customer &#8212; safety-critical context? If not, leave edges cases for later.<\/li>\n<\/ul>\n<h2>Enable face-to-face communication<\/h2>\n<ul>\n<li><strong>Power of Three<\/strong>: programmer, tester, product owner.<\/li>\n<li><strong>Never get in the way<\/strong> of direct customer-developer communication. Know when to step away from being the <em>middle man<\/em>.<\/li>\n<li>Help the customer envision requirements: whiteboard discussions, examples, usage scenarios.<\/li>\n<\/ul>\n<h2>Have courage<\/h2>\n<ul>\n<li><strong>To fail<\/strong> (failing fast and learning) and <strong>to ask for help<\/strong>.<\/li>\n<li><strong>To let other fails<\/strong> (so they can learn and improve too).<\/li>\n<li>Create an automated regression suite as a safety net for programmers.<\/li>\n<\/ul>\n<h2>Keep it simple<\/h2>\n<ul>\n<li>Do the simplest thing that could possibly work (XP).<\/li>\n<li>The customer team decides what level of quality they want to pay for.<\/li>\n<li>Evaluate how far to go with edge cases.<\/li>\n<li><code>Simple != Easy<\/code>. For testers, <strong>it means<\/strong> testing &#8220;just enough&#8221; with light-weight tools.<\/li>\n<\/ul>\n<h2>Practice continuous improvement<\/h2>\n<ul>\n<li>The team always tries to do better work. <strong>Retrospectives<\/strong> let the team use yesterday\u2019s experience to do a better job tomorrow.<\/li>\n<li>It&#8217;s easy to try something new for a few iterations.<\/li>\n<li><strong>Always on the lookout<\/strong> for tools &amp; skills. Go to meetings, join mailing lists, read articles, blogs and books.<\/li>\n<li>Automate mundane or repetitive tasks.<\/li>\n<li>Anything not learned quickly might be deemed useless (ROI).<\/li>\n<\/ul>\n<h2>Respond to change<\/h2>\n<ul>\n<li>With agile instead of waterfall, customers can get their change when they want it because they control the <strong>priority<\/strong>.<\/li>\n<\/ul>\n<h2>Self-organize<\/h2>\n<ul>\n<li>Automating is a team effort.<\/li>\n<li>The team creates <strong>its own approach<\/strong> and commits to it.<\/li>\n<\/ul>\n<h2>Focus on people<\/h2>\n<ul>\n<li>Projects succeed when good people are allowed to do their best work.<\/li>\n<li>Opportunities to grow and develop their skills.<\/li>\n<li>Experienced testers ask important questions that didn\u2019t occur to the team.<\/li>\n<\/ul>\n<h2>Enjoy<\/h2>\n<hr \/>\n<p><em>This post is a personal summary of a chapter from the book <a href=\"http:\/\/www.amazon.co.uk\/gp\/product\/0321534468\/ref=as_li_tl?ie=UTF8&amp;camp=1634&amp;creative=6738&amp;creativeASIN=0321534468&amp;linkCode=as2&amp;tag=dionun-21\">Agile Testing: A Practical Guide For Testers And Agile Teams<\/a>. I&#8217;m sure you&#8217;ll find that book useful too.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This post is part of the &#8220;Testing for Agile Teams&#8221; series.<\/p>\n","protected":false},"author":1,"featured_media":2670,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[51],"tags":[54,55],"class_list":["post-2529","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-work","tag-agile","tag-testing"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko<\/title>\n<meta name=\"description\" content=\"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I&#039;m sure you&#039;ll find it useful too.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko\" \/>\n<meta property=\"og:description\" content=\"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I&#039;m sure you&#039;ll find it useful too.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\" \/>\n<meta property=\"og:site_name\" content=\"The Geeky Gecko\" \/>\n<meta property=\"article:published_time\" content=\"2016-12-19T08:00:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-15T13:23:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"489\" \/>\n\t<meta property=\"og:image:height\" content=\"340\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Diogo Nunes\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dialexnunes\" \/>\n<meta name=\"twitter:site\" content=\"@dialexnunes\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Diogo Nunes\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\"},\"author\":{\"name\":\"Diogo Nunes\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c\"},\"headline\":\"Testing for agile teams: 10 principles for agile testers (#2)\",\"datePublished\":\"2016-12-19T08:00:57+00:00\",\"dateModified\":\"2020-05-15T13:23:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\"},\"wordCount\":459,\"publisher\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c\"},\"image\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1\",\"keywords\":[\"agile\",\"testing\"],\"articleSection\":[\"Work\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\",\"url\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\",\"name\":\"Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko\",\"isPartOf\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1\",\"datePublished\":\"2016-12-19T08:00:57+00:00\",\"dateModified\":\"2020-05-15T13:23:23+00:00\",\"description\":\"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I'm sure you'll find it useful too.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage\",\"url\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1\",\"width\":489,\"height\":340},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.diogonunes.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Testing for agile teams: 10 principles for agile testers (#2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#website\",\"url\":\"https:\/\/www.diogonunes.com\/blog\/\",\"name\":\"The Geeky Gecko\",\"description\":\"The Geeky Gecko\",\"publisher\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.diogonunes.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c\",\"name\":\"Diogo Nunes\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2026\/04\/Geeky-Gecko-2026-v2.png?fit=799%2C799&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2026\/04\/Geeky-Gecko-2026-v2.png?fit=799%2C799&ssl=1\",\"width\":799,\"height\":799,\"caption\":\"Diogo Nunes\"},\"logo\":{\"@id\":\"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/image\/\"},\"sameAs\":[\"http:\/\/www.diogonunes.com\",\"https:\/\/x.com\/dialexnunes\"],\"url\":\"https:\/\/www.diogonunes.com\/blog\/author\/diogo-nunes\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko","description":"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I'm sure you'll find it useful too.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/","og_locale":"en_US","og_type":"article","og_title":"Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko","og_description":"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I'm sure you'll find it useful too.","og_url":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/","og_site_name":"The Geeky Gecko","article_published_time":"2016-12-19T08:00:57+00:00","article_modified_time":"2020-05-15T13:23:23+00:00","og_image":[{"width":489,"height":340,"url":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","type":"image\/jpeg"}],"author":"Diogo Nunes","twitter_card":"summary_large_image","twitter_creator":"@dialexnunes","twitter_site":"@dialexnunes","twitter_misc":{"Written by":"Diogo Nunes","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#article","isPartOf":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/"},"author":{"name":"Diogo Nunes","@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c"},"headline":"Testing for agile teams: 10 principles for agile testers (#2)","datePublished":"2016-12-19T08:00:57+00:00","dateModified":"2020-05-15T13:23:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/"},"wordCount":459,"publisher":{"@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c"},"image":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","keywords":["agile","testing"],"articleSection":["Work"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/","url":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/","name":"Testing for agile teams: 10 principles for agile testers (#2) - The Geeky Gecko","isPartOf":{"@id":"https:\/\/www.diogonunes.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage"},"image":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","datePublished":"2016-12-19T08:00:57+00:00","dateModified":"2020-05-15T13:23:23+00:00","description":"This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I'm sure you'll find it useful too.","breadcrumb":{"@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#primaryimage","url":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","width":489,"height":340},{"@type":"BreadcrumbList","@id":"https:\/\/www.diogonunes.com\/blog\/10-principles-agile-testers\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.diogonunes.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Testing for agile teams: 10 principles for agile testers (#2)"}]},{"@type":"WebSite","@id":"https:\/\/www.diogonunes.com\/blog\/#website","url":"https:\/\/www.diogonunes.com\/blog\/","name":"The Geeky Gecko","description":"The Geeky Gecko","publisher":{"@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.diogonunes.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/a6fa79b293f22912664654fcfbd2da0c","name":"Diogo Nunes","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2026\/04\/Geeky-Gecko-2026-v2.png?fit=799%2C799&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2026\/04\/Geeky-Gecko-2026-v2.png?fit=799%2C799&ssl=1","width":799,"height":799,"caption":"Diogo Nunes"},"logo":{"@id":"https:\/\/www.diogonunes.com\/blog\/#\/schema\/person\/image\/"},"sameAs":["http:\/\/www.diogonunes.com","https:\/\/x.com\/dialexnunes"],"url":"https:\/\/www.diogonunes.com\/blog\/author\/diogo-nunes\/"}]}},"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-2.jpg?fit=489%2C340&ssl=1","jetpack-related-posts":[{"id":2497,"url":"https:\/\/www.diogonunes.com\/blog\/testing-for-agile-teams-summary\/","url_meta":{"origin":2529,"position":0},"title":"Testing for agile teams: Summary","author":"Diogo Nunes","date":"1 August, 2016","format":false,"excerpt":"This post is part of the \"Testing for Agile Teams\" series. Incrementally delivering business value, through short iterations (SCRUM) and virtuous loops of feedback (XP). Roles' boundaries are blurred, everyone's focused on quality. Testers help customers clarify requirements, turn those into tests that guide development, and provide a holistic viewpoint\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book.jpg?fit=489%2C340&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2523,"url":"https:\/\/www.diogonunes.com\/blog\/testing-for-agile-teams\/","url_meta":{"origin":2529,"position":1},"title":"Testing for agile teams: Introduction (#1)","author":"Diogo Nunes","date":"10 October, 2016","format":false,"excerpt":"This post is part of the \"Testing for Agile Teams\" series. The agile way Remember the manifesto. Focus on delivering small chunks of business value in short cycles. Numerous implementations of the manifesto: Scrum, XP, Kanban, DSDM... Solve problems as a team of people who all feel responsible for delivering\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-1.jpg?fit=489%2C340&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2536,"url":"https:\/\/www.diogonunes.com\/blog\/four-testing-quadrants\/","url_meta":{"origin":2529,"position":2},"title":"Testing for agile teams: The four testing quadrants (#3)","author":"Diogo Nunes","date":"16 January, 2017","format":false,"excerpt":"This post is part of the \"Testing for Agile Teams\" series. We do different types of testing to accomplish different goals. Your team has its own unique context. It's a tool, not a rule. Tests that support the team Supports the team as it develops the product: Drives development to\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-4.jpg?fit=489%2C340&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2554,"url":"https:\/\/www.diogonunes.com\/blog\/tests-that-criticize-the-product\/","url_meta":{"origin":2529,"position":3},"title":"Testing for agile teams: Tests that review the product (#5)","author":"Diogo Nunes","date":"13 March, 2017","format":false,"excerpt":"This post is part of the \"Testing for Agile Teams\" series. All that's left is to possibly find some obscure or interesting bugs. And to avoid things like \"that's what I said, but it\u2019s not what I meant.\" Business-Facing Tests (Q3) All about trying to recreate actual experiences of the\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-3.jpg?fit=489%2C340&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2546,"url":"https:\/\/www.diogonunes.com\/blog\/tests-that-support-the-team\/","url_meta":{"origin":2529,"position":4},"title":"Testing for agile teams: Tests that support the team (#4)","author":"Diogo Nunes","date":"13 February, 2017","format":false,"excerpt":"This post is part of the \"Testing for Agile Teams\" series. Technology-Facing Tests (Q1) Strive to make time to test more complex scenarios and edge cases. TDD means writing a test that captures the behavior of a tiny bit of code and then working the code until the test passes.\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2016\/03\/Agile-Testing-Book-Part-5.jpg?fit=489%2C340&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":4379,"url":"https:\/\/www.diogonunes.com\/blog\/testing-concepts-5\/","url_meta":{"origin":2529,"position":5},"title":"Requirements (Concepts #5)","author":"Diogo Nunes","date":"8 November, 2021","format":false,"excerpt":"tl;dr Requirements are what your stakeholders require to achieve their goals. Testers clarify and detail those needs. Theory Here are some concepts you should keep in mind: Requirement: Some behaviour or property needed by a stakeholder to achieve a goal. Specification: The list containing all requirements for a given project\/product.\u2026","rel":"","context":"In &quot;Work&quot;","block_context":{"text":"Work","link":"https:\/\/www.diogonunes.com\/blog\/category\/work\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2021\/10\/leon-Oalh2MojUuk-unsplash.jpg?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2021\/10\/leon-Oalh2MojUuk-unsplash.jpg?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2021\/10\/leon-Oalh2MojUuk-unsplash.jpg?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2021\/10\/leon-Oalh2MojUuk-unsplash.jpg?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/www.diogonunes.com\/blog\/wp-content\/uploads\/2021\/10\/leon-Oalh2MojUuk-unsplash.jpg?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/posts\/2529","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/comments?post=2529"}],"version-history":[{"count":1,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/posts\/2529\/revisions"}],"predecessor-version":[{"id":3788,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/posts\/2529\/revisions\/3788"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/media\/2670"}],"wp:attachment":[{"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/media?parent=2529"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/categories?post=2529"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.diogonunes.com\/blog\/wp-json\/wp\/v2\/tags?post=2529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}