{"id":110993,"date":"2023-07-28T18:17:46","date_gmt":"2023-07-28T18:17:46","guid":{"rendered":"https:\/\/learnexams.com\/blog\/?p=110993"},"modified":"2023-07-28T18:17:50","modified_gmt":"2023-07-28T18:17:50","slug":"leading-safe-certification-exam2023-2024-100-verified-answers-safe-certification-exam","status":"publish","type":"post","link":"https:\/\/www.learnexams.com\/blog\/2023\/07\/28\/leading-safe-certification-exam2023-2024-100-verified-answers-safe-certification-exam\/","title":{"rendered":"LEADING SAFE CERTIFICATION EXAM(2023\/2024) 100% VERIFIED ANSWERS\/SAFE CERTIFICATION EXAM"},"content":{"rendered":"\n<p>Leading safe certification exam questions and answers pdf<br>Leading safe certification exam questions and answers<br>Leading safe certification exam questions<br>Leading safe certification exam answers pdf<br>Leading safe certification exam answers<br>leading safe exam questions<br>safe agile exam cheat sheet<br>safe agilist exam<\/p>\n\n\n\n<p>What are the core values of SAFe?<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Built-in Quality<\/li>\n\n\n\n<li>Program execution<\/li>\n\n\n\n<li>Alignment<\/li>\n\n\n\n<li>Transparency<\/li>\n<\/ol>\n\n\n\n<p>Train<br>a team of agile teams<\/p>\n\n\n\n<p>Value Stream<br>a team of trains<\/p>\n\n\n\n<p>Value steams deliver value via<br>Capabilities<\/p>\n\n\n\n<p>A train delivers value via<br>features and benefits<\/p>\n\n\n\n<p>An agile portfolio delivers value via<br>Epics<\/p>\n\n\n\n<p>Eight big mistakes when trying to make a change:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Allowing too much complacency<\/li>\n\n\n\n<li>Failure to create a sufficiently powerful guiding coalition<\/li>\n\n\n\n<li>Underestimating the power of vision<\/li>\n\n\n\n<li>Under-communicating the power of vision by 10-100x<\/li>\n\n\n\n<li>Permitting obstacles to block the new vision<\/li>\n\n\n\n<li>Failure to create short term wins<\/li>\n\n\n\n<li>Declaring victory too soon<\/li>\n\n\n\n<li>Neglecting to anchor changes firmly in the corporate culture<\/li>\n<\/ol>\n\n\n\n<p>ART<br>Agile Release Train<\/p>\n\n\n\n<p>VSE<br>Value Stream Engineer<\/p>\n\n\n\n<p>How many people are on a scrum team?<br>7 +\/- 2<\/p>\n\n\n\n<p>Which line of the agile structure is optional?<br>Value Stream<\/p>\n\n\n\n<p>Who is concerned with what institute the work comes from?<br>The epic owner<\/p>\n\n\n\n<p>What are the parts of the SAFe house of lean?<br>Base: Leadership<br>Pillars: Respect for people and culture, Flow, Innovation, and Relentless improvement<br>Top: Value<\/p>\n\n\n\n<p>What is the purpose of the SAFe house of lean?<br>Achieve the sustainably shortest lead time with:<br>-Best quality and value to people and society<br>-High morale, safety and customer delight<\/p>\n\n\n\n<p>What does a Respect for People and Culture entail?<br>Your culture must support change and you must anchor new behavior and then your culture will change. You must change the organization in order to change the culture.<\/p>\n\n\n\n<p>What does a Flow entail?<br>This prevents bottle necks and there is no stopping and starting. There is no room for the unknown is this is at max capacity.<\/p>\n\n\n\n<p>What does Innovation entail?<br>Producers innovate and customers validate; pivot without mercy or guilt; like undercover bosses<\/p>\n\n\n\n<p>What does Relentless Improvement entail?<br>Reflect at key milestones and identify and address shortcomings.<\/p>\n\n\n\n<p>What does Leadership mean as the base of the SAFe House of Lean?<br>leadership must be on board in order for the system to change; the system is how we are getting our work done so we might need a structural change to the organization<\/p>\n\n\n\n<p>What is the Agile Manifesto?<br>We have come to value:<br>Individuals and interactions over processes and tools<br>Working software over comprehensive documentation<br>Customer collaboration over contract negotiation<br>Responding to change over following a plan.<br>That is, while there is value in the items on the right, we value the items on the left more.<\/p>\n\n\n\n<p>What are the 12 parts of the Agile Manifesto?<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<\/li>\n\n\n\n<li>Welcoming changing requirements, even late in development. Agile processes harness change for the customer&#8217;s competitive advantage.<\/li>\n\n\n\n<li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.<\/li>\n\n\n\n<li>Business people and developers must work together daily throughout the project.<\/li>\n\n\n\n<li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<\/li>\n\n\n\n<li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<\/li>\n\n\n\n<li>Working software is the primary measure of progress.<\/li>\n\n\n\n<li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<\/li>\n\n\n\n<li>Continuous attention to technical excellence and good design enhances agility.<\/li>\n\n\n\n<li>Simplicity&#8211; the art of maximizing the amount of work not done &#8212; is essential<\/li>\n\n\n\n<li>The best architectures, requirements, and designs emerge from self-organizing teams.<\/li>\n\n\n\n<li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<\/li>\n<\/ol>\n\n\n\n<p>SAFe Lean-Agile principles<\/p>\n\n\n\n<p>Reasons for adopting Agile &#8211; Top 3<br>Accelerate Product Delivery<br>Enhance ability to manage changing priorities<br>Increase Productivity<\/p>\n\n\n\n<p>What does SAFe do?<br>Synchronizes alignment, collaboration and delivery for large numbers of teams<br>Deal in smaller chuncks<\/p>\n\n\n\n<p>Contracts<br>Do not build design deliverables into a contract<\/p>\n\n\n\n<p>Agile team<br>Cross functional and self-organizing. Can define, build and test valuable things<br>Applied Agile SW Engineering practices with XP, Scrum and Kanban<br>Delivers value every 2 weeks<\/p>\n\n\n\n<p>Enterprise, Lean and Large<br>In the large Enterprise, there may be multiple SAFe portfolios.<\/p>\n\n\n\n<p>House of Lean<br>Respect for people and culture<br>Flow<br>Innovation<br>Relentless Improvement<\/p>\n\n\n\n<p>House of Lean Purpose<br>Best quality<br>High morale<\/p>\n\n\n\n<p>House of Lean Flow<br>Avoid start and sop<br>Build quality in<br>Integrate frequently<br>Fast feedback<\/p>\n\n\n\n<p>House of Lead Innovation<br>Give members time and capacity to think<br>Producers innovate, customers validate<\/p>\n\n\n\n<p>House of Lean Relentless improvement<br>Optimize the whole<br>A constant sense of danger<\/p>\n\n\n\n<p>House of Lean Leadership<br>Lead the change<br>Develop people<br>Intrinsic motivation<\/p>\n\n\n\n<p>Agile Manifesto<br>Value<br>Individuals and interactions over processes and tools<br>Working SW over comprehensive documentation<br>Customer Collaboration over contract negoiation<br>Responding to change over following a plan<\/p>\n\n\n\n<p>Aspects of systems thinking<br>Optimizing a component does not optimize the system<br>A system can evolve no faster than its slowest integration point<\/p>\n\n\n\n<p>Value Stream<br>Optimize<br>Focus on delays<br>Deliver customer value<\/p>\n\n\n\n<p>Uncerainty<br>Requirements must be flexible<br>Designs must be flexible<br>Preservation of options improves economic results<\/p>\n\n\n\n<p>Set based approach<br>Multiple design options<br>Learning points<\/p>\n\n\n\n<p>Learning cycles<br>Fast feedback accelerates knowledge<br>Small batch sizes<br>Shorter cycles = faster learning<\/p>\n\n\n\n<p>The iterative learning cycle<br>PDCA<br>Plan, Do, Check, Adjust<\/p>\n\n\n\n<p>Phase Gates<br>Fix requirements and designs too early<\/p>\n\n\n\n<p>Objective Milestones<br>Facilitate learning and allow for continuous cost-effective adjustments towards and optimal solution<\/p>\n\n\n\n<p>System Demos<br>Orchestrated to deliver objective progress, product and process metrics<\/p>\n\n\n\n<p>BVIR<br>Big Visible Information Radar<\/p>\n\n\n\n<p>Queue<br>Work committed to<\/p>\n\n\n\n<p>Backlog<br>Work not committed too<\/p>\n\n\n\n<p>WIP<br>Limit of three user stories IP. If a developer is done, help other developers or test in order to move the stories forward<\/p>\n\n\n\n<p>Limit WIP, reduce batch sizes and manage queue lengths<\/p>\n\n\n\n<p>Small batches<br>Go through the system faster<br>Most important batch is the handoff batch<\/p>\n\n\n\n<p>Large batches<br>Increase variability<br>High utilization increases variability<br>Severe project slippage is the most likely result<\/p>\n\n\n\n<p>Optimum batch size<br>Lowest total cost<br>Example of U curve optimization<br>Total costs are the sum of holding costs and transaction costs<br>Higher transaction costs shift optimum batch size higher<br>Higher holding costs shift batch size lower<\/p>\n\n\n\n<p>Reducing optimum batch size<br>Reducing transaction costs reduces total costs and shifts optimum batch size lower<br>Reducing batch size<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increases predicstibility<\/li>\n\n\n\n<li>Accelerates feedback<\/li>\n\n\n\n<li>Reduces rework<\/li>\n\n\n\n<li>Lowers cost<\/li>\n<\/ul>\n\n\n\n<p>Holding cost<br>holding cost (the cost for delayed feedback, inventory decay, and delayed value delivery)<\/p>\n\n\n\n<p>Transaction cost<br>transaction cost (the cost of preparing and implementing the batch)<\/p>\n\n\n\n<p>U Curve<br>To improve the economics of handling smaller batches\u2014and thus increase throughput\u2014teams must focus on reducing the transaction costs of any batch. This typically involves increasing the attention to and investment in infrastructure and automation, including things such as Continuous Integration and the build environment, DevOps automation, and system test setup times. This is integral to systems thinking (Principle #2) and a critical element in long-view optimization.<\/p>\n\n\n\n<p>Queues<br>Long queues are back<br>Committed work<\/p>\n\n\n\n<p>Little&#8217;s Law<br>Reduce queue lengths<br>Faster processing time decreases wait<br>Shorter queue lengths decreases wait<br>Control wait times by controlling queue lengths<\/p>\n\n\n\n<p>Cadence<br>5 Sprints per increment<br>Develop on cadence; release on demand<\/p>\n\n\n\n<p>Decentralize decision making<br>Define economic logic behind a decision<br>Empower others to actually make them<\/p>\n\n\n\n<p>Value doesn&#8217;t follow silos<br>Value delivery is inhibited by hand-offs and delays<br>Political boundaries can prevent cooperation<br>Silos encourage geographical distribution of functions<br>Communication across silos is difficult<\/p>\n\n\n\n<p>Build cross functional Agile teams<br>Agile teams are cross-functional, self organizing<br>Optimized for communication<br>Deliver value every 2 weeks<\/p>\n\n\n\n<p>Teams execute iterations with Scrum<br>Scrum is built on transparency, inspection and adaption<\/p>\n\n\n\n<p>ARTs<br>Continuously deliver value<br>5 &#8211; 12 teams (50 &#8211; 125+ individuals)<br>Common cadence, PI<br>Common mission, Program Backlog<\/p>\n\n\n\n<p>RTE<br>Acts as the Chief Scrum Master<\/p>\n\n\n\n<p>Product Management<br>Owns, defines and prioritizes the Program Backlog<\/p>\n\n\n\n<p>System Architect\/Engineering<br>Provides architectural guidance and technical enablement to the teams on the train<\/p>\n\n\n\n<p>System Team<br>Provides processes and tools to integrate and evaluate assets early and often<\/p>\n\n\n\n<p>Business Owners<br>Key Stakeholders on the ART<\/p>\n\n\n\n<p>PI Planning<br>Cadence-based PI planning meetings are the pacemaker of the Agile Enterprise<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Two days every 8-12 weeks. 10 weeks typical<\/li>\n\n\n\n<li>Everyone attends if possible<\/li>\n\n\n\n<li>Product Management owns the features if possible<\/li>\n\n\n\n<li>Development owns Story Planning and HLE<\/li>\n\n\n\n<li>Arch\/Eng and US work as intermediaries for governance, interfaces and dependencies<\/li>\n<\/ul>\n\n\n\n<p>PI Planning Process<br>Input &#8211; Vision and Top 10 features<br>Output &#8211; Team and Program PI objectives and program board<\/p>\n\n\n\n<p>PI Objectives<br>Business summaries of what each team intends to deliver in the upcoming PI<br>Typically map to features, but now always<\/p>\n\n\n\n<p>Maintain predictability with Stretch objectives<br>They do count in velocity\/capacity<br>They are planned<br>However, not included in the commitment<br>Low confidence or many unknowns &#8211; move to a stretch<\/p>\n\n\n\n<p>Features are implemented by Stories<br>Small increments of value that can be delivered in days and provide value<br>Teams collaborate to deliver Features incrementally via User Stories<br>Features fit in one PI for one ART<br>Stories fit in one Iteration (Sprint) for one team<\/p>\n\n\n\n<p>Enabler Stories<br>Exploration<br>Architecture<br>Infrastructure<br>Compliance<\/p>\n\n\n\n<p>Story Points<br>Singular number that represents Volume, Complexity, Knowledge, Uncertainty<br>Relative &#8211; Not connected to a unit of measure<br>8 point story should take 4x longer than a 2 point story<\/p>\n\n\n\n<p>Story Points 2<br>Find a small Story that would take about a half-day to develop and a half-day to test and validate. Call it a 1<br>Estimate every other Story relative to that one<br>Never look back (don&#8217;t worry about recalibrating)<\/p>\n\n\n\n<p>PI Management Review<br>After PI Planning Day 1, Management meets to adjust as needed.<br>What did we just learn?<br>Adjust Vision, Scope, Resources?<br>Bottlenecks?<br>Decisions that need to be made before tomorrow?<\/p>\n\n\n\n<p>PI Final Plan<br>Collected at the front of the room<br>Reviewed by all teams<br>Business owners asked if they accept the plans<br>If so, okay. If not, continue to plan.<\/p>\n\n\n\n<p>Program Risks<br>ROAM<br>Resolved &#8211; Has been addresses. No Longer a concern.<br>Owned &#8211; Someone has taken responsibility<br>Accepted &#8211; Nothing more can be done. If risk occurs, release may be compromised<br>Mitigated &#8211; Team has plan to adjust as necessary<\/p>\n\n\n\n<p>PI &#8211; Confidence Vote<br>Completed after dependencies are resolved and risks are addressed<br>Range of 1-5<br>1 = No confidence<br>5 = Very high confidence<\/p>\n\n\n\n<p>PI &#8211; Retrospective<br>Help continuously evolve<\/p>\n\n\n\n<p>ARTs<br>Continuously deliver value<br>Continuous Exploration<br>Continuous Integration<br>Continuous Deployment<\/p>\n\n\n\n<p>Closed Loop<br>Program Events create a closed loop system to keep the train on the tracks<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PI Planning<\/li>\n\n\n\n<li>Scrum of Scrums<\/li>\n\n\n\n<li>PO Sync<\/li>\n\n\n\n<li>System Demo<\/li>\n\n\n\n<li>Prepare for PI Planning<\/li>\n\n\n\n<li>Inspect &amp; Adapt<\/li>\n<\/ul>\n\n\n\n<p>ART Sync<br>Used to coordinate progress<br>Programs coordinate dependencies through sync meetings<\/p>\n\n\n\n<p>Scrum of Scrums<br>Visibility into progress and impediments<br>Facilitated by RTE<\/p>\n\n\n\n<p>PO Sync<br>Visibility into progress, scope and priority adjustments<br>Facilitated by RTE<\/p>\n\n\n\n<p>Roadmap<br>Guides the deliver of features over time<br>PX &#8211; Committed<br>PX+2 &#8211; Foretasted<\/p>\n\n\n\n<p>Features<br>Is an industry-standard term familiar to marketing and Product Management<br>Have Benefit Hypothesis and Acceptance Criteria<br>Reflect functional and non functional requirements<br>Fitsin one PI<\/p>\n\n\n\n<p>Benefit Hypothesis<br>Justify Feature implementation cost, and provides business perspective when making scope decisions<\/p>\n\n\n\n<p>Acceptance Criteria<br>Typically defined during the backlog refinement<\/p>\n\n\n\n<p>Prioritize Features<br>For Optimal ROI<br>What is the Cost of Delay (CoD) in delivering value<br>What is the cost to implement the valuable thing?<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Business impact, missed revenue, delay other project, opportunity enablement<\/li>\n<\/ul>\n\n\n\n<p>WSJF<br>Weighted Shortest Job First<br>Give preference to jobs with shorter duration and higher CoD using WSJF<br>WSJF = CoD \/ Duration<\/p>\n\n\n\n<p>Components of CoD<br>User and business value &#8211; Relative value to the customer or business<br>Time criticality &#8211; How user\/business value decays over time<br>Risk Reduction &amp; Opportunity enablement (RR &amp; OE) &#8211; What else does this do for our business<\/p>\n\n\n\n<p>WSJF Stakeholders<br>Business Owners, Product Managers, Product Owners, System Architects<\/p>\n\n\n\n<p>Continuously Integrate<br>Stories and Features<\/p>\n\n\n\n<p>System Increment<br>Continuous functionality building<\/p>\n\n\n\n<p>Continious Story Integration<br>Features<br>Enablers &#8211; Functionality needed for a feature to work<br>Spike &#8211; research enabler<\/p>\n\n\n\n<p>Demo<br>Demo the full system increment every two weeks<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Features are functionally complete or toggled so not to disrupt the demonstrable functionality<\/li>\n\n\n\n<li>New Features work together, and with existing functionality<\/li>\n\n\n\n<li>Happens after the team&#8217; demo (may lag by as much as one iteration)<\/li>\n\n\n\n<li>Demo from a staging environment, resemble production as much as possible<\/li>\n<\/ul>\n\n\n\n<p>DOD (Definition of Done)<br>E.g. Do not close story unless all defects closed<\/p>\n\n\n\n<p>Build quality in<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensures every increment of the solution reflects quality standards<\/li>\n<\/ul>\n\n\n\n<p>Test First<br>Automate now<br>Automated tests are implemented in the same iteration as the functionality<\/p>\n\n\n\n<p>Architectural Runway<br>Existing code, hw components, etc. that enables near-term business features<br>Enablers build up the runway<br>Features consume it<br>Must be continuously maintained<\/p>\n\n\n\n<p>DevOps<br>is a cultural change<\/p>\n\n\n\n<p>Deployment pipeline<br>Used to deploy environments as well as solutions<\/p>\n\n\n\n<p>Measurements<br>Are an important part of DevOps<\/p>\n\n\n\n<p>Chaos Monkey<br>Developed by NEtflix<\/p>\n\n\n\n<p>What is DevOps<br>An agile approach to bridge the gap between development and operations to deliver value faster and more reliably<\/p>\n\n\n\n<p>DevOps is IN the Value Stream<br>Value occurs only when the end users are operating the solution<br>Define, Implement, Deploy &#8211; REPEAT<br>DevOps is not optional<\/p>\n\n\n\n<p>CALMR approach to DevOps<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Culture &#8211; establish a culture of shared responsibility<\/li>\n\n\n\n<li>Automation &#8211; Automate the continuous delivery pipeline<\/li>\n\n\n\n<li>Lean Flow &#8211; Keep batch sizes small, limit WIP and provide extreme visibility<\/li>\n\n\n\n<li>Measurement &#8211; Measure the flow through the pipeline. Implement application telemetry<\/li>\n\n\n\n<li>Recovery &#8211; Architect and enable low-risk releases. Establish fast recovery, fast reversion and fast fix forward<\/li>\n<\/ul>\n\n\n\n<p>DevOps goal<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deliver value more frequently<\/li>\n\n\n\n<li>Ends the Silo approach<\/li>\n\n\n\n<li>Deliver small batches of functionality in a flow process called the Continuous Delivery Pipeline<\/li>\n\n\n\n<li>Improve collaboration between IT and Delivery<\/li>\n\n\n\n<li>Faster time to market<\/li>\n\n\n\n<li>Take an economic view and decentralize decision making applies to DevOps<\/li>\n<\/ul>\n\n\n\n<p>Automate Everything &#8211; DevOps Tools<br>ALM &#8211; CA Agile Central, Version One, Agile Craft<br>Build &#8211; Ant, Maven, Bamboo, Jenkins<br>Continuous Integration (CI) &#8211; CruiseControl, Jenkins, Continuum<br>Continuous Development &#8211; Capistrano, UrbanCode, Ansible, Puppet<\/p>\n\n\n\n<p>Lean Flow<br>SAFe teams strive to achieve a state of continuous flow, enabling new features to move quickly from concept to cash.<br>Three primary keys:<br>1) Visualize and limit WIP<br>2) Reduce the batch sizes of work items<br>3) Manage queue lengths<\/p>\n\n\n\n<p>Measure the Flow of the Value through Telemetry<br>Automated collection of real-time data regarding the performance of solutions &#8211; helps to quickly assess the impact of frequent application changes<\/p>\n\n\n\n<p>Recover &#8211; Enable Low-Risk Releases<br>To support release on demand, the system must be designed for low-risk component or service-based deploy, fast recovery, etc. To support fast recovery:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stop-the-line mentality &#8211; Everyone swarms to fix any problem<\/li>\n\n\n\n<li>Plan for and rehearse for failures &#8211; Chaos Monkey<\/li>\n\n\n\n<li>Build the environment and capability to fix forward or roll back<\/li>\n<\/ul>\n\n\n\n<p>Non Functional Requirements<br>NFR<br>Put into Definition of Done<\/p>\n\n\n\n<p>Six recommended practices for Continuous Development<br>1) Maintain development and test environments to better match production<br>2) Maintain a staging environment that emulates production<br>3) Deploy to staging every iteration<br>4) Automate testing of features and nonfunctional requirements<br>5) Automate deployment<br>6) Decouple deployment from release<\/p>\n\n\n\n<p>Decouple deployment from release<br>Release on demand<br>Develop on cadence<\/p>\n\n\n\n<p>Decouple release elements from the total solution<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>End-user functionality (released every 2 weeks)<\/li>\n\n\n\n<li>Security updates (released on demand)<\/li>\n\n\n\n<li>Back-office functionality (released every month)<\/li>\n\n\n\n<li>Entire solution (major release every quarter)<\/li>\n<\/ul>\n\n\n\n<p>Triangle<br>You can have fixed dates and fixed cost, just not fixed scope<\/p>\n\n\n\n<p>System validation<br>User acceptance testing<br>Final NFR testing<br>Integration testing with other systems<br>Regulatory standards and requirements<\/p>\n\n\n\n<p>Innovation and Planning iteration<br>Opportunity for innovation hackathons, and infrastructure improvements<br>Provides for cadence-based planning<br>Estimating guard band for cadence-based delivery<\/p>\n\n\n\n<p>Without the IP iteration<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lack of delivery capacity buffer<\/li>\n\n\n\n<li>Little innovation<\/li>\n\n\n\n<li>Technical debt grows uncontrollably<\/li>\n\n\n\n<li>People burn out<\/li>\n\n\n\n<li>No time for teams to plan, demo or improve together<\/li>\n<\/ul>\n\n\n\n<p>Inspect and Adapt<br>Three parts:<br>1) PI System Demo<br>2) Quantitative measurement<br>3) Problem-solving workshop<\/p>\n\n\n\n<p>PI system demo<br>At the end of a PI, teams demonstrate the current state of the solution to the appropriate stakeholders<\/p>\n\n\n\n<p>Program performance reporting<br>As part of the solution demo, teams compare planned vs. actual PI objectives<\/p>\n\n\n\n<p>PI Predictability measure<br>Shows weather achievements fall into an acceptable process control band<\/p>\n\n\n\n<p>Problem solving workshop<br>Teams conduct a short retrospective, then systematically address the larger impediments that are limiting velocity<\/p>\n\n\n\n<p>Benefits of features<br>Hypothesis<br>Acceptance criteria<\/p>\n\n\n\n<p>Transformational leadership<br>A model in which leaders inspire and motivate followers to achieve high performance<\/p>\n\n\n\n<p>Four dimensions of a transformational leader<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Vision<\/li>\n\n\n\n<li>Authenticity<\/li>\n\n\n\n<li>Growth<\/li>\n\n\n\n<li>Innovation<\/li>\n<\/ul>\n\n\n\n<p>Transformational leadership &#8211; Vision<br>Inspire and align with the mission, minimize constraints<br>Lead change<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establish a sense of urgency<\/li>\n\n\n\n<li>Create a powerful guiding coalition<\/li>\n<\/ul>\n\n\n\n<p>Transformational leadership &#8211; Authenticity<br>Lead the change, know the way<br>Be a role model<br>Be a lifelong learner<br>Create an environment of trust and respect<br>Act with integrity<\/p>\n\n\n\n<p>Transformational leadership &#8211; Growth<br>Offer personalized support, coaching and encouragement<br>Keep communication open<br>Offer direct recognition<br>Exhibit genuine care and concern<br>Build an environment of mutual influence<\/p>\n\n\n\n<p>Leadership styles<br>Expert<br>Conductor<br>Developer of people<\/p>\n\n\n\n<p>Leader as an expert<br>Effective when manager has greater knowledge than direct people<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Technician or master craftsman<\/li>\n\n\n\n<li>Problem-solver<\/li>\n\n\n\n<li>Understands the domain and the technology<\/li>\n<\/ul>\n\n\n\n<p>Challenges<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limits learning and growth<\/li>\n<\/ul>\n\n\n\n<p>Leader as a conductor<br>Effective when coordination is a prerequisite for maximum performance<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Central decision maker<\/li>\n\n\n\n<li>Subtle and indirect manipulation<\/li>\n<\/ul>\n\n\n\n<p>Challenges<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Narrows focus of direct reports to their own areas<\/li>\n\n\n\n<li>Use systems and procedures to control work<\/li>\n<\/ul>\n\n\n\n<p>Leader as &#8216;developer of people&#8217;<br>Escape the trap with a post-heroic, Lean leadership style<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Creates a team jointly responsible for success<\/li>\n\n\n\n<li>How can each problem be solved in a way to develop people<\/li>\n<\/ul>\n\n\n\n<p>Benefits<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increased direct report ownership and responsibility<\/li>\n\n\n\n<li>Increased employee engagement and motivation<\/li>\n\n\n\n<li>Allows leader to spend more time managing laterally and upward<\/li>\n\n\n\n<li>There is no limit to the power of getting things done<\/li>\n<\/ul>\n\n\n\n<p>Transformational Leadership &#8211; Innovation<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Challenge the Status Quo<\/li>\n\n\n\n<li>Encourage learning, creativity, exploring new ways of doing things<\/li>\n\n\n\n<li>Decentralize decision making<\/li>\n\n\n\n<li>Expect relentless improvement<\/li>\n\n\n\n<li>Encourage innovative thinking<\/li>\n\n\n\n<li>Create a safe environment of mutual influence<\/li>\n<\/ul>\n\n\n\n<p>Lean portfolio management empowers the portfolio<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strategy &amp; Investment funding<\/li>\n\n\n\n<li>Lean Governance<\/li>\n\n\n\n<li>Agile Portfolio Operations<\/li>\n<\/ul>\n\n\n\n<p>Strategic themes<br>Differentiating, specific and itemized business objectives that connect a portfolio to the strategy of the enterprise<\/p>\n\n\n\n<p>Problem: Cost-center budgeting<br>Traditional project-based, cost center budgeting creates overhead and friction, lowers velocity<\/p>\n\n\n\n<p>Problem: Projects increase Cost of Delay<br>When overruns happen, project accounting and re-budgeting increases Cost of Delay and impacts culture<\/p>\n\n\n\n<p>Solution: Lean-Agile budgeting<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Organize and fund value streams<\/li>\n\n\n\n<li>Fund value streams, not projects<\/li>\n\n\n\n<li>Provides for full control of spend, with:<\/li>\n\n\n\n<li>No costly and delay inducing project cost variance analysis<\/li>\n\n\n\n<li>No resource reassignments<\/li>\n\n\n\n<li>No blame game for project overruns<\/li>\n<\/ul>\n\n\n\n<p>Control costs with increased flexibility<br>ART budgets and resources are unaffected by Features cost overruns or changing priorities<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Delay feature as necessary<\/li>\n<\/ul>\n\n\n\n<p>Epics<br>Enterprise initiatives sufficiently substantial in scope so to warrant analysis, understanding ROI, a lightweight business case, and approval.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Portfolio Epics cut across Value Streams<\/li>\n\n\n\n<li>Program Epics can be implemented in a single train<\/li>\n\n\n\n<li>Business Epics are customer-facing<\/li>\n\n\n\n<li>Enabler Epics enable solutions to address business needs<\/li>\n\n\n\n<li>Developed and analyzed in the Kanban systems<\/li>\n<\/ul>\n\n\n\n<p>Each Epic<br>-Has a hypothesis<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Defines MVP<\/li>\n<\/ul>\n\n\n\n<p>Portfolio Kanban<br>Manages the flow of Epics<\/p>\n\n\n\n<p>Estimating Epics<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Broken down into potential Features during the Portfolio Kanban analysis stage<\/li>\n\n\n\n<li>Potential Features are estimated in Story Points<\/li>\n\n\n\n<li>Feature estimates are aggregated back into the Epic estimate as part of the Lean Business Case<\/li>\n<\/ul>\n\n\n\n<p>Dynamic budgeting<br>Adjust budgets dynamically to meet changing business needs<\/p>\n\n\n\n<p>ARTs power the Solution Train<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Each ART within A Solution Train contributes to the development of a large solution<\/li>\n<\/ul>\n\n\n\n<p>Suppliers play a key role in large solution development<br>The overall value stream is dependent on the suppliers&#8217; agility<\/p>\n\n\n\n<p>Customers are inseparable from the development process<br>Indirect &#8211; General solutions. Example. End-user purchaser of a CRM System. MS Office<br>Direct &#8211; Custom- built solutions. Example. Government purchaser of a defense system<\/p>\n\n\n\n<p>Coordinate and integrate multiple ARTs and suppliers<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prepare with Pre- and Post-PI Planning meetings<\/li>\n\n\n\n<li>Typically attended by customers, STE, Solution Mgmt, Solution Architects, etc.<\/li>\n<\/ul>\n\n\n\n<p>Pre-Planning structure<br>Goal &#8211; Align Product Managers, System Architects and other ART stakeholders to a common vision<br>Input &#8211; Results of the previous PI execution<br>Output &#8211; A set of features for every ART<\/p>\n\n\n\n<p>Post-Planning structure<br>Goal &#8211; Understand the PI plan for the entire Solution team<br>Input &#8211; Program PI objectives from all ARTs; Train board and risks<br>Output &#8211; Consolidated solution train PI objectives<\/p>\n\n\n\n<p>Solution demo<br>Major event for the life of the solution. E.g. Boeing getting a plane off the ground.<\/p>\n\n\n\n<p>Solution Train Inspect &amp; Adapt<br>Consists of three parts:<br>1) Solution Demo<br>2) Retrospective<br>3) Problem-solving workshop<\/p>\n\n\n\n<p>Solution<br>Uniquely associated with one Value Stream. It is defined by Solution Intent.<\/p>\n\n\n\n<p>Capability<br>Describes the higher level behavior of a solution<\/p>\n\n\n\n<p>Backlog Matching &#8211; Solution Epic<br>One Solution Train across multiple PIs<\/p>\n\n\n\n<p>Backlog Matching &#8211; Story<br>One team, one interation<\/p>\n\n\n\n<p>Backlog Matching &#8211; Program Epic<br>One ART across multiple PIs<\/p>\n\n\n\n<p>Backlog Matching &#8211; Capability<br>One Solution Train within one PI<\/p>\n\n\n\n<p>Backlog Matching &#8211; Portfolio Epic<br>Multiple Value Streams and multiple PIs<\/p>\n\n\n\n<p>Backlog Matching &#8211; Feature<br>One ART within one PI<\/p>\n\n\n\n<p>Solution Intent<br>Single source of truth as to the intended and actual behavior of the solution<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Record and communicate requirements<\/li>\n\n\n\n<li>Facilitate continuous exploration<\/li>\n\n\n\n<li>Align the customer<\/li>\n\n\n\n<li>Support compliance<\/li>\n<\/ul>\n\n\n\n<p>Move from variable to fixed solution intent<br>Preserve flexibility to enable evolution towards optimum solution alternative<\/p>\n\n\n\n<p>Purpose of Business Agility<br>Creating the right solutions for the right customers at the right time<\/p>\n\n\n\n<p>What do you need to balance in Agile Product Delivery?<br>Balance execution focus with a customer focus<\/p>\n\n\n\n<p>What are the 3 dimensions of agile product delivery?<br>1) Customer Centricity \/ Design Thinking 2) Develop on cadence, release on demand 3) DevOps and the continuous delivery pipeline<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Leading safe certification exam questions and answers pdfLeading safe certification exam questions and answersLeading safe certification exam questionsLeading safe certification exam answers pdfLeading safe certification exam answersleading safe exam questionssafe agile exam cheat sheetsafe agilist exam What are the core values of SAFe? Traina team of agile teams Value Streama team of trains Value steams [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[],"tags":[],"class_list":["post-110993","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/posts\/110993","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/comments?post=110993"}],"version-history":[{"count":0,"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/posts\/110993\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/media?parent=110993"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/categories?post=110993"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.learnexams.com\/blog\/wp-json\/wp\/v2\/tags?post=110993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}