The primary ambition of the Scaled Agile Framework is to take the Agile principles to be effective at the enterprise level.
We have already seen several approaches to utilizing hierarchy in using the Agile methodology at the team level. This framework takes the hierarchy, from a team or a project level, to program and portfolio levels, and recognizes the need for non-functional requirements (NFRs), in addition to the user stories that a user would definitely interact with, and recognizes business epics and architectural epics.
|Meetup on 19 March 2013.|
At the team level, you may have 2- or 3-week sprints; a release may occur at a Potentially Shippable Increment (PSI) comprising of work amounting to several sprints; at the portfolio level, there may be a need to synchronize of releases of several products.
|Scaled Agile Framework™.|
And, if you believe that organizing the enterprise-level needs to be driven hierarchically, you wonder why anyone would not want adopt a framework such as SAF.