| Part of a series on |
| Software development |
|---|
Paradigms and models |
Standards and bodies of knowledge |
Thescaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises inscalinglean andagile practices.[1][2] Along withdisciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.[3][4]
SAFe promotes alignment, collaboration, and delivery across large numbers of agile teams. It was developed by and for practitioners, by leveraging three primary bodies of knowledge:agile software development,lean product development, andsystems thinking.[5]
The primary reference for the scaled agile framework was originally the development of abig picture view of how work flowed fromproduct management (or otherstakeholders), throughgovernance,program, anddevelopment teams, out tocustomers.[6][7] With the collaboration of others in the agile community, this was progressively refined and then first formally described in a 2007 book.[8] The framework continues to be developed and shared publicly; with an academy and an accreditation scheme supporting those who seek to implement, support, or train others in the adoption of SAFe.
Starting at its first release in 2011, six major versions have been released[9] while the latest edition, version 6.0, was released in March 2023.[10]
While SAFe continues to be recognised as the most common approach to scaling agile practices (at 30 percent and growing),[11][12][page needed],[13] it also has received criticism for being toohierarchical and inflexible.[14] It also receives criticism for giving organizations the illusion of adoptingAgile, while keeping familiar processes intact.[15]
Development teams typically refine their backlog up to two to three iterations ahead, but in larger organizations the product marketing team needs to plan further ahead for their commitments to market and discussions with customers.[16] They will often work with a very high level, 12 to 18-month roadmap, then plan collaboratively with the teams for three months of work.[citation needed] The development teams will still get into detailed refinement 2–3 iterations ahead, only getting into detailed task plans for the next iteration.[citation needed]
While development teams have a number of frameworks that define how they should be agile, there is very little that describes this for management. SAFe delivers many of the same principles, such as cross-functional teams, to the groups that handle the more abstract levels of responsibility and planning (product and portfolio).[citation needed]
InScrum, the product owner is expected to assume responsibility for the fullproduct life-cycle, including thereturn on investment of development decisions, as well as performance in market. On large-scale developments, the organization wants a view across multiple team backlogs, such as provided by aproduct manager.[17] Although SAFe assumes the product owner role sits with product management, it has nonetheless been criticized for separating product owners into the development organization.[18]
Agile frameworks are designed to enable the development team to be autonomous and free to design how they work. SAFe acknowledges that, at the scale of many tens or hundreds of development teams, it becomes increasingly chaotic for teams to fully self-organize.[19] It therefore puts some constraints on this, so that where teams are working on the same product, their deliverables can be better synchronized for releasing together, although this has been one area in which SAFe has been criticized.[17][18]
 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Scaled agile framework" – news ·newspapers ·books ·scholar ·JSTOR(September 2022) (Learn how and when to remove this message) |
The SAFe planning cycle recommends including an additional iteration after a release, allowing teams to improve their practices and are ready for the next planning increment. Earlier editions of SAFe also designed this to be ahardening iteration, namely to stabilize or harden the product before releasing it. This was predicated on the complications of working with large integration environments where dependencies prevented several matters from being tested until the very end. SAFe was criticized for this because it represented an anti-agile or waterfall element, but was in line with lean 90-day increments which make 13 weeks, and if doing two-week sprints you need six of them plus a one-week planning or hardening cycle.[20] This is not included in recent editions of SAFe.
| This sectionmay rely excessively on sourcestoo closely associated with the subject, potentially preventing the article from beingverifiable andneutral. Please helpimprove it by replacing them with more appropriatecitations toreliable, independent sources.(July 2018) (Learn how and when to remove this message) |
According to its authors, SAFe is based upon ten underlying concepts, which are derived from existing lean and agile principles, as well as observation:[21]
SAFe has been criticized for aggregating too many disparate practices.[22]
In SAFe version 5.1, there are four configurations: essential, portfolio, large solution and full:[23]
Scaled Agile providescertifications that cover different areas and knowledge levels.[24]
{{cite book}}:|work= ignored (help)