Talk:Scaled agile framework
HI Vinpinhari. Thank you for creating this page. As the author and creator of the Scaled Agile Framework, there are several points of clarification that I recommend to create a more accurate and comprehensive page.
Please let me know what follow up questions you might have. References follow the recommendations.
Replace: After every 5 iterations, a train delivers a potentially shippable increment (PSI). A demo along with Inspect and Adapt sessions will be held. Also, planning will begin for the next increment.
With:
Teams develop complete systems in short iterations, typically two weeks in length. The Program Increment is a larger, quantum measuring point, which typically occurs on a cadence of 3-5 development iterations, followed by one Innovation and Planning (IP) Iteration. Each PI concludes with a demo of all the functionality that has been developed through the course of the PI. This is accompanied by an Inspect and Adapt session that includes root cause analysis and identification of systematic improvements.
The Innovation and Planning iteration supports the dedicated time for PI system demo, innovation and face to face PI planning.
This describes the basic development cadence, which synchronizes teams to a common mission and cadence, and focuses on the frequent integration of the full system. However, Teams and Programs can release functionality at any time the market demands, including continuous delivery.
Replace There are two different types of SAFe implementation, 3-Level SAFe and 4-Level SAFe. 3-Level SAFe is for smaller implementation with 100 people or less whereas 4-Level SAFe is for larger solutions having 100 or more people
With 3-level safe is generally applied in enterprises with Agile Release Trains that have less than 100 or so practitioners, although there can be many such programs within an enterprise portfolio. So a single instance of 3-level safe can often handle many hundreds of practitioners.
4-level safe is designed for the largest systems builders, enterprises that build systems that require the cooperation of multiple Agile Release Trains. In some cases, 200-400 people, and even more, are required to build these largest systems.
In addition, the large enterprises typically deploy multiple SAFe instances, one for each business unit, division or significant product line. Within that portfolio, there may be implementations of both 3-level and 4-level SAFe.
Replace:
A portfolio is a collection of programs which accounts for the whole part of budget going into software development.
With: A portfolio contains the value streams that sponsor the various solutions, which are realized by program-level Agile Release Trains. Portfolio fiduciaries fund value streams and apply lean-agile budgeting to eliminate much of the overhead and multiplexing caused by traditional project structures and project cost accounting.
Deanleffingwell (talk) 22:01, 16 March 2016 (UTC)Dean Leffingwell
- ^ http://www.scaledagileframework.com
- ^ Bloomberg, Jason. "Scaling Agile Development for Digital Transformation". Forbes. Forbes.
- ^ Leffingwell, Dean (2007). Scaling Software Agility: Best Practices for Large Enterprises (First ed.). Addison-Wesley. ISBN 978-0321458193.
- ^ Leffingwell, Dean (2011). Agile Software Requirements: Lean Requirements Practices for Teams, Programs and the Enterprise (First ed.). Addison-Wesley. ISBN 978-0321635846.
- ^ Linders, Ben. "Lean and Agile Leadership with the Scaled Agile Framework (SAFe)". InfoQ. Retrieved 12 January 2015.
- ^ Crain, Anthony. "Cracking the SAFe: An expert's take on the Scaled Agile Framework". Tech Beacon. HPE. Retrieved 20 October 2015.