Leading SAFe Exam Questions with Complete Solutions, Rated A+

Reasons for adopting Agile - Top 3 - Accelerate Product Delivery Enhance ability to manage changing priorities Increase Productivity What does SAFe do? - Synchronizes alignment, collaboration and delivery for large numbers of teams Deal in smaller chuncks Contracts - Do not build design deliverables into a contract Agile team - Cross functional and self-organizing. Can define, build and test valuable things Applied Agile SW Engineering practices with XP, Scrum and Kanban Delivers value every 2 weeks Enterprise, Lean and Large - In the large Enterprise, there may be multiple SAFe portfolios. House of Lean - Respect for people and culture Flow Innovation Relentless Improvement House of Lean Purpose - Best quality High morale House of Lean Flow - Avoid start and sop Build quality in Integrate frequently Fast feedback House of Lead Innovation - Give members time and capacity to think Producers innovate, customers validate House of Lean Relentless improvement - Optimize the whole A constant sense of danger House of Lean Leadership - Lead the change Develop people Intrinsic motivation Agile Manifesto - Value Individuals and interactions over processes and tools Working SW over comprehensive documentation Customer Collaboration over contract negoiation Responding to change over following a plan Aspects of systems thinking - Optimizing a component does not optimize the system A system can evolve no faster than its slowest integration point Value Stream - Optimize Focus on delays Deliver customer value Uncerainty - Requirements must be flexible Designs must be flexible Preservation of options improves economic results Set based approach - Multiple design options Learning points Learning cycles - Fast feedback accelerates knowledge Small batch sizes Shorter cycles = faster learning The iterative learning cycle - PDCA Plan, Do, Check, Adjust Phase Gates - Fix requirements and designs too early Objective Milestones - Facilitate learning and allow for continuous cost-effective adjustments towards and optimal solution System Demos - Orchestrated to deliver objective progress, product and process metrics BVIR - Big Visible Information Radar Queue - Work committed to Backlog - Work not committed too WIP - Limit of three user stories IP. If a developer is done, help other developers or test in order to move the stories forward Limit WIP, reduce batch sizes and manage queue lengths Small batches - Go through the system faster Most important batch is the handoff batch Large batches - Increase variability High utilization increases variability Severe project slippage is the most likely result