{"id":26772,"date":"2017-08-23T15:27:27","date_gmt":"2017-08-23T19:27:27","guid":{"rendered":"https:\/\/sdtimes.com\/?p=26772"},"modified":"2018-12-07T09:49:49","modified_gmt":"2018-12-07T14:49:49","slug":"scaling-agile","status":"publish","type":"post","link":"https:\/\/sdtimes.com\/agile\/scaling-agile\/","title":{"rendered":"Scaling Agile"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">The concepts of <a href=\"https:\/\/sdtimes.com\/tag\/agile\/\">Agile software development<\/a> are well understood, more than a decade after the original manifesto was put to paper. It calls for things such as \u201cpeople over process\u201d and \u201cresponding to change over following a plan.\u201d <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Of course, the devil is in the details, and companies are hitting a wall in trying to implement Agile, especially when they look to infuse Agile beyond their development organizations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Part of the reason is that Agile is not prescriptive. It provides a broad framework, but there is no map to follow, and organizations are developing their own processes to achieve the Agile goal of delivering software more quickly, of higher quality, and that meets the requirements of the user.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Also, it was originally designed as an approach to developing software. Now, the \u201cAgile enterprise\u201d is the goal. Why should only software development move quickly? Why can\u2019t marketing, and sales, and business decisions, be made in a more Agile fashion.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They can, of course, but again, the devil is in the details. There are challenges in organizational leadership, in allowing teams to find their rhythms and then coming together at critical junctures and in using metrics to guide the business.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cAgile is front and center for everyone trying to make a digital transformation,\u201d said Steve Elliot, CEO of AgileCraft, makers of a scaled Agile management platform. \u201cBut running an Agile mindset across groups of teams is the challenge.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And therein lies perhaps the greatest challenge to achieving business agility. Few organizations are starting from scratch; most have development teams doing Agile projects and creating versions of software faster than release teams, marketing and sales teams, and even business decision-makers can keep up. \u201cThe agile methodology has been so successful that development teams are pushing code more quickly than IT can deal with,\u201d said Anders Wallgren, CTO at Electric Cloud, a DevOps release automation software provider.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Some of this is due to the fact that whether most organizations embrace it or not, they are all becoming software companies. Pizza sellers want to be platform players. Automobile manufacturers use more software in their cars than ever before; mechanics are transforming from \u2018grease monkeys\u2019 to debuggers. \u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And a lot of companies piloted Agile in software projects, and found that it works. But they never had a strategy to scale it throughout the enterprise, said, Sally Elatta, president of Agile Transformations Inc. and founder of Agility Health. \u201cThey never realized the organizational impact Agile would have. It was a bottom-up movement.\u201d<\/span><\/p>\n<p><strong>Making the digital transformation<br \/>\n<\/strong><span style=\"font-weight: 400;\">\u201cThe essence of Agile is adaption and change,\u201d noted Boris Chen, co-founder and vice president of engineering at tCell.io, a company focused on real-time application security for DevOps. \u201cBut there are friction points if you can\u2019t get all parts of the organization up to the same speed.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cIt\u2019s almost like when mobile came along,\u201d said AgileCraft\u2019s Elliot. \u201cCompanies struggled to adapt. The ability to deal with changes in technology is critical to success.\u201d Today, he said, organizations must conceive of a technology strategy \u2013 in this case, with the goal of business agility \u2013 and trace it down to deployment. \u201cThere has to be one view of the world,\u201d he said.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Smart companies making the change understand that an Agile enterprise is more than having individual teams doing Agile. \u201cThat,\u201d said Robert Holler, former CEO of agile project management software provider VersionOne and newly minted chief strategy officer at development tools maker CollabNet, \u201ccan create a tribal scenario where each team sets its own practices and tooling. That doesn\u2019t scale very well. Organizations need to take a systems thinking approach, make decisions about improving and optimizing the whole system, not just the pieces. Lots of organizations are still wrapped up in tribal agile, and they\u2019re not getting the full benefit. They\u2019re not working for the benefit of the whole.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s difficult to get teams working at the same speed, and Holler said it\u2019s fine if they don\u2019t. \u201cIt\u2019s OK for teams to work at different cadences, but ultimately they have to align,\u201d he said. Holler went on to say that organizations might be doing continuous delivery internally, creating software that is deployable every day but not necessarily deployed. Meanwhile the business is operating on a quarterly or annual cadence. \u201cSo you have to come together on monthly, quarterly and annual cycles. When the month rolls around, the organization has to operate on that meta-cadence,\u201d he said, coining a new term.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Because the development group is working at a faster cadence than other teams, challenges lie in understanding when to pull PR and marketing, for example, in to discuss work being done in development. \u201cThere are different levels of releases,\u201d said Shannon Mason, vice president of product management for CA Agile Central. \u201cThere are minor tweaks, changes. With the big paradigm-shifting things, you can get them out and hide them, then educate the field teams by turning it on for them. You can turn it on in pieces.\u201d <\/span><\/p>\n<p><span style=\"font-weight: 400;\">tCells\u2019 Chen suggests integrating marketing into some developer meetings, perhaps weekly, \u201cso they can understand what\u2019s delivered and what is coming.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In the days of waterfall, teams would create requirements (with marketing and business input) for development, and after the 12-month development life cycle was complete, marketing would have the list of new features to promote. But in today\u2019s world, since there is the notion that software is never done but simply improved iteratively, you need to break work down into increments of value, Mason said. \u201cWhat\u2019s the value proposition? Who are you targeting? What defines a \u2018win\u2019? If the uptake is good, the feedback is positive and the tech is solid, then we determine something is done.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">But the work has to be done at a sustainable pace, offered Ronica Roth, CA agility services advisor and team lead. \u201cThere\u2019s a heartbeat and rhythm\u201d to work, she said. \u201cI don\u2019t turn my heart off at the end of the day because it did a good job. But I don\u2019t run 24 hours a day either because I\u2019d fall dead.\u201d Organizations, she said, need cadences and rhythms, just as people mark days, weeks and seasons. \u201cWhen an organization has a set of rhythms that work together, that\u2019s business agility.\u201d<\/span><\/p>\n<p><strong>Leadership is critical<br \/>\n<\/strong><span style=\"font-weight: 400;\">One of the biggest hurdles to scaling Agile across the enterprise and achieving business agility is a lack of business leadership experience in Agile processes. Pizza sellers never had to deal with Agile practices before. \u201cYou can teach people how to do Scrum in five seconds. It\u2019s completely logical. But you don\u2019t put a kid in pre-K and say, \u2018We\u2019ll see you in 12 years. They need continued instruction and training,\u201d said Mason. \u201cThe people are the hard part. Getting people over their own egos and long-held beliefs, especially in leadership, is the real challenge.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">One of the reasons cited for a void in leadership is that training and education are \u201cnotoriously underfunded,\u201d said CollabNet\u2019s Holler. \u201cOrganizations say \u2018Everyone\u2019s doing agile, so let\u2019s do agile.\u201d But Holler said making a digital transformation for business agility is a change management process. \u201cTraining, education, centers of excellence are required for positive outcomes. Large organizations have lots of inertia.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Programs have become more agile, but not the enterprise. Budgeting, for instance, \u201cand the way organizations think about budget, is antiquated,\u201d said AgileCraft\u2019s Elliot. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">In short, leadership has to change, as the role of an Agile manager is \u201cchanging in a huge way,\u201d said Agile Transformations\u2019 Elatta. \u201cThe role is more strategic and less tactical. They must remove organizational obstacles, form and support communities of practice. It\u2019s a big deal.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Elatta noted that organizations \u201chaven\u2019t invested in these people. They\u2019ve forgotten about the middle management layer.\u201d<\/span><\/p>\n<p><strong>Using metrics<br \/>\n<\/strong>For organizations to get to business agility, they need to measure what matters most to them, and to know if their investment in people and process is bring a desired return on investment. Without metrics, \u201cyou can\u2019t tell if you\u2019re faster, cheaper, better and healthier\u201d with Agile, Elatta said. \u201cYou need continuous measurement for growth. Measure where you are today, gain consensus of where you want to go, then measure again. This cycle is critical.\u201d<\/p>\n<p><span style=\"font-weight: 400;\">CA\u2019s Mason pointed out that organizations collect massive amounts of data from their software that can be used \u201cto save them from creating bad plans. We look at our data and see patterns from a human perspective. Envisioning what a product will look like 12 months from now is like looking for something that isn\u2019t there. Knowing yourself a week from now is easier than knowing yourself a year from now.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Businesses are looking to extend agility across their entire value stream, said CollabNet\u2019s Holler. Data helps organizations deliver the products their customers want. \u201cWhen your value stream is optimized, how do you optimize the feedback loop? Faster feedback can totally transform your business. It\u2019s nirvana for Agile.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Electric Cloud\u2019s Wallgren echoed that sentiment. \u201cContinuous improvement requires data,\u201d he said, providing insights into release frequency, failure rates, user experiences and much more. \u201cWe ought to be doing more monitoring before production. If nothing else, you learn what a properly operating system looks like.\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>The concepts of Agile software development are well understood, more than a decade after the original manifesto was put to paper. It calls for things such as \u201cpeople over process\u201d and \u201cresponding to change over following a plan.\u201d Of course, the devil is in the details, and companies are hitting a wall in trying to  &hellip; <a class=\"read-more\" href=\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\">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":205,"featured_media":26773,"comment_status":"open","ping_status":"open","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":[2439,1],"tags":[132,11476,1141],"coauthors":[11448],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Scaling Agile - SD Times<\/title>\n<meta name=\"description\" content=\"Enterprises need to let teams find their own rhythms, but come together at critical junctures.\" \/>\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\/agile\/scaling-agile\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scaling Agile - SD Times\" \/>\n<meta property=\"og:description\" content=\"Enterprises need to let teams find their own rhythms, but come together at critical junctures.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\" \/>\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=\"2017-08-23T19:27:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-12-07T14:49:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"1132\" \/>\n\t<meta property=\"og:image:height\" content=\"750\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"David Rubinstein\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@sdtimes\" \/>\n<meta name=\"twitter:site\" content=\"@sdtimes\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Rubinstein\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\"},\"author\":{\"name\":\"David Rubinstein\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/c5979508a52529c65d558ca23cb64a4a\"},\"headline\":\"Scaling Agile\",\"datePublished\":\"2017-08-23T19:27:27+00:00\",\"dateModified\":\"2018-12-07T14:49:49+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\"},\"wordCount\":1553,\"commentCount\":7,\"publisher\":{\"@id\":\"https:\/\/sdtimes.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg\",\"keywords\":[\"agile\",\"agile software\",\"software development\"],\"articleSection\":[\"Column\",\"Latest News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\",\"url\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\",\"name\":\"Scaling Agile - SD Times\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg\",\"datePublished\":\"2017-08-23T19:27:27+00:00\",\"dateModified\":\"2018-12-07T14:49:49+00:00\",\"description\":\"Enterprises need to let teams find their own rhythms, but come together at critical junctures.\",\"breadcrumb\":{\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sdtimes.com\/agile\/scaling-agile\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage\",\"url\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg\",\"contentUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg\",\"width\":1132,\"height\":750},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sdtimes.com\/agile\/scaling-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sdtimes.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scaling Agile\"}]},{\"@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\/c5979508a52529c65d558ca23cb64a4a\",\"name\":\"David Rubinstein\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/image\/efe807ec0a4a29a22c1ba89dd5689fe2\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1b3fdab44b2a65d11f93bdc301690be3?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1b3fdab44b2a65d11f93bdc301690be3?s=96&d=mm&r=g\",\"caption\":\"David Rubinstein\"},\"description\":\"David Rubinstein is editor-in-chief of SD Times.\",\"url\":\"https:\/\/sdtimes.com\/author\/david-rubinstein\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scaling Agile - SD Times","description":"Enterprises need to let teams find their own rhythms, but come together at critical junctures.","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\/agile\/scaling-agile\/","og_locale":"en_US","og_type":"article","og_title":"Scaling Agile - SD Times","og_description":"Enterprises need to let teams find their own rhythms, but come together at critical junctures.","og_url":"https:\/\/sdtimes.com\/agile\/scaling-agile\/","og_site_name":"SD Times","article_publisher":"https:\/\/www.facebook.com\/SDTimesD2","article_published_time":"2017-08-23T19:27:27+00:00","article_modified_time":"2018-12-07T14:49:49+00:00","og_image":[{"width":1132,"height":750,"url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg","type":"image\/jpeg"}],"author":"David Rubinstein","twitter_card":"summary_large_image","twitter_creator":"@sdtimes","twitter_site":"@sdtimes","twitter_misc":{"Written by":"David Rubinstein","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#article","isPartOf":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/"},"author":{"name":"David Rubinstein","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/c5979508a52529c65d558ca23cb64a4a"},"headline":"Scaling Agile","datePublished":"2017-08-23T19:27:27+00:00","dateModified":"2018-12-07T14:49:49+00:00","mainEntityOfPage":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/"},"wordCount":1553,"commentCount":7,"publisher":{"@id":"https:\/\/sdtimes.com\/#organization"},"image":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg","keywords":["agile","agile software","software development"],"articleSection":["Column","Latest News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/sdtimes.com\/agile\/scaling-agile\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/","url":"https:\/\/sdtimes.com\/agile\/scaling-agile\/","name":"Scaling Agile - SD Times","isPartOf":{"@id":"https:\/\/sdtimes.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage"},"image":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg","datePublished":"2017-08-23T19:27:27+00:00","dateModified":"2018-12-07T14:49:49+00:00","description":"Enterprises need to let teams find their own rhythms, but come together at critical junctures.","breadcrumb":{"@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sdtimes.com\/agile\/scaling-agile\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#primaryimage","url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg","contentUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2017\/08\/pexels-photo-357891.jpeg","width":1132,"height":750},{"@type":"BreadcrumbList","@id":"https:\/\/sdtimes.com\/agile\/scaling-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sdtimes.com\/"},{"@type":"ListItem","position":2,"name":"Scaling Agile"}]},{"@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\/c5979508a52529c65d558ca23cb64a4a","name":"David Rubinstein","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/image\/efe807ec0a4a29a22c1ba89dd5689fe2","url":"https:\/\/secure.gravatar.com\/avatar\/1b3fdab44b2a65d11f93bdc301690be3?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1b3fdab44b2a65d11f93bdc301690be3?s=96&d=mm&r=g","caption":"David Rubinstein"},"description":"David Rubinstein is editor-in-chief of SD Times.","url":"https:\/\/sdtimes.com\/author\/david-rubinstein\/"}]}},"_links":{"self":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/26772"}],"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\/205"}],"replies":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/comments?post=26772"}],"version-history":[{"count":2,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/26772\/revisions"}],"predecessor-version":[{"id":33547,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/26772\/revisions\/33547"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media\/26773"}],"wp:attachment":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media?parent=26772"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/categories?post=26772"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/tags?post=26772"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/coauthors?post=26772"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}