Scaled agile framework: Difference between revisions

Revision as of 12:09, 21 May 2024

Revision as of 12:10, 21 May 2024

Line 28:

=== Allowing time for innovation and planning ===

{{More citations needed|date=September 2022}}

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.<ref>{{Cite news|url=https://neilkillick.wordpress.com/2012/03/21/the-horror-of-the-scaled-agile-framework/|title=The Horror Of The Scaled Agile Framework|last=Killick|first=Neil|date=21 March 2012|work=Agile, Scrum, Kanban, Lean, and everything that's in between|access-date=2017-11-27}}</ref> This is not included in recent editions of [https://scholaracad.com/article/safe-agilist-vs-safe-scrum-master-understanding-the-distinct-roles-in-agile-frameworks SAFe].

==Implementation==

Line 45:

#[[Decentralization|Decentralize]] decision-making

# Organize around value

SAFe is very useful for Agile way of working. It focus on organizational-level improvement in Agile way.

<ref>https://scholaracad.com/article/safe-agilist-vs-safe-scrum-master-understanding-the-distinct-roles-in-agile-frameworks</ref>

SAFe has been criticized for aggregating too many disparate practices.<ref>{{Cite web|url=https://www.infoq.com/news/2013/08/safe|title=Has SAFe Cracked the Large Agile Adoption Nut?|last=Elssamadisy|first=Amr|website=InfoQ|access-date=2017-11-11}}</ref>