Scaled agile framework

The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices.[1][2] Along with disciplined agile delivery (DAD), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.[3][4]

Part of a series on
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and bodies of knowledge
Glossaries
Outlines

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, and systems thinking.[5]

The primary reference for the scaled agile framework was originally the development of a big picture view of how work flowed from product management (or other stakeholders), through governance, program, and development teams, out to customers.[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],[13] it also has received criticism for being too hierarchical and inflexible.[14] It also receives criticism for giving organizations the illusion of adopting Agile, while keeping familiar processes intact.[15]

Challenges of scaling agile principles and practices

Coping with longer planning horizons

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. The development teams will still get into detailed refinement 2-3 iterations ahead, only getting into detailed task plans for the next iteration.

Keeping agile at abstract levels of responsibility

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).

Dealing with delegated authority

In Scrum, the product owner is expected to assume responsibility for the full product life-cycle, including the return 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 a product 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]

Synchronizing deliverables

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]

Allowing time for innovation and planning

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 a hardening 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.

Implementation

Underlying principles of SAFe

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]

  1. Take an economic view
  2. Apply systems thinking
  3. Assume variability; preserve options
  4. Build incrementally with fast integrated learning cycles
  5. Base milestones on objective evaluation of working systems
  6. Visualize and limit work-in-progress, reduce batch sizes, and manage queue lengths
  7. Apply cadence (timing), synchronize with cross-domain planning
  8. Unlock the intrinsic motivation of knowledge workers
  9. Decentralize decision-making
  10. Organize around value

SAFe has been criticized for aggregating too many disparate practices.[22]

The SAFe framework

In SAFe version 5.1, there are four configurations: essential, portfolio, large solution and full:[23]

  • Essential SAFe is the most basic configuration. It describes the most critical elements needed and is intended to provide the majority of the framework's benefits. It includes the team and program level (which it calls agile release trains or ARTs).
  • Large Solution SAFe allows for coordination and synchronization across multiple programs, but without the portfolio considerations. In earlier versions of SAFe, this level was referred to as value stream.
  • Portfolio SAFe includes concerns for strategic direction, investment funding, and lean governance.
  • Full SAFe combines the other three levels.

Certifications

Scaled Agile provides certifications that cover different areas and knowledge levels.[24]

See also

References
  1. Hayes, Will; Lapham, Mary Ann; Miller, Suzanne; Wrubel, Eileen; Capell, Peter (2016). Scaling Agile Methods for Department of Defense Programs. Software Engineering Institute. CMU/SEI-2016-TN-005.
  2. Athrow, Desiree (29 January 2015). "Why Continuous Delivery is key to speeding up software development". TechRadar. Retrieved 2017-11-27.
  3. Linders, Ben (January 22, 2015). "Scaling Agile with the Disciplined Agile Delivery Framework". InfoQ. Retrieved 2017-11-27.
  4. van Haaster, K (2014). Agile in-the-large: Getting from Paradox to Paradigm. Unpublished paper from Charles Sturt University.
  5. King, Michael (2017). "Serving Federal Customers with SAFe Concepts" (PDF). Capability Counts Conference Proceedings.
  6. Bridgwater, Adrian (August 7, 2013). "Real Agile Means Everybody Is Agile". Dr. Dobb's. Retrieved 2017-11-27.
  7. Linders, Ben (August 28, 2014). "Death by Planning in Agile Adoption". InfoQ. Retrieved 2017-11-27.
  8. Leffingwell, Dean (2007). Scaling Software Agility: Best Practices for Large Enterprises. Addison-Wesley. ISBN 978-0321458193.
  9. "About Scaled Agile Framework - A Brief History of SAFe". Scaled Agile Inc. Retrieved 12 August 2020.
  10. "Say Hello to SAFE 6.0". Scaled Agile Inc. Retrieved 2023-03-16.
  11. "13th Annual State of Agile Report". State of Agile Survey. CollabNet VersionOne. 2019. Retrieved 2019-08-27.
  12. Link, P; Lewrick, M (29 September 2014). "Agile Methods in a New Area of Innovation Management" (PDF). Science to Business Marketing Conference.
  13. Baptista, Roberto (28 January 2015). "Profissionais brasileiros e o interesse por treinamentos de especialização". Computerworld Brazil. Retrieved 28 January 2015.
  14. Schwaber, Ken (2013-08-06). "unSAFe at any speed". Telling It Like It Is. Retrieved 2017-11-11.
  15. Gothelf, Jeff (2021-10-05). "SAFe is not Agile". Retrieved 2023-05-21.
  16. Eklund, U; Olsson, H; Strøm, N (2014). Industrial challenges of scaling agile in mass-produced embedded systems. ISBN 9783319143583. {{cite book}}: |work= ignored (help)
  17. Vaidya, A (2014). Does DAD Know Best, Is it Better to do LeSS or Just be SAFe? Adapting Scaling Agile Practices into the Enterprise. Excerpt from PNSQC 2014 Proceedings. pp. 8–9.
  18. Maximini, Dominik (11 September 2013). "A critical view on SAFe - Scrumorakel - Blog". Scrum Oracle. Retrieved 2017-11-27.
  19. Stafford, Jan (December 9, 2013). "Scaling Agile development calls for defined practices, consultant says". SearchSoftwareQuality. Retrieved 2017-11-27.
  20. Killick, Neil (21 March 2012). "The Horror Of The Scaled Agile Framework". Agile, Scrum, Kanban, Lean, and everything that's in between. Retrieved 2017-11-27.
  21. "SAFe Lean-Agile Principles". Retrieved 19 February 2016.
  22. Elssamadisy, Amr. "Has SAFe Cracked the Large Agile Adoption Nut?". InfoQ. Retrieved 2017-11-11.
  23. Rose, Doug (2018). Enterprise Agility For Dummies. John Wiley & Sons. pp. 87–89. ISBN 9781119446095.
  24. "Certification". Scaled Agile. Retrieved 19 February 2016.

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.