{"version":"1.0","provider_name":"E5","provider_url":"https:\/\/e5.ua\/en\/","title":"Myths about Scaled Agile Framework","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"OtYhJP25WM\"><a href=\"https:\/\/e5.ua\/en\/blogpost-2-en\/mify-o-scaled-agile-framework\/\">Myths about Scaled Agile Framework<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/e5.ua\/en\/blogpost-2-en\/mify-o-scaled-agile-framework\/embed\/#?secret=OtYhJP25WM\" width=\"600\" height=\"338\" title=\"&#8220;Myths about Scaled Agile Framework&#8221; &#8212; E5\" data-secret=\"OtYhJP25WM\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script type=\"text\/javascript\">\n\/* <![CDATA[ *\/\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/* ]]> *\/\n<\/script>\n","thumbnail_url":"https:\/\/e5.ua\/wp-content\/uploads\/2020\/05\/myth-reality-1024x683.jpg","thumbnail_width":1024,"thumbnail_height":683,"description":"Author: Helen Lubchak SAFe (Scaled Agile Framework) is the most popular scaling agile framework, which has been confirmed by the research conducted by the leading companies of the years 2017 \u2013 2019. And yet we still hear a lot of myths related to the framework which we would like to debunk, shall we? Myth # 1: It is an overly difficult framework SAFe is a construction kit with 4 configurations easily adapted to a variety of companies, products, and projects. If you have a relatively small team (e.g., 50+ people), you should consider Essential SAFe consisting of two levels, with one of which you are already familiar, namely, the teams\u2019 level. And if you have thousands of people, it makes sense to get acquainted with Full SAFe (to operate budgets, organize flows of business idea validation, etc.) or with Large Solution (if you face only the organizational part of business without getting too much into its business one). However, if there are up to 125 people and you need to organize budgets, validation of hypotheses, etc., then you should consider Portfolio SAFe. Myth # 2: SAFe is solely for an Enterprise Undoubtedly, when you see such giants using SAFe as SONY, KLM, HP, Intel, and the like, you immediately feel that the framework itself is monstrous and hard as if having been built specifically for them. Not quite \ud83d\ude0a Due to its flexibility and a particular approach to the framework as to a construction kit, it is as suitable for &hellip; Continued"}