SAFe 4.5 Emphasis on Lean Flow and Portfolio Management
•Download as PPTX, PDF•
1 like•406 views
Talk given at Scaled Agile Scotland about Lean Kanban and Lean Portfolio Management in SAFe 4.5 and comparisons with SAFe 4.0
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to SAFe 4.5 Emphasis on Lean Flow and Portfolio Management
Similar to SAFe 4.5 Emphasis on Lean Flow and Portfolio Management (20)
Recently uploaded
Recently uploaded (20)
SAFe 4.5 Emphasis on Lean Flow and Portfolio Management
- 1. 1© Scaled Agile, Inc. © Scaled Agile, Inc. Scaled Agile Hot Topics Lean Kanban & Lean Portfolio Management Craig Cockburn SAFe SA and SPC4 www.craigcockburn.com
- 2. 2© Scaled Agile, Inc. New Emphasis Was SAFe 4.0 for Lean Software and Systems Engineering Now in 4.5 SAFe for Lean Enterprises It’s not just about software, it’s about business agility Reminder: SAFe Lean and Agile Principles Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths
- 3. 3© Scaled Agile, Inc. 3© Scaled Agile, Inc. Lean Kanban 1
- 4. 4© Scaled Agile, Inc. What’s different in 4.5? SAFe 4.0 (supported until June 2018) • Team, Program and Portfolio (3 level) • Team, Program, Value Stream and Portfolio (4 level) SAFe 4.5 : • NEW: Essential SAFe: Team and Program levels • Portfolio SAFe: Team, Program and Portfolio levels • NEW: Large Solution SAFe: Team, Program & Large Solution levels • Full SAFe: Team, Program and Large Solution levels
- 5. 5© Scaled Agile, Inc. 4 Configurations in SAFe 4.5 • Essential SAFe - one agile release train (ART). One solution. • Large Solution SAFe - more than one ART. One solution • Portfolio SAFe - more than one solution • Full SAFe - both portfolio and large solution needed Each ART is a long-lived, self-organizing team of Agile Teams, a virtual organization (5 – 12 teams) Effective Agile Release Trains typically consist of 50 – 125 people
- 6. 6© Scaled Agile, Inc.
- 7. 7© Scaled Agile, Inc. Kanban in SAFe 4.5 • Portfolio Kanban: for epics – largest developments in a portfolio (require a lean business case, epic hypothesis). WSJF (cost of delay/job size) • Solution Kanban: for capabilities – solution behaviour. Fit in a PI. • Program Kanban: for features – system services to meet user needs. Benefits hypothesis + acceptance criteria. • Team Kanban (alternative to Scrum) • Epics -> Capabilities -> Features -> Stories • Enablers at all levels in SAFe support functionality for: Exploration, Architecture, Infrastructure and Compliance
- 8. 8© Scaled Agile, Inc. SAFe 4.5: New Program Kanban Funnel Analyzing Backlog Implementing Validating on Staging Deploying to Production Releasing Done IN PROG. READY 2 6 4 5 6 IN PROG. READY 4 3 5 Continuous Exploration Continuous Integration Continuous Deployment Release on Demand
- 9. 9© Scaled Agile, Inc. Focus on continuous Lean flow of value Identify bottlenecks and balance the amount of WIP against the available development and operations Decrease the batch sizes of the work Manage and reduce, queue lengths Optimum batch size (lowest total cost) Items per batch Cost Principles of Product Development Flow, Don Reinertsen Funnel Analyzing Backlog Implementing Validating on Staging Deploying to Production Releasing Done IN PROG. READY 2 6 4 5 6 IN PROG. READY 4 3 5 Continuous Exploration Continuous Integration Continuous Deployment Release on Demand
- 10. 10© Scaled Agile, Inc. 10© Scaled Agile, Inc. Lean Portfolio Management 2
- 11. 11© Scaled Agile, Inc. Lean Portfolio Management Full - both portfolio and large solution needed Portfolio - more than one solution Large Solution - more than one agile release train. One solution Essential SAFe - one agile release train (ART). One solution
- 12. 12© Scaled Agile, Inc. Lean Portfolio Management (was Program Portfolio Management in 4.0)
- 13. 13© Scaled Agile, Inc. Seven Transformational Patterns
- 14. 14© Scaled Agile, Inc. Lean Agile Budgeting
- 15. 15© Scaled Agile, Inc. Further Reading Lean portfolio http://www.scaledagileframework.com/lean-portfolio-management/ Small teams – core practices for getting started http://www.scaledagileframework.com/guidance-six-safe-practices-for-s- sized-teams/
- 16. 16© Scaled Agile, Inc. Published 11th April 2017
- 17. 17© Scaled Agile, Inc.
- 18. 18© Scaled Agile, Inc. Questions ?
- 19. 19© Scaled Agile, Inc. 19© Scaled Agile, Inc. Extra slides for further reading !
- 20. 20© Scaled Agile, Inc. SAFe Lean and Agile Principles
- 21. 21© Scaled Agile, Inc. Full SAFe configuration
- 22. 22© Scaled Agile, Inc. Portfolio SAFe configuration
- 23. 23© Scaled Agile, Inc. Large Solution SAFe configuration
- 24. 24© Scaled Agile, Inc. Essential SAFe configuration
- 25. 25© Scaled Agile, Inc. Links to courseware 12 new articles
Editor's Notes
- Lean is not a black and white. There is a connection between the transaction and holding costs. You can see how the transaction cost changes by the size of the batch. The more items I transfer at once, the lower the overall transaction cost is. On the other hand, the more items I have in a batch, the larger my inventories are, which increases the holding cost. The optimal batch size is at the minimum of the aggregation of the transaction and holding costs. The aggregated values form a U-Curve, and it’s not an exact science, rather, a sweet spot. More Examples: U-Curve illustrates the number of batch sizes U-Curve Optimization is a common effect in Lean, it highlights trade-offs which vary by context. Must understand transaction and holding costs. Applies to collocation since there are greater holding costs due to batching and lower transaction costs. Want the intersection. Applies to Iteration length, number of stories in a Iteration, number of features in a PI, amount of code developed before check in etc. etc.