SAFe Advanced Scrum Master | 93 Questions And Answers Already Graded A+

Agile Architecture - 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) - 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 - 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 - existing code, hardware components, etc., that technically enable nearterm business features Built-in Quality - Practices that ensure that each Solution element, at every increment, meets appropriate quality standards throughout development. Business Owners - 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 - 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 patentsCapabilities - 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