{"id":211,"date":"2014-07-08T14:52:32","date_gmt":"2014-07-08T13:52:32","guid":{"rendered":"http:\/\/www.tcc-net.com\/blog\/?p=211"},"modified":"2017-06-08T14:34:31","modified_gmt":"2017-06-08T14:34:31","slug":"scaled-agile-framework-scaling-scrum","status":"publish","type":"post","link":"https:\/\/www.tcc-net.com\/blog\/scaled-agile-framework-scaling-scrum\/","title":{"rendered":"Scaled Agile Framework (SAFe): Scaling Scrum to Enterprise Level"},"content":{"rendered":"

The benefits of using an Agile approach for delivering IT products and software are now well-established. The majority of organisations use the Scrum<\/a>\u00a0Agile approach, which is optimised for team-level working, but how do we take Scrum to the next level and scale it company-wide?<\/p>\n

The Scaled Agile Framework\u00ae (SAFe\u2122) is an\u00a0approach for doing just that!<\/p>\n

\"Scaled<\/p>\n

What is SAFe: Scaled Agile Framework?<\/strong><\/h2>\n

The Scaled Agile Framework (SAFe) is designed to provide a structure\u00a0for building and enhancing IT systems (software and architecture) in a continuous, predictable and Agile way. SAFe takes advantage of the working practices of Agile teams, embedding these into a framework which scales to enterprise level. It encompasses roles, practices and guidance for adoption and operation of the framework.<\/p>\n

The goal of SAFe is to enable multiple Agile development teams to provide a\u00a0continuous flow of new and enhanced software, and supporting infrastructure, with a focus\u00a0on providing strategically-defined and targeted value. \u00a0In other words, it delivers what the business needs, when it needs it, with regular and frequent releases into live use.\u00a0SAFe is typically aimed at a development group\u00a0of\u00a050 people or more (including all development and testing roles, and appropriate business customer representatives). Many Scaled Agile Framework success stories have been reported: a large Australian telecom company implemented SAFe for a\u00a0software development capability of\u00a070 software professionals working as eight Agile teams. You can read more stories of\u00a0the\u00a0successful adoption of SAFe at www.scaledagile.org<\/a>.<\/p>\n

The Structure of the Scaled Agile Framework<\/h2>\n

\"Scaled<\/p>\n

The Scaled Agile Framework (SAFe) is presented as an interactive “Big Picture” graphic (www.scaledagileframework.com<\/a>) which defines\u00a0roles, teams, activities, techniques and artifacts necessary to scale Agile from team to program to enterprise level. It provides a framework for the organisational structuring of an on-going IT development capability. It combines elements of Kaizen (continual improvement), Lean thinking, Agile development techniques, Kanban and Product Development Flow.<\/p>\n

SAFe defines three levels: Team, Program and Portfolio.<\/p>\n

<\/h3>\n

<\/h3>\n

Team Level<\/h3>\n

The team level is based on Scrum and Extreme Programming (XP) practices. SAFe expands these to cater for the scenario where multiple Scrum \/ XP teams are delivering business software concurrently\u00a0and interdependently.<\/p>\n

SAFe provides a structure to co-ordinate the work of multiple small teams to allow them to deliver maximum return on investment, in line with an overall Portfolio-level Vision and Roadmap. This goes far beyond the Scrum concept of “Scrum-of-Scrums”, providing role definitions and guidance for achieving this co-ordination. SAFe also adopts the technical practices of eXtreme Programming (such as test-first development and continuous integration) to enable the production of high-quality software.<\/p>\n

How does SAFe work in practice at team level?<\/h4>\n

The Agile development capability is divided into small, cross-functional teams. Each team works in synchronised Sprints, of typically two weeks, to deliver both new business functionality and related technical architecture. Time-synchronised sprints give a regular “cadence” (i.e.\u00a0rhythm) to their work and allow for easier co-ordination of their efforts. These Agile teams collaborate to plan their releases and explore their dependencies at the Program level.<\/p>\n

Program Level<\/h3>\n

The Program level provides the vehicle for scheduling\u00a0regular and frequent output\u00a0of business functionality, which the Scaled Agile Framework\u00a0calls the “Agile Release Train<\/a>“. \u00a0It also provides structure for the Agile development teams to co-ordinate their planning, related to both business features and architecture, thus ensuring that the teams are aligned. It promotes the prioritisation of the most valuable features based on delivering the “weighted shortest job first<\/a>“. Finally, it provides the\u00a0Portfolio level with a mechanism for predictable and visible delivery of their Vision and Roadmap. The Program level receives vision and strategic guidance from the Portfolio level.<\/p>\n

The Agile Release Train<\/h4>\n

Releases are planned jointly by development teams, typically every 2-3 months, with the mantra “develop on cadence, deliver on demand”. The evolving architecture necessary to support new business functionality is planned and developed just ahead of the related\u00a0business functionality as an “Architectural Runway<\/a>” that can successfully land<\/em>\u00a0the new business functionality.<\/p>\n

Portfolio Level<\/h3>\n

The Portfolio level provides the Vision and Roadmap to which the development teams work and prioritise. \u00a0SAFe Portfolio Management views the organisation\u2019s strategy as a set of investment themes. Management roles agree a percentage allocation of budget and resource for each theme, proportional to\u00a0strategy and predicted return on investment. A Portfolio Backlog is compiled, listing the large scale development items to be initiated;\u00a0these may span multiple releases. A Kanban-style approach is used to keep control of the amount of work in progress and to manage the flow of work, to optimise the use of\u00a0the development capability of the organisation.<\/p>\n

Should I Implement the Scaled Agile Framework?<\/h2>\n

Where an organisation has already mastered Agile at a team level, but now needs a way to scale this into a predictable delivery function on a continuous and large scale, the Scaled Agile Framework has the potential to be a great fit. The techniques and ways of working learned for Scrum and XP will be directly transferable to the SAFe approach. Even if the Agile approach used at team level was not Scrum, the adoption of SAFe teams should still be straightforward, as\u00a0there is much\u00a0overlap in Agile practices and culture. SAFe gives the structure and guidance to carry these practices to a wider, enterprise level.<\/p>\n

For some organisations,\u00a0SAFe will require\u00a0changes to the way development work is initiated and funded, to support regular releases. It will often promote\u00a0cultural changes and will need a style of leadership which is facilitative and empowering. SAFe\u00a0may\u00a0not be appropriate for all situations, but where there is a substantial, continuous IT development capability and a need to provide new software in an Agile way, to satisfy business demands on a frequent, on-going basis, the Scaled Agile Framework is worthy of serious consideration.<\/p>\n

 <\/p>\n

\"Scaled<\/a>Ready to take the next step? \u00a0Scaled Agile Framework: SAFe Agilist training<\/a>\u00a0may be\u00a0just what you’re looking for. It covers\u00a0both the underlying principles of the Scaled Agile Framework and the\u00a0knowledge necessary to lead an enterprise Agile transformation.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

The benefits of using an Agile approach for delivering IT products and software are now well-established. The majority of organisations use the Scrum\u00a0Agile approach, which is optimised for team-level working, but how do we...<\/p>\n","protected":false},"author":3,"featured_media":407,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,7,35],"tags":[],"_links":{"self":[{"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/posts\/211"}],"collection":[{"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/comments?post=211"}],"version-history":[{"count":2,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/posts\/211\/revisions"}],"predecessor-version":[{"id":408,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/posts\/211\/revisions\/408"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/media\/407"}],"wp:attachment":[{"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/media?parent=211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/categories?post=211"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tcc-net.com\/blog\/wp-json\/wp\/v2\/tags?post=211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}