Content deleted Content added
m Open access bot: arxiv updated in citation with #oabot. |
Gowtham819 (talk | contribs) m Updated the dead links to the right pdf Tag: Reverted |
||
Line 3:
The '''scaled agile framework''' ('''SAFe''') is a set of organization and workflow patterns intended to guide enterprises in [[Scaling of innovations|scaling]] [[Lean software development|lean]] and [[Agile software development|agile]] practices.<ref>{{Cite book|title=Scaling Agile Methods for Department of Defense Programs|last1=Hayes|first1=Will|last2=Lapham|first2=Mary Ann|last3=Miller|first3=Suzanne|last4=Wrubel|first4=Eileen|last5=Capell|first5=Peter|publisher=Software Engineering Institute|year=2016|id=CMU/SEI-2016-TN-005}}</ref><ref>{{Cite news|url=http://www.techradar.com/news/software/why-continuous-delivery-is-key-to-speeding-up-software-development-1282498|title=Why Continuous Delivery is key to speeding up software development|last=Athrow|first=Desiree|date=29 January 2015|work=TechRadar|access-date=2017-11-27}}</ref> Along with [[disciplined 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.<ref>{{Cite web|url=https://www.infoq.com/news/2015/01/disciplined-agile-delivery|title=Scaling Agile with the Disciplined Agile Delivery Framework|last=Linders|first=Ben|date=January 22, 2015|website=InfoQ|access-date=2017-11-27}}</ref><ref>{{Cite book|title=Agile in-the-large: Getting from Paradox to Paradigm|last=van Haaster|first=K|publisher=Unpublished paper from Charles Sturt University|year=2014}}</ref>
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]].<ref>{{Cite journal|last=King|first=Michael|year=2017|title=Serving Federal Customers with SAFe Concepts|url=
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.
| |||