Scaled Agile Framework (SAFe) - Leading SAFe questions and answers 100% correct

Scaled Agile Framework (SAFe) - Leading SAFe questions and answers 100% correct 5 Core Competencies Lean Agile Leadership Team - Team and Technical Ability Program - DevOps and release on demand Large Solution - Business Solutions & Lean Systems Portfolio - Lean Portfolio Management Benefits of safe Time to market: 30-75% faster Quality: 25-75% defect reduction Productivity: 20-50% increased productivity Engagement: 10-50% happier, more motivated employees Steps in Agile Define Build Test Deploy Continuous Delivery Pipeline Continuous Exploration Continuous Integration Continuous Deployment Release on Demand Lean Portfolio Management Connect the portfolio to the enterprise strategy Creates Lean Budgets and investment guardrails Manages portfolio operations Provides Lean government across value streams SAFe core values - Alignment - Transparency - Built-in Quality - Program Execution SAFe House of Lean VALUE - Respect for people and culture - Flow - Innovation - Relentless Improvement LEADERSHIP Value Achieve the shortest sustainable lead time with: - best quality and value to people and society - high morale, safety, and customer delight Respect for People and Culture - people do the work - your customer is whoever consumes your work - build long term partnerships based on trust - cultural change comes last, not first - to change the culture, you have to change the organization Flow - Optimize continuous and sustainable throughput of value - avoid start-stop-start project delays - Build quality in - Understand, exploit, and manage variability - Integrate frequently - Informed decision-making via fast feedback Innovation - Producers innovate, customers validate - Get out of the office (Gemba: walk around) - Provide time and space for creativity - Pivot without mercy of guilt Relentless Improvement - A constant sense of danger - Optimize the whole - Consider facts carefully, then act quickly - Apply lean tools to identify and address root causes - Reflect at key milestones; identify and address shortcomings Leadership - Lead the change - Know the way; emphasize life long learning - Develop people - Inspire and align with mission; minimize constraints - Decentralize decision-making - Unlock the intrinsic motivation of knowledge workers Agile Manifesto (4 key points) 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan 12 Principles of Agile Manifesto (1-6) 1. Our highest priority is to satisfy the customer through early and continuous delivery of software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference on shorter. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 12 Principles of Agile Manifesto (6-12) 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity - the art of maximizing the amount of work not done, is essential. 11. The best architectures, requirements and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. SAFe Lean-Agile Principles (9 total) 1. Take an economic view. 2. Apply systems thinking. 3. Assume variability; preserve options. 4. Build incrementally with fast, integrated learning cycles. 5. Base milestones on objective evaluation of working systems. 6. Visualize and limit WIP, reduce batch sizes, and manage queue length. 7. Apply cadence, synchronize with cross-domain planning. 8. Unlock the intrinsic motivation of knowledge workers. 9. Decentralize decision making.