SAFe Advanced Scrum Master

SAFe Advanced Scrum Master Agile Architecture Ans- Agile architecture is a set of values and practices that support the active evolution of the design and architecture of a system, concurrent with the implementation of new business functionality. With this approach, the architecture of a system, even a large one, evolves over time while simultaneously supporting the needs of current users. This avoids Big Up-Front Design (BUFD) and the starting and stopping of stage-gated methods. Agile Release Train (ART) Ans- A long-lived and cross-functional team-of-Agile-teams, which along with other stakeholders, develops and delivers solutions incrementally, using a series of fixed-length Iterations within a Program Increment (PI) timebox. Aligns teams to a common business and technology mission. Agile Team Ans- A cross-functional group of five to ten people who have the ability and authority to define, build, and test some element of Solution value—all in a short Iteration timebox. Specifically, it incorporates the DevTeam, Scrum Master, and Product Owner roles. Architectural Runway Ans- existing code, hardware components, etc., that technically enable near-term business features Built-in Quality Ans- Practices that ensure that each Solution element, at every increment, meets appropriate quality standards throughout development. Business Owners Ans- A small group of stakeholders who have the primary business and technical responsibility for governance, compliance, and Return on Investment for a Solution developed by an Agile Release Train (ART). They are key stakeholders on the ART who must evaluate fitness for use and actively participate in certain ART events. CapEx and OpEx Ans- Capital Expenses and Operating Expenses describe Lean-Agile financial accounting practices in a Value Stream budget. In some cases, CapEx may include capitalized labor associate with the development of intangible assets - such as software, intellectual property, and patents Capabilities Ans- A higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split into multiple features so that they can be implemented in a single PI. Community of Practice (CoP) Ans- An organized group of people with common interests in a specific technical or business domain. They collaborate regularly to share information, improve their skills, and actively work on advancing the general knowledge of the domain. Compliance Ans- A strategy and set of activities and artifacts that allow teams to apply Lean-Agile development methods to build systems that have the highest possible possible quality, while simultaneously assuring they meet any regulatory, industry, or relevant standards. Continuous Delivery Pipeline Ans- CD Pipeline (also referred to as 'pipeline') represents the workflows, activities, and automation needed to provide a continuous release of value to the end user. Continuous Deployment (CD) Ans- The process that takes validated Features from Continuous Integration and deploys them into the production environment, where they are tested and readied for release. It is the third element in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment, and Release on Demand. Continuous Exploration (CE) Ans- The process of constantly exploring market and user needs, and defining a Vision, Roadmap, and set of Features that address those needs. It is the first element in the four-part Continuous Delivery Pipeline, preceding Continuous Integration (CI) Continuous Deployment (CD), and Release on Demand. Continuous Integration (CI) Ans- The process of taking features from the Program Backlog and developing, testing, integrating, and validating them in a staging environment where they are ready for deployment and release. It is the second element in the four-part Continuous Delivery Pipeline. Core Values Ans- The Four Core Values of alignment, Built-In Quality, transparency, and program execution represent the fundamental beliefs that are key to SAFE's effectiveness. These guiding principles represent the fundamental beliefs that are key to SAFe's effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe portfolio. Customers Ans- The ultimate buyer of every Solution. They are an integral part of the Lean-Agile development process and Value Stream and have specific responsibilities in SAFe. Dev Team Ans- A subset of the Agile Team. It consists of the dedicated professionals who can develop and test a story, feature, or component. It typically includes software developers and testers, engineers and other dedicated specialists who are required to complete a vertical slice of functionality. DevOps Ans- DevOps is a mindset, culture, and set of technical practices that stresses communication, collaboration, and close cooperation between Agile development teams and other technology professionals who are necessary for developing, testing, deploying, and maintaining software and systems. Develop on Cadence Ans- A strategy for managing the inherent variability in solution development by making sure important events and activities occur on a regular, predictable schedule. It is an essential method for managing the inherent vaibility of systems development in a flow-based system. Economic Framework Ans- A set of decision rules that aligns everyone to the financial objectives of the Solution, and guides the economic decision-making process. It contains four primary constructs: Lean Budgeting, Epic funding and governance, decentralized economic decision-making, and job sequencing based on the Cost of Delay (CoD). Enablers Ans- Promote the activities needed to extend the architectural runway to support future business functionality. These include exploration, infrastructure, compliance, and architecture development. They are captured in the various backlogs and occur at all levels of the framework. Enterprise Ans- Represents the business entity that has the ultimate strategic, fiduciary, and governance authority for all the Value Streams and Solutions that make up a SAFe portfolio. Enterprise Architect Ans- Fosters adaptive design and engineering practices, and drives strategic architectural initiatives for a SAFe Portfolio. Also facilitates the reuse of ideas, components, services, and proven patterns across various Solutions in a portfolio. Epic Owners Ans- Responsible for coordinating portfolio epics through the Portfolio Kanban system. They define the Epic, its Minimum Viable Product and lean business case, and when approved, facilitate implementation. Essential SAFe configuration Ans- The heart of the Framework and is the simplest starting point for implementation. It is the basic building block for all other SAFe configurations and describes the most critical elements needed to realize the majority of the Framework's benefits. Features Ans- A system service that fulfills a stakeholder need. Each feature includes a Benefit Hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). Foundation Ans- Contains the supporting principles, values, mindset, implementation guidance, and leadership roles needed to successfully deliver value at scale. Full SAFe configuration Ans- The most comprehensive version of the Framework. It supports enterprises that build and maintain large integrated solutions, which require hundreds of people enterprises that build and maintain large integrated solutions, which require hundreds of people or more, and includes all levels of SAFe: Team, program, large solution, and portfolio. In the largest enterprises, multiple instances of various SAFe configurations may be required. Innovation and Planning Iteration Ans- Occurs every PI and serves multiple purposes. It acts as an estimating buffer for meeting PI objectives, as well as providing dedicated time for innovation, continuing education, and PI planning and Inspect and Adapt (I&A) events. Inspect & Adapt (I&A) Ans- A significant event, held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated. Teams then reflect, and identify improvement backlog items via a structured, problem-solving workshop. Iteration Ans- A basic building block of Agile development. Each iteration is a standard, fixed-length timebox, during which Agile teams deliver incremental value in the form of working, tested software and systems. They may last from one to four week, with two weeks as the suggested and most common duration. Iteration Execution Ans- How Agile teams manage their work throughout the iteration timebox, resulting in a high-quality, working, tested system increment. Iteration Goals Ans- Iteration goals are a high-level summary of the business and technical goals that the team and Product Owner agree to accomplish in an iteration. In SAFe, iteration goals are integral to the effective coordination of an Agile Release Train as a self-organizing, self-managing team of teams. Iteration Planning Ans- An event where all team members determine how much of the team backlog they can commit to delivering during an upcoming iteration. The team summarizes the work as a set of committed iteration goals. Iteration Retrospective Ans- A regular meeting where Agile Team members discuss the results of the iteration, review their practices, and identify ways to improve. Iteration Review Ans- A cadence-based event where each team inspects the increment at the end of every iteration to assess progress, and then adjusts its backlog for the next iteration. Large Solution Level Ans- Contains the roles, artifacts and processes needed to build large and complex solutions. This includes a stronger focus on capturing requirements in Solution Intent, the coordination of multiple Agile Release Trains (ARTs) and Suppliers, and the need to ensure compliance with regulations and standards. Large Solution SAFe configuration Ans- For developing the largest and most complex solutions that typically require multiple Agile release trains ans Suppliers, but do not require portfolio-le