Scaled agile framework: Difference between revisions

Revision as of 12:53, 10 February 2023

Revision as of 04:00, 12 February 2023

Line 29:

{{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 SAFe.

=== Full SaFE Implementation ===

Scaling SaFE across an organization to achieve Full Business Agility may be impractical. Upward scaling can only extend as far as Agile Team leads and Business Owners are able to make Value Stream Management (VSM) decisions at the Portfolio Configuration. SaFE includes a Value Stream Manager role that can be utilized by solutions teams and Business Owners to create a cohesive layer, while acknowledging its limitations: "A single Value Stream Manager may suffice for small, independent value streams; however, it is unlikely that any individual possesses all the necessary characteristics at scale.<ref>{{Cite"https://www.scaledagileframework.com/value-stream-management-in-safe/</ref>

==Implementation==