{"id":32600,"date":"2018-10-04T09:57:31","date_gmt":"2018-10-04T13:57:31","guid":{"rendered":"https:\/\/sdtimes.com\/?p=32600"},"modified":"2018-10-04T09:57:31","modified_gmt":"2018-10-04T13:57:31","slug":"defining-software-quality-metrics-for-agile-and-devops","status":"publish","type":"post","link":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/","title":{"rendered":"Defining software quality metrics for Agile and DevOps"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">In a a Tricentis-commissioned report from Forrester released in July, \u201cThe Definitive Software Quality Metrics For Agile+DevOps,\u201d surveyors found that it\u2019s a common trait of companies that have seen the most success from Agile and DevOps adoption that they have made another operational transition. These companies have moved on from considering \u201ccounting\u201d metrics \u2014 for instance, whether you\u2019ve run tests an adequate number of times \u2014 as key indicators of success, to \u201ccontextual\u201d metrics \u2014 whether the software meets all of the requirements of the user experience, and that these are better indicators of success.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This conclusion is based on the report\u2019s findings that of the 603 enterprise Agile and DevOps specialists surveyed, those referred to as \u201cDevOps leaders\u201d are significantly better at measuring success and are much further along in their pursuit of end-to-end automation, a key ingredient in meeting the rapid development and delivery expected of modern software cycles.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It seems that somewhere along the way, there is a bottleneck holding some businesses back while the DevOps leaders speed ahead; fifty-nine percent of respondents placed the blame squarely on manual testing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This focus on automated end-to-end functional testing is among four other best-practices that \u00a0the report\u2019s findings say are almost universally employed by DevOps leaders. They are:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Properly allocated testing budgets and a focus on upgrading testing skills<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">The implementation of continuous testing \u201cto meet the demands of release frequency and support continuous delivery\u201d<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">The inclusion of testers as part of integrated delivery teams<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">A shift left to implement testing earlier in development<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">But businesses shouldn\u2019t be quick to rush the gates on implementing test automation across the board \u2014 there are some risks involved.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cAutomating the software development life cycle is an imperative for accelerating the speed and frequency of releases,\u201d Forrester wrote in its report. \u201cHowever, without an accurate way to measure and track quality throughout the software development life cycle, automating the delivery pipeline could increase the risk of delivering more defects into production. And if organizations cannot accurately measure business risk, then automating development and testing practices can become a huge danger to the business.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">All businesses, even DevOps leaders, should pay heed. According to Forrester, 80 percent of respondents believe that they \u201calways or often deliver customer-facing products that are within acceptable business risk.\u201d This despite that only 29 percent of DevOps \u201claggards\u201d think that delivering software within acceptable business risk is \u201cvery important,\u201d and only 50 percent of leaders think so. Forrester speculates that this finding must be a mass overestimation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cGiven that most firms, even the ones following continuous testing best practices, admit that their software testing processes have risk gaps and do not always give accurate measures of business risk, it stands to reason that the 80% who say they always or often deliver within acceptable risk may be overestimating their capabilities,\u201d Forrester wrote in the report.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Diego Lo Giudice, vice president and principal analyst at Forrester and the lead on the report, found this disparity unusual.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cI think it\u2019s more intentional than truth \u2014 they get it that business risk is of paramount importance and have the illusion of addressing it,\u201d Lo Giudice said. \u201cIt\u2019s a misinterpretation of what real business risk is perhaps? I think it\u2019s hard to keep testing and quality focus on business risk.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Wayne Ariola, chief marketing officer at Tricentis, was a little more sure of where this disconnect lay.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cThis is your classic geek gap,\u201d Ariola said. \u201cBusiness leaders assume that the definition of risk is aligned to a business-oriented definition of risk, but the technical team has it aligned to a very different definition of risk. This mismatch is your primary cause of overconfidence. For example, assume a tester saw that 100 percent of the test suite ran with an 80 percent pass rate. This gives you no indication of the risk associated with the release. The 20 percent that failed could be an absolutely critical functionality, like security authentication, or it could be trivial, like a UI customization option that\u2019s rarely used.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Avoiding this pitfall comes with the preparedness provided by knowing which metrics to watch to know whether a process is ready for automation. But there is yet another gap that sees less developed DevOps and Agile initiatives tracking metrics that used to mean a lot, but have very little value once a digital transformation is fully underway.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201c\u2018Counting\u2019 metrics lost their value because the question changed for DevOps,\u201d Ariola said. \u201cIt was no longer about how much testing you completed in the allotted time. The focus shifted to whether you could release and what business risks were associated with the release. If you can answer this question with five tests, that\u2019s actually better than answering it with 5,000 tests that aren\u2019t closely aligned with business risk. Count doesn\u2019t matter \u2014 what\u2019s important is \u2014 one, the ability to assess risk and two, the ability to make actionable decisions based on test results.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Forrester\u2019s Lo Giudice also elaborated on what \u201coutdated\u201d metrics were and where focus should be shifted.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cMeasuring productivity is one example,\u201d Lo Giudice said. \u201cTeams focus on the amount of output, or read code, not necessarily valuable outcomes for the business or the right code. Agile focuses on both building the right things and [evaluating] things right, so value metrics become more important than productivity of teams, and so related productivity metrics lose relevance. Quality, however, remains always of paramount importance. \u201c<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Quality can severely slip if proper metrics aren\u2019t tracked and businesses continue operating on old metrics while trying to implement modern automated testing initiatives. Businesses need to be aware of those risks, Tricentis\u2019 Ariola explained.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cWe\u2019ve seen many organizations that are severely over-testing,\u201d Ariola said. \u201cThey\u2019re running massive test suites against minor changes\u2014self-inflicting delays for no good reason. To start, organizations must take a step back and really assess the risks associated with each component of their application set. Once risk is better understood, you can identify practices that will mitigate those risks much earlier in the process. This is imperative for speed and accuracy.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In its report, Forrester lists which metrics and factors are rated the highest in importance by the successful DevOps leaders. The figure below, taken from the report, breaks down the stages of development and shows which factors these leaders considered a priority during each stage.<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-32601\" src=\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM.png\" alt=\"\" width=\"627\" height=\"305\" srcset=\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM.png 627w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-300x146.png 300w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-490x238.png 490w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-150x73.png 150w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-400x195.png 400w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-320x156.png 320w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-164x80.png 164w, https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/Screen-Shot-2018-10-04-at-9.54.39-AM-100x50.png 100w\" sizes=\"(max-width: 627px) 100vw, 627px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Productivity, while still an obvious goal of a successful business, is not precisely where Agile and DevOps specialists should be putting their thoughts. \u201cOnce risk is better understood, you can identity practices that will mitigate those risks much earlier in the process. This is imperative for speed and accuracy,\u201d Ariola said. Productivity will then follow.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cIn the past, when software testing was a timeboxed activity at the end of the cycle, we focused on answering the question, \u2018Are we done testing?\u2019 Ariola said. \u201cWhen this was the primary question, counting metrics associated with the number of tests run, incomplete tests, passed tests, failed tests, etc. drove the process and influenced the release decision. As you can imagine, these metrics are highly ineffective in understanding the actual quality of a release. In today\u2019s world, we have to ask a different question: \u2018Does the release have an acceptable level of risk?\u2019\u201d<\/span><\/p>\n<!-- AddThis Advanced Settings generic via filter on the_content --><!-- AddThis Share Buttons generic via filter on the_content -->","protected":false},"excerpt":{"rendered":"<p>In a a Tricentis-commissioned report from Forrester released in July, \u201cThe Definitive Software Quality Metrics For Agile+DevOps,\u201d surveyors found that it\u2019s a common trait of companies that have seen the most success from Agile and DevOps adoption that they have made another operational transition. These companies have moved on from considering \u201ccounting\u201d metrics \u2014 for  &hellip; <a class=\"read-more\" href=\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\">continue reading<\/a><!-- AddThis Advanced Settings generic via filter on get_the_excerpt --><!-- AddThis Share Buttons generic via filter on get_the_excerpt --><\/p>\n","protected":false},"author":738,"featured_media":32602,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"cybocfi_hide_featured_image":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[1],"tags":[132,254,841,738,1051,6777],"coauthors":[11418],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Defining software quality metrics for Agile and DevOps - SD Times<\/title>\n<meta name=\"description\" content=\"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Defining software quality metrics for Agile and DevOps - SD Times\" \/>\n<meta property=\"og:description\" content=\"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\" \/>\n<meta property=\"og:site_name\" content=\"SD Times\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/SDTimesD2\" \/>\n<meta property=\"article:published_time\" content=\"2018-10-04T13:57:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"660\" \/>\n\t<meta property=\"og:image:height\" content=\"371\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ian C. Schafer\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@iancsc\" \/>\n<meta name=\"twitter:site\" content=\"@sdtimes\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ian C. Schafer\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\"},\"author\":{\"name\":\"Ian C. Schafer\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/9022c63a7e3a542f7a9df8385ad5fd3f\"},\"headline\":\"Defining software quality metrics for Agile and DevOps\",\"datePublished\":\"2018-10-04T13:57:31+00:00\",\"dateModified\":\"2018-10-04T13:57:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\"},\"wordCount\":1214,\"publisher\":{\"@id\":\"https:\/\/sdtimes.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg\",\"keywords\":[\"agile\",\"DevOps\",\"Forrester\",\"metrics\",\"software quality\",\"Tricentis\"],\"articleSection\":[\"Latest News\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\",\"url\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\",\"name\":\"Defining software quality metrics for Agile and DevOps - SD Times\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg\",\"datePublished\":\"2018-10-04T13:57:31+00:00\",\"dateModified\":\"2018-10-04T13:57:31+00:00\",\"description\":\"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands\",\"breadcrumb\":{\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage\",\"url\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg\",\"contentUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg\",\"width\":660,\"height\":371},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sdtimes.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Defining software quality metrics for Agile and DevOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sdtimes.com\/#website\",\"url\":\"https:\/\/sdtimes.com\/\",\"name\":\"SD Times\",\"description\":\"Software Development News\",\"publisher\":{\"@id\":\"https:\/\/sdtimes.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sdtimes.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/sdtimes.com\/#organization\",\"name\":\"SD Times\",\"url\":\"https:\/\/sdtimes.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png\",\"contentUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png\",\"width\":225,\"height\":90,\"caption\":\"SD Times\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/SDTimesD2\",\"https:\/\/x.com\/sdtimes\",\"https:\/\/www.linkedin.com\/company\/sdtimes\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/9022c63a7e3a542f7a9df8385ad5fd3f\",\"name\":\"Ian C. Schafer\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/image\/d2379e9eeb891a65bb56e82be996e74d\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/af176b4e562bd686310678b2fa6c6011?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/af176b4e562bd686310678b2fa6c6011?s=96&d=mm&r=g\",\"caption\":\"Ian C. Schafer\"},\"description\":\"Ian C. Schafer is a multimedia reporter and undeniable nerd living and working in New York City and on Long Island.\",\"sameAs\":[\"http:\/\/iancschafer.com\",\"https:\/\/x.com\/iancsc\"],\"url\":\"https:\/\/sdtimes.com\/author\/iancschafer\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Defining software quality metrics for Agile and DevOps - SD Times","description":"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands","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:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/","og_locale":"en_US","og_type":"article","og_title":"Defining software quality metrics for Agile and DevOps - SD Times","og_description":"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands","og_url":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/","og_site_name":"SD Times","article_publisher":"https:\/\/www.facebook.com\/SDTimesD2","article_published_time":"2018-10-04T13:57:31+00:00","og_image":[{"width":660,"height":371,"url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg","type":"image\/jpeg"}],"author":"Ian C. Schafer","twitter_card":"summary_large_image","twitter_creator":"@iancsc","twitter_site":"@sdtimes","twitter_misc":{"Written by":"Ian C. Schafer","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#article","isPartOf":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/"},"author":{"name":"Ian C. Schafer","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/9022c63a7e3a542f7a9df8385ad5fd3f"},"headline":"Defining software quality metrics for Agile and DevOps","datePublished":"2018-10-04T13:57:31+00:00","dateModified":"2018-10-04T13:57:31+00:00","mainEntityOfPage":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/"},"wordCount":1214,"publisher":{"@id":"https:\/\/sdtimes.com\/#organization"},"image":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg","keywords":["agile","DevOps","Forrester","metrics","software quality","Tricentis"],"articleSection":["Latest News"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/","url":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/","name":"Defining software quality metrics for Agile and DevOps - SD Times","isPartOf":{"@id":"https:\/\/sdtimes.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage"},"image":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg","datePublished":"2018-10-04T13:57:31+00:00","dateModified":"2018-10-04T13:57:31+00:00","description":"Measuring success in Agile and DevOps is shifting from \u2018counting\u2019 metrics, such as number of tests run, to \u2018contextual\u2019 metrics, which can show if the software is meeting requirements and user demands","breadcrumb":{"@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#primaryimage","url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg","contentUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2018\/10\/metrics-1.jpg","width":660,"height":371},{"@type":"BreadcrumbList","@id":"https:\/\/sdtimes.com\/devops\/defining-software-quality-metrics-for-agile-and-devops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sdtimes.com\/"},{"@type":"ListItem","position":2,"name":"Defining software quality metrics for Agile and DevOps"}]},{"@type":"WebSite","@id":"https:\/\/sdtimes.com\/#website","url":"https:\/\/sdtimes.com\/","name":"SD Times","description":"Software Development News","publisher":{"@id":"https:\/\/sdtimes.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sdtimes.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/sdtimes.com\/#organization","name":"SD Times","url":"https:\/\/sdtimes.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/","url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png","contentUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png","width":225,"height":90,"caption":"SD Times"},"image":{"@id":"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/SDTimesD2","https:\/\/x.com\/sdtimes","https:\/\/www.linkedin.com\/company\/sdtimes\/"]},{"@type":"Person","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/9022c63a7e3a542f7a9df8385ad5fd3f","name":"Ian C. Schafer","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/image\/d2379e9eeb891a65bb56e82be996e74d","url":"https:\/\/secure.gravatar.com\/avatar\/af176b4e562bd686310678b2fa6c6011?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/af176b4e562bd686310678b2fa6c6011?s=96&d=mm&r=g","caption":"Ian C. Schafer"},"description":"Ian C. Schafer is a multimedia reporter and undeniable nerd living and working in New York City and on Long Island.","sameAs":["http:\/\/iancschafer.com","https:\/\/x.com\/iancsc"],"url":"https:\/\/sdtimes.com\/author\/iancschafer\/"}]}},"_links":{"self":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/32600"}],"collection":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/users\/738"}],"replies":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/comments?post=32600"}],"version-history":[{"count":2,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/32600\/revisions"}],"predecessor-version":[{"id":32604,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/32600\/revisions\/32604"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media\/32602"}],"wp:attachment":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media?parent=32600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/categories?post=32600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/tags?post=32600"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/coauthors?post=32600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}