Scaled agile framework: Difference between revisions

Revision as of 12:50, 19 September 2022

Revision as of 13:02, 19 September 2022

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.<ref>{{Cite news|url=http://searchsoftwarequality.techtarget.com/tip/Agile-testing-methods-for-multiple-teams|title=Agile testing methods for multiple teams|last=Heusser|first=Matt|date=23 September 2014|work=SearchSoftwareQuality|access-date=2017-11-27cn}}</ref> The development teams will still get into detailed refinement 2-3 iterations ahead, only getting into detailed task plans for the next iteration.<ref>{{Cite journal|last1=Stettina|first1=C|last2=Horz|first2=J|year=2015|title=Agile portfolio management: An empirical perspective on the practice in use|journal=International Journal of Project Management|volume=33 |issue=1|pages=140–152|doi=10.1016/j.ijproman.2014.03.008}}</ref>

=== Keeping agile at abstract levels of responsibility ===