Content deleted Content added
The citation is about proposing principles for Scaled Agile, it does not support that "SAFe delivers many of the same principles" and does not mention cross-functional teams. Replaced with citation needed. Also moved a criticism to a more suitable section. |
Marked a dead link |
||
Line 24:
=== Synchronizing deliverables ===
Agile frameworks are designed to enable the development team to be autonomous and free to design how they work. SAFe acknowledges that, at the scale of many tens or hundreds of development teams, it becomes increasingly chaotic for teams to fully self-organize.<ref name=":1">{{Cite news|url=http://searchsoftwarequality.techtarget.com/answer/Scaling-Agile-development-calls-for-defined-practices-consultant-says|title=Scaling Agile development calls for defined practices, consultant says|last=Stafford|first=Jan|date=December 9, 2013|work=SearchSoftwareQuality|access-date=2017-11-27}}{{dead link|date=September 2022}}</ref> It therefore puts some constraints on this, so that where teams are working on the same product, their deliverables can be better synchronized for releasing together, although this has been one area in which SAFe has been criticized.<ref name=":2" /><ref name=":3" />
=== 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 SAFe.
| |||