SCALING: SAFe 4.6 Flashcards
learning something new and interesting
What is the connection between feedback and optimum batch size?
A. Lack of feedback contributes to higher holding cost
B. Feedback and batch size are generally not connected
C. Small batch sizes enable faster feedback with lower transaction costs
D. Large batches reduce transaction cost and provide a higher return on investment
C. Small batch sizes enable faster feedback with lower transaction costs
source: Sample test: SAFe 4 Agilist
What is one key reason for keeping the test data for automated tests under version control?
A. For reporting and auditing purposes
B. Version control is required for quality standards
C. All enterprise assets must be under version control
D. If test data gets out of sync, automated tests may not properly execute
D. If test data gets out of sync, automated tests may not properly execute
source: Sample test: SAFe 4 Agilist
What is the primary goal of decentralized decision-making? A. Reduce Cost of Delay B. Resolve dependencies C. Enable faster flow of value D. Increase alignment
C. Enable faster flow of value
source: Sample test: SAFe 4 Agilist
What does SAFe® Principle #3, "Assume variability; preserve options," enable? A. Better economic results B. Specification traceability C. Up front design of systems D. Stronger Definition of Done
A. Better economic results
source: Sample test: SAFe 4 Agilist
What is a result of shorter queue lengths? A. Lower quality B. Increased risk C. Less variability D. Longer cycle times
C. Less variability
source: Sample test: SAFe 4 Agilist
Which statement is most accurate about the Program Vision?
A. It expresses the strategic intent of the Program
B. It drives the allocation of budget for the Agile Release Train
C. It summarizes the team PI Objectives for the current Program Increment
D. It provides an outline of the Features for the next three Program Increments
A. It expresses the strategic intent of the Program
source: Sample test: SAFe 4 Agilist
What Definition of Done is required for the Iteration Review? A. Release B. Team Increment C. System Increment D. Solution Increment
B. Team Increment
source: Sample test: SAFe 4 Agilist
What is the primary purpose of Strategic Themes?
A. Determine the order in which Epics should be executed
B. Drive incremental implementation across the enterprise
C. Connect the portfolio to the enterprise business strategy
D. Define the sequence of steps used to deliver value to the customer
C. Connect the portfolio to the enterprise business strategy
source: Sample test: SAFe 4 Agilist
An Epic spanning two PIs was approved for implementation. What is the optimum implementation path from a Lean-Agile perspective?
A. Implement the Epic across the same number of PIs as it took to develop
B. Report the percentage completed to the key stakeholders at every PI boundary
C. Demonstrate the progress to the key stakeholders after two PIs and have them accept the epic
D. Demonstrate the progress to key stakeholders after first PI and make a decision how to proceed with the Epic in the second PI
D. Demonstrate the progress to key stakeholders after first PI and make a decision how to proceed with the Epic in the second PI
source: Sample test: SAFe 4 Agilist
What backlog items are part of the Solution Backlog? A. Benefits B. Features C. Capabilities D. User Stories
C. Capabilities
source: Sample test: SAFe 4 Agilist
What is Agile Architecture?
Agile Architecture is a set of values and practices that support active evolution of the design and architecture of a system, while implementing new system capabilities.
In SAFe 4.5, Agile Architecture, while still an element of Solution Intent, has been moved off the big picture and into the guidance page. Agile Architecture is also covered briefly in Built-in Quality.
source: Scaled Agile Framework glossary 4.5, “01 Whats New in SAFe 4.5 article.pdf”
What is an Agile Release Train (ART)?
The Agile Release Train (ART) is 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. The ART aligns teams to a common business and technology mission.
source: Scaled Agile Framework glossary 4.5
What is an Agile Team?
The SAFe Agile Team is a cross-funtional 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, the SAFe Agile Team incorporates the DevTeam, Scrum Master, and Product Owner roles.
source: Scaled Agile Framework glossary 4.5
What is an Architectural Runway?
The Architectural Runway consists of the existing code, components and technical infrastructure necessary to support implementation of prioritized, near-term features, without excessive redesign and delay.
source: Scaled Agile Framework glossary 4.5
What is meant by “Built-in Quality” in SAFe?
Built-in Quality practices ensure that each Solution element, at every increment, meets appropriate quality standards throughout development.
Quality is built in at the lowest level, at the team level, along these five dimensions:
flow architecture and design quality code quality system quality release quality
source: Scaled Agile Framework glossary 4.5, and Lesson 6 video, What’s new in SAFe 4.0, What’s New in SAFe 4.6?
Who are the Business Owners in SAFe?
Business Owners are a small group of stakeholders who have the primary business and technical responsibility for governance, compliance, and Return on Investent 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.
source: Scaled Agile Framework glossary 4.5
How are Features and Capabilities defined in SAFe? What is the difference between them?
A Feature is a system service that fulfills a stakeholder need. Each feature includes a benefits 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).
A Capability is a higher-level solution behavior that typically spans multiple Agile Release Trains (ARTs). They are sized and split into multiple features so that they can be implemented in a single PI.
Features and Capabilities are defined using the same components, and in smaller solutions, they are one and the same (Capabilities are not needed in a smaller solution, instead Features are defined as end-to-end capabilities of a system)
source: Scaled Agile Framework glossary 4.5, and Lesson 4 video, What’s new in SAFe 4.0, https://www.scaledagileframework.com/features-and-capabilities/
What is CapEx and OpEx in SAFe?
Capital Expenses (CapEx) and Operating Expenses (OpEx) describe Lean-Agile financial tracking practices in a Value Stream budget. In some cases, CapEx may include capitalized labor associated with the development of intangible assets – such as software, intellectual property, and patents.
source: Scaled Agile Framework glossary 4.5
CoP
Communities of Practice (CoPs)
Communities of Practice (CoPs) are organized groups of people who have a common interest in a specific technical or business domain. They collaborate regularly to share information, improve their skills, and actively work to advance the general knowledge of the domain.
source: Scaled Agile Framework glossary 4.5
Explain what Compliance is, in SAFe
In SAFe, Compliance refers to a strategy, and a set of activities and artifacts that allow teams to apply Lean-Agile development methods to build systems that have the highest possible quality, while simultaneously assuring they meet any regulatory, industry, or other relevant standards.
In SAFe 4.5, Compliance is now part of Solution Intent, and describes how to achieve high quality results while meeting regulatory and industry requirements using Lean-Agile development.
source: Scaled Agile Framework glossary 4.5, “01 Whats New in SAFe 4.5 article.pdf”
What is CD in SAFe?
Continuous Deployment (CD) is 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 (CD) • Release on Demand
source: Scaled Agile Framework glossary 4.5
What is CE in SAFe?
Continuous Exploration (CE) is a process of constantly exploring market and user needs, and defining a
Vision,
Roadmap, and
a set of Features that address those needs.
It is the first element in the four-part Continuous Delivery Pipeline
source: Scaled Agile Framework glossary 4.5
Name the four parts of the Continuous Delivery Pipeline
Four-part Continuous Delivery Pipeline: • Continuous Exploration (CE) • Continuous Integration (CI) • Continuous Deployment (CD) • Release on Demand
source: Scaled Agile Framework glossary 4.5
What is CI in SAFe?
Continuous Integration (CI) is 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 join the four-part Continuous Delivery Pipeline.
source: Scaled Agile Framework glossary 4.5
What are the four Core Values in SAFe?
The four Core Values are • Alignment • Built-in Quality • Transparency • Program execution
Thee guiding principles help dictate behavior and action for everyone who participates in a SAFEe portfolio.
source: Scaled Agile Framework glossary 4.5, also in 4.6
How are Customers defined in SAFe?
Customers are the ultimate economic buyer of every Solution They are an integral part of the Lean-Agile development process and Value Stream, and have specific responsibilities in SAFe.
source: Scaled Agile Framework glossary 4.5
What is the Dev Team in SAFe?
The Dev Team is a subset of the Agile Team. It consist s 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.
source: Scaled Agile Framework glossary 4.5
Define DevOps. What are the three components of DevOps in SAFe?
DevOps is
- a mindset,
- a culture, and
- a set of technical practices (e.g, CALMR automation of the delivery pipeline, lean flow, measurement.
DevOps is an agile approach to bridge the gap between development and operations to deliver value faster and more reliably.
DevOps is a capability in every Agile Release Train.
source: Scaled Agile Framework glossary 4.5, and What’s New in SAFE 4.5 presentation
Develop on Cadence
Develop on Cadence is a strategy for managing the inherent variability in solution development by making sure important events and activities occur on a regular, predictable schedule.
“Develop on Cadence. Release on Demand.”
source: Scaled Agile Framework glossary 4.5, https://www.scaledagileframework.com/release-on-demand/
What is meant by Economic Framework in SAFe?
The economic Framework is a set of decision rules that aligns everyone to the financial objectives of the Solution, and guides the economic decision-making process in SAFe.
source: Scaled Agile Framework glossary 4.5
What are the four primary constructs of Economic Framework in SAFe?
Economic Framework contains four primary constructs:
- Lean Budgeting
- Epic funding and governance
- Decentralized economic decision-making
- Job sequencing based on the Cost of Delay (CoD)
source: Scaled Agile Framework glossary 4.5
CoD
Cost of Delay
Three primary elements contribute to the Cost of Delay:
- User-business value – Do our users prefer this over that? What is the revenue impact on our business? Is there a potential penalty or other adverse consequences if we delay?
- Time criticality – How does the user/business value decay over time? Is there a fixed deadline? Will they wait for us or move to another solution? Are there Milestones on the critical path impacted by this?
- Risk reduction-opportunity enablement value – What else does this do for our business? Does it reduce the risk of this or a future delivery? Is there value in the information we will receive? Will this feature open up new business opportunities?
Cost of delay = business value + time value + RR/OE value
source: https://www.scaledagileframework.com/wsjf/
What are Enablers in SAFe?
Enablers promote the activities needed to extend the architectural runway to support future business functionality.
These include
• Exploration - research, prototyping, etc.
• Architectural - building the Architectural Runway
• Infrastructure - build, enhance, and automate the development, testing, and deployment environments … Continuous Delivery Pipeline
• Compliance
They are captured in the various backlogs and occur at all levels of the framework.
source: Scaled Agile Framework glossary 4.5, https://www.scaledagileframework.com/enablers/
What is meant by Enterprise in SAFe?
The Enterprise 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.
source: Scaled Agile Framework glossary 4.5
Enterprise Architect
The Enterprise Architect
• fosters adaptive design and engineering practices, and
• drives strategic architectural initiatives for a SAFe Portfolio.
• facilitate the reuse of ideas, components, services, and proven patterns across various solutions in a portfolio.
source: Scaled Agile Framework glossary 4.5
Epic Owners
Epic Owners are 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.
source: Scaled Agile Framework glossary 4.5
Innovation and Planning Iteration
The Innovation and Planning Iteration 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
source: Scaled Agile Framework glossary 4.5
I&A
The Inspect & Adapt is a significatnt 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.
source: Scaled Agile Framework glossary 4.5
Iteration
Iterations are the 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 weeks, with two weeks as the suggested and most common duration.
source: Scaled Agile Framework glossary 4.5
Large Solution Level
The Large Solution Level 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.
source: Scaled Agile Framework glossary 4.5
Lean Budgets
Lean Budgets is a set of practices that minimizes overhead by funding and empowering Value Streams rather than projects, while maintaining financial and fitness-for-use governance. This is achieved through objective evaluation of working systems, prudent management of Epic investments, and dynamic budget adjustments.
source: Scaled Agile Framework glossary 4.5
LPM
Lean Portfolio Management (LPM) (formerly “Program Portfolio Management (PPM)”) is a function that represents the individuals with the highest-level of decision-making and financial accountability for a SAFe portfolio. This group is responsible for three primary areas:
• Strategy and investment funding
• Agile program guidance
• Lean governance
source: Scaled Agile Framework glossary 4.5, “01 Whats New in SAFe 4.5 article.pdf”
Lean UX
Lean User Experience (Lean UX) design is a mindset, a culture, and a process that embraces Lean-Agile methods. It implements functionality in minimum viable increments, and determines success by measuring results against an outcome hypothesis.
source: Scaled Agile Framework glossary 4.5
Lean and Agile Principles
SAFe is based on NINE immutable, underlying Lean and Agile Principles. These are the fundamental tenets, basic truths, and economic premises that inspire and inform the roles and practices that make SAFe effective.
source: Scaled Agile Framework glossary 4.5
Lean-Agile Leaders
Lean-Agile Leaders are lifelong learners who are responsible for the successful adoption of SAFe and the results it delivers. They empower and help teams build better systems by learning, exhibiting, teaching and coaching SAFe’s Lean-Agile principles and practices.
source: Scaled Agile Framework glossary 4.5
Lean-Agile Mindset
The Lean-Agile Mindset is the combination of beliefs, assumptions and actions of SAFe leaders and practitioners who embrace the concepts of the Agile Manifesto and Lean thinking. It’s the personal, intellectual and leadership foundation for adopting and applying SAFe’s principles and practices.
also, it is the “House of Lean” plus the “Agile Manifesto”
source: Scaled Agile Framework glossary 4.5. also, What’s New in SAFe 4.0? (SAFe 4.0 Upgrade Training v5 6/9/2016) with Dean Leffingwell, Alex Yakyma, Richard Knaster and Inbar Oren
Metrics
Metrics are agreed-upon measures used to evaluate how well the organization is progressing toward the portflio, large solution, program, and the team’s business and technical objectives.
source: Scaled Agile Framework glossary 4.5
What are the three types of Milestones in SAFe?
Milestones are used to track progress toward a specific goal or event. There are three types of SAFe milestones.
• Program Increment
• Fixed-date, and
• Learning milestones
source: Scaled Agile Framework glossary 4.5
MBSE
Model Based Systems Engineering (MBSE) is the practice of developing a set of related system models that help define, design and document a system under development. These models provide an efficient way to explore, update, and communicate system aspects to stakeholders, while significantly reducing or eliminating dependence on traditional documents.
In practice, engineers use models to gain knowledge (e.g. performance) and to serve as a guide for system implementation (e.g. SysML, UML). In some cases, they use them to directly build the actual implementation (e.g. electrical CAD, mechanical CAD).
source: Scaled Agile Framework glossary 4.5, https://www.scaledagileframework.com/model-based-systems-engineering/
NFRs
Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs.
source: Scaled Agile Framework glossary 4.5
Portfolio Backlog
The Portfolio Backlog is the highest-level backlog in SAFe. It provides a holding mechanism for the upcoming Business and Enabler Epics intended to create a comprehensive portfolio solution set, one that provides the competitive differentiation and/or operational efficiencies necessary to address the Strategic Themes and facilitate business success.
source: Scaled Agile Framework glossary 4.5
Portfolio Kanban
The portfolio Kanban is a method used to visualize and manage the analysis, prioritization and flow of portfolio epics from ideation to implementation and completion.
source: Scaled Agile Framework glossary 4.5
Portfolio Level
The SAFe Portfolio Level contains the guidance, practices and roles needed to initiate and govern a set of development value streams. It provides the strategy and investment funding for people and resources, Agile program guidance, and Lean governance.
source: Scaled Agile Framework glossary 4.5
Pre- and Post-PI Planning
Pre- and Post-PI (Program Increment) planning events are used to prepare for, and follow-up after, PI Planning for Agile Release Trains (ARTs) and Suppliers in a Solution Train.
source: Scaled Agile Framework glossary 4.5
Product and Solution Management
Product and Solution Managers are responsible for identifying customer needs, prioritizing features and developing the program Vision and Roadmap.
The Product Management role has content authority for the Program Backlog.
Solution Management has the content authority for the Solution Backlog. They work with Customers to understand their needs, create the Solution vision and Roadmap, define requirements, and guide work through the Solution Kanban.
source: Scaled Agile Framework glossary 4.5
PI
A Program Increment (PI) is a timebox in which an Agile Release Train (ART) delivers incremental value in the form of working, tested software and systems. PIs are typically eight to twelve weeks long, and the most common pattern for a PI is four development iterations, followed by one Innovation and Planning (IP) iteration.
source: Scaled Agile Framework glossary 4.5
PI Planning
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 common mission and vision.
source: Scaled Agile Framework glossary 4.5
Program Level
The Program Level contains the roles and activities needed to continuously deliver solutions via an Agile Release Train (ART).
source: Scaled Agile Framework glossary 4.5
Program and Solution Backlog
The Program Backlog is the final state in the Program Kanban, which is also the last state of Continuous Exploration. It’s the holding area for a prioritized list of Features that have been analyzed and are intended to address user needs and deliver business benefits for a single Agile Release Train (ART). It also contains the Enabler features necessary to build the Architectural Runway.
The Solution Backlog is the holding area for upcoming Capabilities and Solution enablers, each of which can span multiple ARTs, and are intended to advance the Solution and build its architectural runway.
source: Scaled Agile Framework glossary 4.5
Program and Solution Kanban
The Program and Solution Kanban systems are methods used to visualize and manage the flow of value from ideation to analysis, implementation, and release. They support the flow of features and capabilities through the full Continuous Delivery Pipeline of Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand.
source: Scaled Agile Framework glossary 4.5
Refactoring
Refactoring is the activity of improving the internal structure or operation of a code or component without changing its external behavior.
source: Scaled Agile Framework glossary 4.5
RTE and STE
The Release Train Engineer (RTE) is a servant leader and coach for the Agile Release Train (ART).
The RTE’s major responsibilities are to facilitate the major events and processes, and assist the teams in delivering value. RTEs communicate with stakeholders, escalate impediments, help manage risk, and drive continuous improvement.
The Solution Train Engineer (STE) (formerly known as the “Value Stream Engineer”) plays an equivalent role for a Solution Train, facilitating and guiding the work of all ARTs and Suppliers in the ValueStream.
source: Scaled Agile Framework glossary 4.5
Release on Demand
The process by which features deployed into production are released incrementally or immediately to Customers based on market demand.
The Program Kanban is used by the ART to facilitate the flow of features through the Continuous Delivery Pipeline.
source: Scaled Agile Framework glossary 4.5, “01 Whats New in SAFe 4.5 article.pdf”
What is the Roadmap and what is its benefit?
The Roadmap is a schedule of events and milestones that communicate planned Solution deliverables over a timeline. It includes commitments for the planned Program Increment (PI) and offers visibility into the deliverables forecasted for the next few PIs.
The SAFe Implementation Roadmap gives CIOs and leadership confidence.
source: Scaled Agile Framework glossary 4.5
SAFe Implementation Roadmap
The SAFe Implementation Roadmap consists of an overview graphic and a twelve-article series that describes a strategy and an ordered set of activities that have proven to be effective in successfully implementing SAFe.
source: Scaled Agile Framework glossary 4.5
SPC
SAFe Program Consultants (SPCs) are change agents who combine their technical knowledge of SAFe with an intrinsic motivation to improve their company’s software and systems development processes. They play a critical role in successfully implementing SAFE. SPCs come from numerous internal or external roles, including business and technology leaders, portfolio/program/project managers, process leads, architects, analysts, and consultants.
source: Scaled Agile Framework glossary 4.5
Scrum Master
SAFe Scrum Masters are servant leaders and coaches for an Agile team. The help educate the team in Scrum, eXtreme Programming, Kanban and SAFe, ensuring that the agreed Agile process is being followed. They also help remove impediments, and foster and environment for high-performing team dynamics, continuous flow, and relentless improvement.
source: Scaled Agile Framework glossary 4.5
ScrumXP
ScrumXP is a lightweight process for cross-functional, self-organized teams to deliver value within the context of SAFe. ScrumXP combines the power of Scrum project management practices with extreme programming technical practices.
source: Scaled Agile Framework glossary 4.5, https://www.scaledagileframework.com/scrumxp/
