Content deleted Content added
GreenC bot (talk | contribs) Rescued 1 archive link. Wayback Medic 2.5 per Category:All articles with dead external links - pass 3 |
Citation bot (talk | contribs) Added date. | Use this bot. Report bugs. | Suggested by Abductive | Category:Software development philosophies | #UCB_Category 13/39 |
||
| (One intermediate revision by one other user not shown) | |||
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, six 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 6.0, was released in March 2023.<ref>{{Cite web|url=https://scaledagileframework.com/blog/say-hello-to-safe-6-0/|title=Say Hello to SAFE 6.0|date=15 March 2023 |publisher=Scaled Agile Inc|access-date=2023-03-16}}</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> It also receives criticism for giving organizations the illusion of adopting [[Agile software development|Agile]], while keeping familiar processes intact.<ref>{{Cite news|url=https://jeffgothelf.com/blog/safe-is-not-agile/|title=SAFe is not Agile|last=Gothelf|first=Jeff|author-link=Jeff Gothelf|date=2021-10-05|access-date=2023-05-21}}</ref>
Line 15:
=== 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.<ref>{{Cite book|title=Industrial challenges of scaling agile in mass-produced embedded systems.|last1=Eklund|first1=U|last2=Olsson|first2=H|last3=Strøm|first3=N|work=Agile Methods. Large-Scale Development, Refactoring, Testing, and Estimation|publisher=Springer International Publishing|year=2014|isbn=9783319143583}}</ref> 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.{{cn|date=September 2022}} The development teams will still get into detailed refinement
=== Keeping agile at abstract levels of responsibility ===
| |||