SAFe-Agilist Dumps SAFe-Agilist Braindumps
SAFe-Agilist Real Questions SAFe-Agilist Practice Test SAFe-Agilist Actual Questions
SAFe-Agilist
https://killexams.com/pass4sure/exam-detail/SAFe-Agilist
Within the SAFE principles (10), what is related to this principle: #3, "Assume variability; preserve options,"?
Stronger Definition of Done
Specification traceability
Better economic results
Up front design of systems
Explanation:
Solution development is an inherently uncertain process. Technical variability and market variability are present throughout the development process. Innovative new systems have, by definition, never been developed before, so there is no guaranteed path to success. If there were, it wouldnât be innovation. Thatâs why we love this business. To assure forward progress, system developers are inclined to reduce variability as quickly as possible. The more deterministic things are, the better we feel. Thatâs just human nature. It seems that the more we think we know and have already decided, the further along we think we are. And thatâs true up to a point, but even then variability is a constant presence. Variability is inherently neither bad or goodâit just is what it is. But itâs the economics associated with the timing and type of variability that determines outcomes. The goal is to manage variability, and to preserve options, providing the controls and flexibility teams need to build great solutions.
The product backlog contains 60 story points. The team velocity is around 20 story points per iteration. How many Iterations would it take to finish the backlog?
1 Iteration
2 Iterations
4 Iterations
3 Iterations
When is Continuous Exploration happening?
On demand, based on market rhythms and events
Every Iteration
During the IP Iteration in preparation for PI Planning
In the first PI Iteration to prepare for work in Iteration 2 and deployment in Iteration 3
Explanation:
Continuous Exploration (CE) is the process that drives innovation and fosters alignment on what should be built by continually exploring market and customer needs, and defining a Vision, Roadmap, and set of Features for a Solution that addresses those needs.
Who is facilitating the Scrum of Scrums?
Business Owners
Scrum Master
Product Owner
Release Train Engineer
Explanation:
The Release Train Engineer (RTE) typically facilitates a weekly (or more frequently, as needed) Scrum of Scrums (SoS) event. The SoS helps coordinate the dependencies of the ARTs and provides visibility into progress and impediments. The RTE, representatives from each team (often the Scrum Master), and others (where appropriate) meet to review their progress toward milestones and PI objectives, and dependencies among the teams. The event is timeboxed for 30-60 minutes and is followed by a âmeet afterâ where individuals who want to do a deeper dive into specific problems can remain behind.
What are the three inputs to start PI Planning?
A set of PI Objectives
Product/Solution Vision
Business context
Solution Roadmap
Top-10 Features
Ready user stories
Explanation:
Program Increment (PI) Planning is a cadence-based, face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and Vision. PI planning is essential to SAFe: If you are not doing it, you are not doing SAFe. Inputs to PI planning include: Business context (see âcontent readinessâ below) Roadmap and vision Top 10 Features of the Program Backlog A successful PI planning event delivers two primary outputs: Committed PI objectives C A set of SMART objectives that are created by each team with the business value assigned by the Business Owners. Program board C Highlighting the new feature delivery dates, feature dependencies among teams and relevant Milestones.
How feedback is connected with optimum batch size?
Feedback and batch size are generally not connected
Small batch sizes enable faster feedback with lower transaction costs
Large batches reduce transaction cost and provide a higher return on investment
Lack of feedback contributes to higher holding cost
Explanation:
The economically optimal batch size depends on both the holding cost (the cost for delayed feedback, inventory decay, and delayed value delivery) and the transaction cost (the cost of preparing and implementing the batch). To improve the economics of handling smaller batchesâand thus increase throughputâteams 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, automating the build environment, automated regression testing and more. (This is a primary purpose of implementing DevOps.)
What is defining the best the Program Vision?
It provides an outline of the Features for the next three Program Increments
It summarizes the team PI Objectives for the current Program Increment
It drives the allocation of budget for the Agile Release Train
It expresses the strategic intent of the Program
Explanation:
When using Full SAFe or Large Solution SAFe, each ART will likely have its own vision, detailing the direction of the specific capabilities or subsystems that it produces. This vision should be tightly coupled to the solution vision it supports.
What kind of items is describing behaviors in the Large Solution view?
Capabilities
User Stories
Features
Benefits
Explanation:
Large Solution SAFe describes additional roles, practices, and guidance to build and evolve the worldâs largest applications, networks, and cyber-physical systems. Large Solution SAFe (Figure 1) configuration includes the following constructs: The Essential SAFe configuration An additional competency, Enterprise Solution Delivery that describes how to apply Lean-Agile principles and practices to the specification, development, deployment, operation, and evolution of the worldâs largest and most sophisticated software applications, networks, and cyber-physical systems. The large solution level roles, artifacts, and events. The full spanning palette A connection to the Enterprise or Government entity the solution supports The following Large Solution SAFe artifacts help coordinate multiple ARTs and suppliers: Capabilities C Capabilities are a higher-level solution behavior that typically spans multiple ARTs. They are sized and split into multiple features so that they can be implemented in a single PI. Enabler CapabilitiesC Enabler capabilities support the activities needed to extend the Architectural Runway to provide future business functionality and include exploration, architecture, infrastructure, and compliance. Solution Epics C Solution Epics are epics implemented by a single Solution Train. Nonfunctional Requirements (NFRs) C NFRs define system attributes such as security, reliability, performance, maintainability, scalability, and usability. These are incorporated in solution intent. Solution Backlog C Solution Backlog is the holding area for upcoming capabilities and enablers, each of which can span multiple ARTs and are intended to advance the solution and build its architectural runway.
What are the three pillars of Scrum: transparency, inspection ...?
Adaptation
Collaboration
Self-organization
Respect
Explanation:
Scrum pillars are Transparency, Inspection and Adaptation.
What is SAFE?
SAFE is a framework to implement Devops
SAFE is based of proven, integrated Lean practices and principles, Agile and Devops
SAFE is a tool for budget management
Explanation:
Scaled Agile Framework® (SAFe®) empowers complex organizations to achieve the benefits of Lean-Agile software and systems development at scale. SAFe is the worldâs leading framework for scaling Agile across the enterprise. Used by hundreds of the worldâs largest organizations, SAFe sustains and drives faster time-to-market, dramatic increases in productivity and quality, and improvement in employee engagement. SAFe is designed to help businesses continuously and more efficiently deliver value on a regular and predictable schedule. It provides a knowledge base of proven, integrated principles and practices to support enterprise agility.
What is the foundation of the customer-centric?
Market and user research
Product lifecycle
Customer value
Whole product solution
Explanation:
The foundation of the customer-centric enterprise is market and user research that creates actionable insights into the problems customers face, the solution requirements, and the solution context. Market research tends to drive strategy; user research tends to drive design. Research activities occur continuously and are directly supported through Continuous Exploration in the Continuous Delivery Pipeline, product telemetry data, and the feedback loops that exist between the solution and the Solution Context.