Scaled agile framework: Difference between revisions

Content deleted Content added
Reverted 1 edit by Konsul28 (talk): Spam
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 |urllast=http://searchsoftwarequality.techtarget.com/answer/Scaling-Agile-development-calls-for-defined-practices-consultant-saysStafford |first=Jan |date=December 9, 2013 |title=Scaling Agile development calls for defined practices, consultant says |lasturl=Stafford|first=Jan|date=Decemberhttps://www.techtarget.com/searchsoftwarequality/definition/agile-software-development 9, 2013|work=SearchSoftwareQuality|access-date=2017-11-27}}{{dead link|datework=September 2022SearchSoftwareQuality}}</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 ===