{"id":71,"date":"2014-01-01T07:56:04","date_gmt":"2014-01-01T12:56:04","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=71"},"modified":"2014-12-21T08:33:45","modified_gmt":"2014-12-21T13:33:45","slug":"over-what-time-frame","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/over-what-time-frame\/","title":{"rendered":"Over what time frame?"},"content":{"rendered":"<p><strong>Takeaway<\/strong>: Ask &#8220;Over what time frame?&#8221;<br \/>\n<strong>When to use?<\/strong>: As always, it depends. I usually ask &#8220;Over what time frame&#8221; when I seem to be agreeing with multiple sides of an argument.<\/p>\n<p>&#8220;Over what time frame?&#8221; is a powerful question to set context, especially in early stage software and\/or recently formed teams. Why? Because the quality of a solution is heavily influenced by the time frame over which it needs to be delivered.<\/p>\n<p><a href=\"http:\/\/qxf2.com\/blog\/wp-content\/uploads\/2014\/01\/solution_timeframe1.png\" data-rel=\"lightbox-image-0\" data-rl_title=\"\" data-rl_caption=\"\" title=\"\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/qxf2.com\/blog\/wp-content\/uploads\/2014\/01\/solution_timeframe1.png\" alt=\"solution_timeframe\" width=\"599\" height=\"322\" class=\"aligncenter size-full wp-image-129\" srcset=\"https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2014\/01\/solution_timeframe1.png 599w, https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2014\/01\/solution_timeframe1-300x161.png 300w, https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2014\/01\/solution_timeframe1-500x268.png 500w\" sizes=\"auto, (max-width: 599px) 100vw, 599px\" \/><\/a><\/p>\n<p>Obvious? Not always. Smart, competent people agree on a problem but argue over the solution without clarifying that time frame is the primary reason driving their choice of solution. Sometimes business wants <i>home<\/i> but development proposes <i>the bushes<\/i>. As a tester, you can likely prevent a ton of errors early on by<br \/>\n1. clarifying expectations<br \/>\n2. anchoring why the solution is being chosen<br \/>\n3. getting a feel for what business\/users mean by &#8216;quality&#8217; of the solution  <\/p>\n<p>If this is your first time trying this, be warned that there are plenty of non-answers. You could hear vague non-answers like: short term, medium term, long term, fairly early on, at steady state, as soon as possible, fairly urgently, its a priority, etc. One way to handle this, is to follow up with a thoughtful &#8216;Hmmmm &#8230; I need some clarity. What do you mean by short term?&#8217; or &#8216;I am assuming short term is within the next one month. Are we all on the same page ?&#8217;<\/p>\n<hr>\n<p><strong>What is the context for this post?<\/strong><br \/>\nI believe some software bugs are born outside of code. I believe testers should try, where possible, to prevent potential bugs before a single line of code is written. Testers can play a big role by continuously asking context, polling for expectations and explicitly communicating assumptions and potential risks about the software. This post is one in a series of tools, questions and tactics that testers can use to set better context.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Takeaway: Ask &#8220;Over what time frame?&#8221; When to use?: As always, it depends. I usually ask &#8220;Over what time frame&#8221; when I seem to be agreeing with multiple sides of an argument. &#8220;Over what time frame?&#8221; is a powerful question to set context, especially in early stage software and\/or recently formed teams. Why? Because the quality of a solution is [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[82],"tags":[7,8,10,9],"class_list":["post-71","post","type-post","status-publish","format-standard","hentry","category-thoughts-on-testing","tag-context","tag-prevent","tag-questions","tag-time-frame"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/71","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=71"}],"version-history":[{"count":16,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/71\/revisions"}],"predecessor-version":[{"id":650,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/71\/revisions\/650"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=71"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=71"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=71"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}