Scaled agile framework: Difference between revisions

Revision as of 07:20, 21 February 2023

Revision as of 21:08, 16 March 2023

Line 7:

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 [[Project stakeholder|stakeholders]]), through [[Project governance|governance]], [[Program management|program]], and [[Software developer|development teams]], out to [[customer]]s.<ref>{{Cite news|url=http://www.drdobbs.com/tools/real-agile-means-everybody-is-agile/240159622|title=Real Agile Means Everybody Is Agile|last=Bridgwater|first=Adrian|date=August 7, 2013|work=Dr. Dobb's|access-date=2017-11-27}}</ref><ref>{{Cite web|url=https://www.infoq.com/news/2014/08/death-by-planning-agile|title=Death by Planning in Agile Adoption|last=Linders|first=Ben|date=August 28, 2014|website=InfoQ|access-date=2017-11-27}}</ref> With the collaboration of others in the agile community, this was progressively refined and then first formally described in a 2007 book.<ref>{{Cite book|title=Scaling Software Agility: Best Practices for Large Enterprises|last=Leffingwell|first=Dean|publisher=Addison-Wesley|year=2007|isbn=978-0321458193}}</ref> 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, fivesix major versions have been released<ref name="History of SAFe">{{cite web |title=About Scaled Agile Framework - A Brief History of SAFe |url=https://www.scaledagileframework.com/about/ |publisher=Scaled Agile Inc. |access-date=12 August 2020}}</ref> while the latest edition, version 56.10, was released in FebruaryMarch 20212023.<ref>{{Cite web|url=https://www.scaledagileframework.com/whatsblog/say-newhello-in-theto-safe-56-1-big-picture0/|title=What'sSay NewHello into theSAFE SAFe 56.1 Big Picture0|publisher=Scaled Agile Inc|access-date=20202023-0203-1016}}</ref>

While SAFe continues to be recognised as the most common approach to scaling agile practices (at 30 percent and growing),<ref>{{Cite web|url=https://www.stateofagile.com/#ufh-i-521251909-13th-annual-state-of-agile-report/473508|title=13th Annual State of Agile Report|date=2019|website=State of Agile Survey|publisher=CollabNet VersionOne|access-date=2019-08-27}}</ref><ref>{{cite journal|last1=Link|first1=P|last2=Lewrick|first2=M|date=29 September 2014|title=Agile Methods in a New Area of Innovation Management|url=http://www.brainguide.de/upload/publication/b0/2c3xg/c51b33fd2c6a9d032a7387f3273b9c62_1402133130.pdf|journal=Science to Business Marketing Conference}}</ref>{{page needed|date=April 2019}},<ref>{{cite web|url=http://computerworld.com.br/carreira/2015/01/28/profissionais-brasileiros-e-o-interesse-por-treinamentos-de-especializacao/|title=Profissionais brasileiros e o interesse por treinamentos de especialização|last=Baptista|first=Roberto|date=28 January 2015|publisher=Computerworld Brazil|access-date=28 January 2015}}</ref> it also has received criticism for being too [[Hierarchy|hierarchical]] and inflexible.<ref>{{Cite news|url=https://kenschwaber.wordpress.com/2013/08/06/unsafe-at-any-speed/|title=unSAFe at any speed|last=Schwaber|first=Ken|author-link=Ken Schwaber|date=2013-08-06|work=Telling It Like It Is|access-date=2017-11-11}}</ref>