SAFe 5.0 Advanced Scrum Master

SAFe 5.0 Advanced Scrum Master Characteristics of an Effective Agile Team Ans- - Displays LeanEnt competency of Team & Tech Agility - Is able to reliably deliver - Members aren't challenge each others ideas - Makes process vis to team & stakeholders - Collaborates to achieve Iter goals & PI Objtives - Produce consistent hi quality increments of value - Sustains a predictable pace of development SAFe's 7 Core Competencies Ans- 1. Enterprise Solution Delivery 2. Agile Product Delivery 3. Team & Technical Agility 4. Lean Portfolio Mgt 5. Organizational Agility 6. Continuous Learning Culture 7. Lean - Agile Leadership 4 Primary Elements of SAFe Economic Framework Ans- 1. Operate within lean Budget & Guardrails 2. Understand solution economic tradeoffs 3. Leveraging suppliers 4. Sequencing Jobs for maximum benefit Economic Trade-off parameters Ans- - Lead time - Product cost - Value - Development expense - Risk Economic Trade-off best practices Ans- - Sequence jobs for maximum value - Don't consider money already spent - Make economic choices continuously - Empower local decision making - If only quantify 1 thing, quantify cost of delay Examples of High impact economic - financial indicators Ans- - Cost of late defect fixing - Cost of code branching with late merge - Cost of delayed performance testing - Cost of large # of cross team dependencies - Economic value of test automation - Econ val of enablers: research spikes, refactors, etc The cost of fixing a defect Ans- Grows nearly exponentially overtime 3 Primary aspects of Systems Thinking Ans- 1. The solution itself is a system 2. The enterprise building the system is a system 3. Optimize the full value stream Most process problems will surface as Ans- Delays Most of the time spent getting to market is spent on Ans- Delays The fastest way to reduce time to market is to Ans- Reduce delays Reduce lead times to Ans- Improve flow Bottlenecks Ans- - SM helps the team identify & remove bottlenecks - Every system has 1 or 2 significant bottlenecks - Removing 1 bottleneck improves performance, then remove more To build an optimal solution, Ans- Requirements and design must be flexible Iterative, incremental development Ans- can reduces uncertainty & increase predictability When Agile is adopted on top of traditional, phase gate mindset a typical problem is that Ans- - too many up front contraints - commitment to a solution is made too early - power of agile is reduced to minor adjustments Fast learning cycles (Increments) Ans- - Improve efficiency - Reduce cost of risk taking - Is facilitated by small batches - Requires increased investment in dev environment - The shorter the cycle the faster the learning Integration points Ans- - Accelerate learning - Dev proceeds no faster than slowest learning loop - Improvement comes through synchronization of design loops and faster learning cycles - Reduce risks Problems with phase gate milestones Ans- - determine requirements and design to early - needed adjusts identified too late, no time to adjust - tracking progress via traditional milestones delays learning points until its too late Objective Milestones Ans- - facilitate learning - allow for continuous cost-effective adjust to optimal solution How to reduce lead times Ans- - reduce size of work - reduce bottlenecks - reduce waiting - Increase swarming - Improve quality Too much WIP results in Ans- - No visibility to bottlenecks - System is usually highly inefficient - Confuses priorities - Causes frequent context switching - Increases overhead Optimal batch size Ans- Has the lowest total cost, which is a combination of holding cost and transaction cost. Reducing transaction cost Ans- - Reduces total cost - Reduces the optimal batch size (Can have more transactions at a lower cost) Reducing batch size Ans- - Increases predictabilit