|
|
| (4 intermediate revisions by one user not shown) |
| Line 1: |
Line 1: |
| − | Traditionally Software development has utilized Project Managers and Project Management. But With the introduction of the Scaled Agile Framework (SAFe) into development organizations from its release in 2011, the most popular Enterprise scale Agile model in the world <ref name ="C-Prime">C-Prime, ''https://www.cprime.com/wp-content/uploads/woocommerce_uploads/2017/09/cPrime-Scaling-Agile-Survey-17-Digital.pdf'', (NC-Prime, 2017), 14.</ref> effectively advocated removing Project Managers from development organizations.
| |
| − | The early SAFe versions advocacy of a new organization with new roles took traditional project manager responsibilities and moved them (partially) into the new SAFe's roles such as Product Owners, Scrum Masters and RTE’s. This led many organizations to "throw out the baby with the bathwater" by ignoring the value of those project, program and portfolio management practices that were not incorporated or clearly articulated in these early versions of SAFe.
| |
| − | During the period 2011-2017 Project management as a separate formal practice within many software development Organizations literally had no place in those organizations that tried to fully deploy SAFe as written. This is important because as of 2017 the SAFe methodology was used by 45% <ref name ="C-Prime"/> of those firms using an Agile methodology at scale. Many of these firms have had to contend with a number of issues that this caused up until the acceptance of Project Management through its "introduction" in the form of an Agile Project Management Office (APMO) in the 2017 release of SAFe version 4,5. This implicitly accepted the role PMO's play in strategy formation, Project and Program execution as well as owning and disseminating best practices (in this case represented in the SAFe model by the "Lean Centre of Excellence"). This development represents and acceptance from SAFe that their model should incorporate these project project, program and portfolio practices that had been dropped in previous versions.
| |
| − | In this article we look at the issues that have arisen in many firms during their SAFe implementations and explore whether the new APMO solves these issues or not.
| |
| − | The article is intended for practitioners who are working in or with organizations that have deployed early versions of SAFe as part of the support for establishing an APMO along the lines now advocated by SAFe.
| |
| − | Note: Due to the relatively new and evolving nature of SAFe there is limited empirical data around specific “Implementation issues in Large Scale Agile transformations”. As a consequence this article is more reliant more on Anecdotes, Personal Experience and other literature in this space.
| |
| | | | |
| − |
| |
| − |
| |
| − | == Scaled Agile Framework (SAFe) ==
| |
| − |
| |
| − | === What is SAFe? ===
| |
| − |
| |
| − |
| |
| − | [[File:scaledagile.PNG|frameless|500px]]
| |
| − |
| |
| − |
| |
| − | According to ScaledAgileFramework.com:
| |
| − |
| |
| − | “SAFe® for Lean Enterprises is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, and DevOps.” “It “…is built around the Seven Core Competencies of the Lean Enterprise that are critical to achieving and sustaining a competitive advantage in an increasingly digital age”
| |
| − |
| |
| − | It is as a standard in Software delivery organizations incorporating many modern "best practices" such as Lean, Systems thinking, Scrum, DevOps. its popularity has meant that there is a deep pool of people working with and available to implement it.
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | <references />
| |
| − |
| |
| − |
| |
| − | [[Category:''Scaled Agile Framework)'']] [[Category:''SAFe)'']] [[Category:''Implmenting Agile'']]
| |
