Content deleted Content added
Citation doesn't say anything about "development teams will still get into detailed refinement 2-3 iterations ahead", replaced with citation needed |
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. |
||
Line 18:
=== Keeping agile at abstract levels of responsibility ===
While development teams have a number of frameworks that define how they should be agile, there is very little that describes this for management. SAFe delivers many of the same principles, such as cross-functional teams, to the groups that handle the more abstract levels of responsibility and planning (product and portfolio).
=== Dealing with delegated authority ===
Line 44:
#[[Decentralization|Decentralize]] decision-making
# Organize around value
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>
=== The SAFe framework ===
| |||