Content deleted Content added
Marked a dead link |
m Dating maintenance tags: {{Cn}} |
||
Line 15:
=== Coping with longer planning horizons ===
Development teams typically refine their backlog up to two to three iterations ahead, but in larger organizations the product marketing team needs to plan further ahead for their commitments to market and discussions with customers.<ref>{{Cite book|title=Industrial challenges of scaling agile in mass-produced embedded systems.|last1=Eklund|first1=U|last2=Olsson|first2=H|last3=Strøm|first3=N|work=Agile Methods. Large-Scale Development, Refactoring, Testing, and Estimation|publisher=Springer International Publishing|year=2014|isbn=9783319143583}}</ref> They will often work with a very high level, 12 to 18-month roadmap, then plan collaboratively with the teams for three months of work.{{cn|date=September 2022}} The development teams will still get into detailed refinement 2-3 iterations ahead, only getting into detailed task plans for the next iteration.{{cn|date=September 2022}}
=== 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).{{cn|date=September 2022}}
=== Dealing with delegated authority ===
| |||