SCALING: SAFe 4.6 Flashcards
learning something new and interesting
1
Q
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
A
C. Small batch sizes enable faster feedback with lower transaction costs
source: Sample test: SAFe 4 Agilist
2
Q
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
A
D. If test data gets out of sync, automated tests may not properly execute
source: Sample test: SAFe 4 Agilist
3
Q
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
A
C. Enable faster flow of value
source: Sample test: SAFe 4 Agilist
4
Q
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
A. Better economic results
source: Sample test: SAFe 4 Agilist
5
Q
What is a result of shorter queue lengths? A. Lower quality B. Increased risk C. Less variability D. Longer cycle times
A
C. Less variability
source: Sample test: SAFe 4 Agilist
6
Q
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
A. It expresses the strategic intent of the Program
source: Sample test: SAFe 4 Agilist
7
Q
What Definition of Done is required for the Iteration Review? A. Release B. Team Increment C. System Increment D. Solution Increment
A
B. Team Increment
source: Sample test: SAFe 4 Agilist
8
Q
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
A
C. Connect the portfolio to the enterprise business strategy
source: Sample test: SAFe 4 Agilist
9
Q
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
A
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
10
Q
What backlog items are part of the Solution Backlog? A. Benefits B. Features C. Capabilities D. User Stories
A
C. Capabilities
source: Sample test: SAFe 4 Agilist
11
Q
What is Agile Architecture?
A
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”
12
Q
What is an Agile Release Train (ART)?
A
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
13
Q
What is an Agile Team?
A
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
14
Q
What is an Architectural Runway?
A
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
15
Q
What is meant by “Built-in Quality” in SAFe?
A
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?
16
Q
Who are the Business Owners in SAFe?
A
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
17
Q
How are Features and Capabilities defined in SAFe? What is the difference between them?
A
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/
18
Q
What is CapEx and OpEx in SAFe?
A
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
19
Q
CoP
A
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
20
Q
Explain what Compliance is, in SAFe
A
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”
21
Q
What is CD in SAFe?
A
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
22
Q
What is CE in SAFe?
A
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
23
Q
Name the four parts of the Continuous Delivery Pipeline
A
Four-part Continuous Delivery Pipeline: • Continuous Exploration (CE) • Continuous Integration (CI) • Continuous Deployment (CD) • Release on Demand
source: Scaled Agile Framework glossary 4.5
24
Q
What is CI in SAFe?
A
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
25
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
26
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
27
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
28
Define DevOps. What are the three components of DevOps in SAFe?
DevOps is
1. a mindset,
2. a culture, and
3. 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
29
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/
30
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
31
What are the four primary constructs of Economic Framework in SAFe?
Economic Framework contains four primary constructs:
1. Lean Budgeting
2. Epic funding and governance
3. Decentralized economic decision-making
4. Job sequencing based on the Cost of Delay (CoD)
source: Scaled Agile Framework glossary 4.5
32
CoD
Cost of Delay
Three primary elements contribute to the Cost of Delay:
1. 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?
2. 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?
3. 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/
33
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/
34
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
35
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
36
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
37
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
38
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
39
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
40
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
41
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
42
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"
43
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
44
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
45
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
46
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
47
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
48
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
49
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/
50
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
51
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
52
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
53
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
54
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
55
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
56
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
57
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
58
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
59
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
60
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
61
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
62
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
63
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"
64
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
65
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
66
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
67
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
68
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/
69
Set-based Design
Set-based Design is a practice that keeps requirements and design options flexible for as long as possible during the development process. Instead of teams choosing single "point" solutions upfront, set-based design identifies and simultaneously explores multiple options and eliminates poorer choices over time. It enhances flexibiity in the design process, commits to technical solutions only after validating assumptions, and produces better economic outcomes.
Set-based design is a fundamental construct of the SAFe Large Solution level.
See also Set-Based Concurrent Engineering (SBCE)
sources: Scaled Agile Framework glossary 4.5, https://www.scaledagileframework.com/solution/
70
Shared Services
Shared Services represents the specialty roles, people and services necessary for the success of an Agile Release Train (ART) or Solution Train, but that cannot be dedicated full-time.
source: Scaled Agile Framework glossary 4.5
71
Solution
Each Value Stream produces one or more solutions, which are products, services, or systems delivered to the Customer, whether internal or external to the enterprise.
source: Scaled Agile Framework glossary 4.5
72
System and Solution Architect/Engineer
The System Architect/Engineering role represents an individual or small team that defines a common technical and architectural vision for the Solution under development. The participate in defining the system, subsystems, and interfaces; validate technology assumptions; and evaluate alternatives. They help align the Solution Train and the Agile Release Train (ART) to a common technological and architectural vision.
source: Scaled Agile Framework glossary 4.5
73
Solution Context
Solution Context identifies critical aspects of the operational environment for a Solution It provides an essential understanding of requirements, usage, installation, operation, and support of the solution itself. Solution context also heavily influences opportunities and constraints for Release on Demand.
source: Scaled Agile Framework glossary 4.5
74
Solution Demo
The Solution Demo is where the results of development efforts from the Solution Train (e.g., multiple Agile Release Trains (ARTs) and the contributions from Suppliers) are integrated, evaluated, and made visible to customers and other stakeholders.
source: Scaled Agile Framework glossary 4.5
75
Solution Train
The Solution Train is the SAFe organizational construct used to build large and complex Solutions that require the coordination of multiple Agile Release Trains (ARTs), as well as the constributions of Suppliers. The Solution Train aligns ARTs to a shared business and technology mission using a common Solution Vision, Backlog and Roadmap, and an aligned Program Increment (PI) cadence.
"The Solution Train is a train of agile trains"
source: Scaled Agile Framework glossary 4.5, What's New in SAFe 4.5 screencast
76
Spikes
Spikes are a type of exploration Enabler story in SAFe. Originally defined within XP, spikes are used for activities such as research, design, investigation, exploration, and prototyping.
source: Scaled Agile Framework glossary 4.5
77
Supplier
A Supplier is an internal or external organization that develops and deliver components, sybsistems or services that help Solution Trains deliver Solutions to their customers.
source: Scaled Agile Framework glossary 4.5
78
System Demo
The System Demo is a significant event that provides an integrated view of new features for the most recent iteration delivered by all the teams in the Agile Release Train (ART). Each demo provides ART stakeholders with an objective measure of progress during a program increment.
source: Scaled Agile Framework glossary 4.5
79
System Team
The System Team is a special Agile team that provides assistance in building and using the Agile development environment, including continuous integration, test automation and continuous deployment. The System Team assists with the integration of assets from Agile teams, performs end-to-end Solution testing where necessary, and assists with deployment and release.
source: Scaled Agile Framework glossary 4.5
80
Team Backlog
The Team Backlog contains user and enabler stories that originate from the program backlog, as well as stories that arise locally from the team's specific context. It can contain other work items as well, representing all the things a team needs to do to advance their portion of the system.
source: Scaled Agile Framework glossary 4.5
81
Team Kanban
```
Team Kanban is a method that helps teams facilitate the flow of value by
• visualizing work flow,
• establishing work-in-process limits,
• measuring throughput, and
• continuously improving their process.
```
source: Scaled Agile Framework glossary 4.5
82
Team Level
The Team Level contains the roles, activities, events and processes through which Agile teams build and deliver value in the context of the Agile Release Train (ART).
source: Scaled Agile Framework glossary 4.5
83
Test-First
Test first is a Built-in Quality practice derived from eXtreme Programming (XP). It focuses on building the tests before the implementation to improve delivery by focus on the results.
Test first includes TDD and ATDD
source: Scaled Agile Framework glossary 4.5
84
Value Stream Coordination
Value Stream Coordination provides guidance for managing dependencies across value streams in a portfolio.
source: Scaled Agile Framework glossary 4.5
85
Value Streams
Value Streams represent the series of steps that an organization uses to build Solutions that provide a continuous flow of value to a customer. SAFe Value Streams are used to define and realize Portfolio business objectives and organize Agile Release Trains (ARTs) to deliver value more rapidly.
* Development Value Streams (Strategic)
* Operational Value Streams (Enablers)
sources: Scaled Agile Framework glossary 4.5, http://projectmanager.org/images/downloads/PDC_2018_Presentations/cindy_lake_safe_in_a_nutshell.pdf
86
Vision
The Vision is a description of the future state of the Solution under development. It reflects customer and stakeholder needs, as well as the features and capabilities propose to meet those needs.
source: Scaled Agile Framework glossary 4.5
87
WSJF: what is it and how is it determined
Weighted Shortest Job First (WSJF) is a prioritization model used to sequence "jobs" (e.g., Features, Capabilities, and Epics) to produce maximum economic benefit. In SAFe, WSJF is estimated as the cost of delay divided by job size. "Job size as first proxy for duration"
"Lowest hanging fruit"
WSJF = Cost of Delay / Job Duration (Job size)
Cost of delay = business value + time value + RR/OE value
Business value = user business value
Time value = time criticality
RR/OE value = Risk Reduction and/or Opportunity Enablement
source: Scaled Agile Framework glossary 4.5, and http://projectmanager.org/images/downloads/PDC_2018_Presentations/cindy_lake_safe_in_a_nutshell.pdf
88
Define Lean Enterprise
The Lean Enterprise is a thriving digital age business that delivers competitive systems and solutions to its customers in the shortest sustainable lead time.
source: What's New in SAFe 4.6 Presentaion
89
What are the four configurations ("levels") of SAFe as of v4.5?
1. Essential SAFe
2. Portfolio SAFe
3. Large Solution SAFe
4. Full SAFe
source: What's New in SAFe 4.5?
90
What is CALMR in SAFe
CALMR is an approach to DevOps.
* Culture (of shared responsibility)
* Automation (of continuous delivery pipeline)
* Lean flow (accelerate delivery through small batches, limiting WIP, providing extreme visibility)
* Measurement ("of everything": of the flow through the pipeline, and through implementing telemetry)
* Recovery (architect and enable low risk releases, establish fast-recovery, fast-reversion, and fast fix-forward)
source: What's New in SAFe 4.5 presentation
91
Name four skills or tools that can be used to architect for "release-ability" and Recovery
1. Dark launches - ability to deploy to a production environment without releasing the functionality to end users
2. Feature toggles technique to facilitate dark launches by implementing toggles in the code, which enables switching between old and new functionality
3. Canary releases - a mechanism for releasing the solution to a specific Customer segment and measuring the results, before expanding and releasing to more Customers.
4. Decouple release elements - e.g., as "value streamlets" such as end-user functionality released every 2 weeks, security updates released on demand, and back-office functionality released every month
Chaos monkey (mentioned in v4.5)
source: What's New in SAFe 4.5 presentation
92
What is an Epic Hypothesis Statement?
The Epic Hypothesis Statement helps prevent people from going too detailed with requirements at the Epic level.
Here is a template for writing an Epic Hypothesis Statement.
```
For
who
the
is a
that
Unlike ,
our solution
```
Anticipated Outcomes hypothesis: ___
Intermediate measures/Leading indicators: ___ (e.g., early innovation accounting measures)
NFRs: ___
source: What's New in SAFe 4.5 presentation, "01 Whats New in SAFe 4.5 article.pdf", What's New in SAFe 4.5 screencast
93
What is meant by decoupling deployment from release?
A solution can be deployed to Production with a feature toggle, for example, and only be released to the end user when it it needed.
source: What's New in SAFe 4.5 presentation
94
What is a value streamlet?
A streamlet is a release element, which is a part of a value stream that can be delivered in isolation, as a small increment without waiting for the full solution.
source: What's New in SAFe 4.5 presentation
95
Telemetry
Telemetry is an automated communications process by which measurements and other data are collected at remote or inaccessible points and transmitted to receiving equipment for monitoring.
The word is derived from Greek roots: tele = remote, and metron = measure.
source: wikipedia
context: metrics in SAFe, from What's New in SAFe 4.5 presentation
96
Chaos monkey and chaos engineering
Chaos engineering is the discipline of experimenting on a software system in production in order to build confidence in the system’s capability to withstand turbulent and unexpected conditions.
Chaos Monkey is responsible for randomly terminating instances in production to ensure that engineers implement their services to be resilient to instance failures.
Chaos Monkey is a tool invented in 2011 by Netflix
source: https://netflix.github.io/chaosmonkey/
97
Benefit hypothesis
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). A Capability is a higher-level solution behavior that typically spans multiple ARTs.
Template:
Feature:
Benefit hypothesis:
Acceptance Criteria:
• ___
• ___
source: scaledagileframework.com,
What's New in SAFe 4.5 screencast
98
Name nine steps in the evolution of common SAFe Lean-Agile Principles (SAFe 4.0)
1. Take an economic view
2. Apply systems thinking
3. Assume variability and preserve options
4. Build incrementally with fast, integrated learning cycles
5. Base milestones on objective evaluation of working systems
6. Visualize and limit WIP, reduce batch sizes, and manage queue lengths
7. Apply cadence, synchronize with cross-domain planning
8. Unlock the intrinsic motivation of knowledge workers
9. Decentralize decision-making
source: 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
99
Define SAFe
```
SAFe is an
• online, freely revealed
• knowledge base of
• proven, integrated success patterns
• for implementing Lean-Agile development at enterprise scale.
```
The first iteration of SAFe was in 2011.
source: 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
100
LSE
Lean Systems Engineering
source: 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
101
What is meant by "assume variability; preserve options"? How is it manifested during development?
"Generate alternative system-level designs and subsystem concepts. Rather than try to pick an early winner, aggressively eliminate alternatives. The designs that survive are your most robust alternatives. —Allen C. Ward"
Use Set-Based Design
Picking a point solution too early in the cone of uncertainty means a team would have less time to adjust/recover if a better point solution is discovered as development progresses.
Attempting to force certainty by freezing requirements and design. The bigger and more technically innovative the system is, the higher the odds are that the agreed starting point was not the best one.
(Allen C. Ward authored "Lean Product and Process Development")
source: https://www.scaledagileframework.com/assume-variability-preserve-options/
102
What is Solution Intent in SAFe?
Solution Intent is the larger purpose for the solution ("build the right thing", or establish "what" to build, before deciding on "how")
Solution Intent is the repository for storing, managing, and communicating the knowledge of current and intended Solution behavior. Where required, this includes both fixed and variable specifications and designs; reference to applicable standards, system models, and functional and nonfunctional tests; and traceability.
Note that this doesn't mean that we are predefining all of the requirements for a solution upfront.
See also Model Based Systems Engineering (MBSE)
https://www.scaledagileframework.com/solution-intent/ and Lesson 4 video, What's new in SAFe 4.0
103
What is the spanning palette
The menu bar at the left of the SAFe map in SAFe 4.5 and above (formerly at the bottom of the SAFe map)
The spanning palette dynamically changes depending upon the configuration chosen.
source: 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, "01 Whats New in SAFe 4.5 article.pdf"
104
What is the Solution?
Each Value Stream produces one or more Solutions, which are products, services, or systems delivered to the Customer, whether internal or external to the Enterprise.
[Everything] in SAFe exits for one purpose: to help development teams continuously deliver solutions that provide value to their customer.
source: https://www.scaledagileframework.com/solution/
105
What does SAFe consist of?
```
Words,
pages,
roles,
activities, and
artifacts
```
source: https://www.scaledagileframework.com/solution/
106
SBCE
Set-Based Concurrent Engineering (SBCE) is an approach where multifunctional team(s) ideate, develop and communicate sets of conceptual solutions in parallel.
As the solutions progress, team(s) build up the understanding, knowledge and evidence about the sets, which permits them to gradually narrow these sets by eliminating inferior or/and infeasible solutions. As they narrow, teams commit to staying within the [overlapping components of] sets so that others can rely on them.
see also Set-Based Design (SBD)
see diagrams at source link
source: http://lean-analytics.org/set-based-concurrent-engineering-sbce-why-should-you-be-interested/
107
SAFE Requirements Model
A comprehensive model for requirements specification. Includes
• ways to express system behaviors for Epics, Capabilities, Features, Stories, Nonfunctional Requirements and more.
• artifacts that can replace the traditional system and requirements specifications withnew paradigms based on Lean-Agile development.
• encourage leaving room for an emerging understanding of intent, not specificity.
See image at source link
source: https://www.scaledagileframework.com/safe-requirements-model/
108
Name the four pillars, and the base and roof of the "House of Lean"
```
Base: Leadership
Four Pillars:
• Respect for people and culture
• Flow
• Innovation
• Relentless improvement
Roof: Value
```
source: 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
109
Explain the difference between budgeting in SAFe and budgeting in traditional project management.
The Lean-Agile enterprise moves from project-based, cost-center accounting to a more streamlined, leaner budget process.
In the new model, the funding is allocated to long-lived Value Streams that produce the Solutions vital to the organization. Once this transition is complete, the cost for each Program Increment (PI) is largely fixed, and scope is varied as necessary. Each value stream budget can then be adjusted over time at PI boundaries, base on the relative value that each provides to the portfolio.
See also Lean Budgets
https://www.scaledagileframework.com/economic-framework/
110
What is meant by "guiding investments by Horizon", in SAFe?
The "Three Horizons of Growth" framework comes from the book "The Alchemy of Growth: Practical Insights for Building the Enduring Enterprise" by Mehrdad Baghai. It provides a structure for companies to manage investments in future growth without neglecting performance in the present. Plotted as curves with x axis = time and y axis = value
Horizon 1 = core businesses, provide greatest profits and cash flow now (but perhaps lower overall value)
Horizon 2 = emerging opportunities, mid-term, could require considerable investment, likely to generate substantial profits over time, mid-value
Horizon 3 = ideas for growth, longer term, and higher value
SAFe uses a model, read left to right, like this:
Horizon 3 = Evaluating
Horizon 2 = Emerging
Horizon 1 = Investing & Extracting Value
Horizon 0 = Retiring
see images at source page
source: https://www.scaledagileframework.com/lean-budgets/
111
What is meant by Sustainably Shortest Lead Time?
TBD
OH on chamgea in SAFe 4.0, lesson 2 foundations
112
explain the difference between operational and development value strems
tbd
113
Value Stream Engineer (VSE)
This is the old term. The new term is Solution Train Engineer.
A servant leader that facilitates and guides the work of all ARTs and suppliers. They have similar responsibilities to an RTE. They help the Solution Train run smoothly by identifying and resolving bottlenecks across the entire solution.
sources: Lesson 4 video, What's new in SAFe 4.0, "01 Whats New in SAFe 4.5 article.pdf"
114
Solution Kanban (formerly "Value Stream Kanban"), and Program Kanban
?? This may have problems, since it was updated in SAFE 4.5 ??
```
Solution Epics (formerly "Value Stream Epics") kanban:
Funnel > Review > Analysis
```
Program kanban:
Funnel > Review > Analysis
Output of Analysis is broken down into epics
The epics become individual Capabilities for the Solution kanban (formerly "Value Stream kanban").
The epics become individual Features for the Program kanban
Capabilities or Features kanban:
(Individual Capabilities or Features in) > Funnel > Analysis > Backlog > Implementing > Done
source: Lessons 4, 5 and 6 videos, What's new in SAFe 4.0, and "01 Whats New in SAFe 4.5 article.pdf"
115
CFD
Cumulative Flow Diagram (CFD) is a control mechanism.
Lead time is measured horizontally between the arrival curve ("Backlog") and the departure cure ("Accepted")
WIP limit is measured vertically between the two curves
source: Lesson 5 video, What's new in SAFe 4.0
116
Who said "Only management can change the system", and what is the context
It was W. Edwards Deming, in "Out of the Crisis".
The ultimate responsibility for success is in the hands of leaders.
source: Leading SAFe 4.0 (Instructor)
117
What are the eight steps in implementing successful change from Joh Kotter's "Leading Change"?
1. Establish a sense of urgency
2. Create the guiding coalition
3. Develop the vision and strategy for change
4. Communicate the change vision
5. Empower employees for broad-based action
6. Generate short-term wins
7. Consolidate gains and produce more change
8. Anchor new approaches in the culture
(and the negatives of these are):
1. Allowing too much complacency.
2, Failure to create a sufficiently powerful guiding coalition
3. Underestimating the power of vision
4. Under-communicating the power of vision by 10-100X
5. Permitting obstacles to block the new vision
6. Failure to create short term wins
7. Declaring victory too soon
8. Neglecting to anchor changes firmly in the corporate culture
source: Leading SAFe 4.0 (Instructor), https://www.scaledagileframework.com/lean-agile-leadership/
118
ROAM
A risk mitigation decision making method:
Resolve
Own
Accept
Mitigate
source: Leading SAFe 4.0 (Instructor)
119
When, if ever, is a Roadmap a queue?
TBD -- it's a question posed in the training, after talking about fitting new items in upcoming PI's
source: Leading SAFe 4.0 (Instructor)
120
Is job size always a good proxy for duration? When might that NOT be the case, and how would you adjust based on that case?
TBD -- it's a question posed in the training, after talking about fitting new items in upcoming PI's
source: Leading SAFe 4.0 (Instructor)
121
What is ART Sync?
TBD -- showed up on a slide in the instructor guide
source: Leading SAFe 4.0 (Instructor)
122
Explain how to use Pareto Analysis
TBD -- showed up on a slide in the instructor guide
source: Leading SAFe 4.0 (Instructor)
123
Explain the concept of "Ba"
According to the theory of existentialism, Ba is a context, which harbours meaning. Thus, ba can be considered as a shared space that serves as a foundation for knowledge creation.
"Ba" can be thought of as a shared space for emerging relationships. This space can be physical (eg. office, dispersed business space), virtual (e.g., email, teleconference), mental (eg. shared experiences, ideas, ideals) or any combination of them. Ba provides a platform for advancing individual and/or collective knowledge.
source: http://cyberartsweb.org/cpace/ht/thonglipfei/ba_concept.html
124
Define Compliance enablers, and give some examples.
Compliance enablers are used to schedule and manage specific compliance activities, including
• Verification and Validation (V&V)
• documentation and signoffs
• regulatory submissions and approvals
source: "01 Whats New in SAFe 4.5 article.pdf"
125
What are some differences between QMS and Lean QMS?
Quality Management System (QMS) progresses in stages of Requirements, Design, Implementation and Verification, with milestones as gateways between each stage.
Lean Quality Management System (Lean QMS) assumes
• the solution and compliance are built incrementally
• Organization for value and compliance
• Build quality and compliance in
• Continuously verify and validate
• Release validated solutions on demand
source: "01 Whats New in SAFe 4.5 article.pdf"
126
What are the steps in the Lean Startup cycle?
Hypothesize
Build
Measure
Learn
This model can be applied to any Epic-level initiative, whether it arises at the Portfolio, Large Solution or Program Level.
Learn more about the Lean Startup cycle in the Epic article.
source: "01 Whats New in SAFe 4.5 article.pdf"
127
BDUF
Big Design Up Front
The Lean UX approach starts with an outcome hypothesis: Agile teams and UX designers accept that the ‘right answer’ is actually unknowable up-front. Rather, they apply Agile methods to avoid Big Design Upfront (BDUF), focusing instead on creating a hypothesis about what business outcomes to expect from a new feature, and then implements and tests that hypothesis incrementally. This results in faster feedback, which steers the solution toward success more effectively.
source: "01 Whats New in SAFe 4.5 article.pdf"
128
FAB
Features And Benefits matrix is updated with a Benefit Hypothesis in SAFe 4.5.
Feature:
[ex. In-service software update]
Benefit hypothesis:
[ex. Downtime decreased by 80%]
Acceptance Criteria:
• ___
• ___
source: "01 Whats New in SAFe 4.5 article.pdf"
129
What elements are part of Essential SAFe configuration?
Team and Program levels
On the spanning palette: Vision, System Team, Lean UX
source: "03 Whats New in SAFe 4.5 presentation.pptx"
130
What elements are part of Large Solution SAFe configuration?
Team, Program and Large Solution levels
The full spanning palette: Metrics, Shared Services, CoP, Milestones, Roadmap, Vision, System Team, Lean UX
source: "03 Whats New in SAFe 4.5 presentation.pptx"
131
What elements are part of Portfolio SAFe configuration?
Team, Program and Portfolio levels
The full spanning palette: Metrics, Shared Services, CoP, Milestones, Roadmap, Vision, System Team, Lean UX
source: "03 Whats New in SAFe 4.5 presentation.pptx"
132
What elements are part of Full SAFe configuration?
Team, Program, Large Solution and Portfolio levels
The full spanning palette: Metrics, Shared Services, CoP, Milestones, Roadmap, Vision, System Team, Lean UX
source: "03 Whats New in SAFe 4.5 presentation.pptx"
133
What are the four steps in the Lean UX cycle?
Outcomes hypothesis
Collaborative Design
Build MMF
Evaluate
source: "03 Whats New in SAFe 4.5 presentation.pptx"
134
To what kind of Product Backlog Item does an outcome hypothesis apply?
Features are implemented using Lean UX, and have an outcome hypothesis.
It is also referred to as a "benefit hypothesis"
source: "03 Whats New in SAFe 4.5 presentation.pptx"
135
Name the things that go into Story Points
Story Points are an aggregation of
* Volume - how much is there?
* Complexity - how hard is it?
* Knowlege - what do we know about it?
* Uncertainty - how much is still unknown?
source: SAFe 4.5 trainer materials
136
What does acceptance criteria look like for Epics in SAFe?
Epics do not have Acceptance Criteria. Epics are too big for Acceptance Criteria or Success Criteria, those would be too specific.
An Epic is complete once it's met its MVP, and there is a decision to either continue because of the success, or stop working on it.
source: What's New in SAFe 4.5 screencast
137
How important is it, to complete an Epic?
It's not necessary to complete all parts of an Epic.
Epics are such big things that the chance that you will need all pieces of them is slim, and until you start evaluating them in the market, you won't know.
source: What's New in SAFe 4.5 screencast
138
What is meant by fix-forward?
Sometimes, we don't have the time to fix something in dev and then move into staging and then to Production. It's such a serious problem that we have to fix it immediately in Production.
We have to have tests that we can run in Production, to be confident, if it's necessary to apply a fix directly into Production.
We also have to have a process for moving the fix back into the dev and staging environments.
source: What's New in SAFe 4.5 screencast
139
What are the five core competencies of the Lean Enterprise?
The five core competencies of the Lean Enterprise are the primary lens for understanding and implementing SAFe. Each competency is a set of related knowledge, skills, and behaviors, which together enable enterprises to achieve the best quality and value in shortest sustainable lead time.
Viewing SAFe through the lens of these competencies, it's easier to see what the Framework is designed to accomplish, and how to best approach SAFe adoption.
* Lean-Agile Leadership
* Team and Technical Agility
* DevOps and Release on Demand
* Business Solutions and Lean Systems
* Lean Portfolio Management
source: What's New in SAFe 4.6? article, https://www.scaledagileframework.com/behavior-driven-development/
140
TDD
Test-Driven Development (TDD) is a philosophy and practice that recommends building and executing tests before implementing the code or a component of a system.
source: What's New in SAFe 4.6? article
141
BDD
Behavioral Driven Development (BDD) is a Test-First, Agile Testing practice that provides Built-In Quality by defining (and potentially automating) tests before, or as part of, specifying system behavior.
Without focusing on internal implementation, BDD tests are business-facing scenarios that attempt to describe the behavior of a Story, Feature, or Capability from a user’s perspective.
BDD is a collaborative process that creates a shared understanding of requirements between the business and the development team.
BDD ensures requirements are written in a way that is inherently testable.
Gherkin is a common language/syntax used for expressing requirements in accordance with BDD, which makes them importable into a variety of automated testing tools, such as Cucumber.
source: What's New in SAFe 4.6? article, and presentation, https://www.scaledagileframework.com/behavior-driven-development/
142
What is meant by Agile Testing?
Agile Testing is a comprehensive overview of Agile testing strategies using the updated Agile testing quadrants.
source: What's New in SAFe 4.6? article
143
What is the Release on Demand health radar?
TBD (see new article)
source: What's New in SAFe 4.6? article
144
What are the four primary constructs of Full SAFe?
TEAM
PROGRAM
LARGE SOLUTION
PORTFOLIO
source: https://www.scaledagileframework.com/safe-for-lean-enterprises/
145
What are the four major areas that enterprises can expect to see benefits when using SAFe (according to dozens of case studies)?
```
SAFe business benefits:
• improved time-to-market
• quality
• productivity
• employee engagement
```
source: https://www.scaledagileframework.com/reaching-the-tipping-point/
146
LACE
Lean-Agile Center of Excellence
A small team of people dedicated to implementing the SAFe Lean-Agile way of working.
SPCs assist the LACE with building and executing the transformation backlog
source: https://www.scaledagileframework.com/safe-program-consultant/
https: //www.scaledagileframework.com/lace/
147
What are the three elements of a "sufficiently powerful guiding coalition" for change?
1. Train a number of Lean-Agile change agents as SAFe Program Consultants (SPCs)
2. Train executives, anagers, and other leaders
3. Charter a LACE
source: https://www.scaledagileframework.com/lace/
148
What is the SAFe DevOps Health Radar?
The SAFe DevOps Health Radar is a maturity assessment tool for DevOps. It helps to assess a team's ability to Release on Demand. It has
• four categories
• 16 dimensions
• five maturity levels
```
Continuous Exploration
• Hypothesize
• Collaborate & Research
• Architect
• Synthesize
```
```
Continuous Integration
• Develop
• Build
• Test end-to-end
• Stage
```
```
Continuous Deployment
• Respond
• Monitor
• Verify
• Deploy
```
```
Release On Demand
• Release
• Stabilize
• Measure
• Learn
```
```
Maturity levels:
1 Sit
2 Crawl
3 Walk
4 Run
5 Fly
```
You can access the Health Radar through the Metrics article on the Framework Website, which contains an excel spreadsheet you can download, or you can go to the Agile Transformation’s website, and try out the SAFe DevOps online assessment at: https://agilityhealthradar.com/safe-devops-assessment.
source: https://www.scaledagileframework.com/blog/assess-your-devops-health-with-the-safe-devops-radar/
149
Define Lean-Agile Leadership
```
Lean-Agile Leaders
drive and sustain
organizational change
and operational excellence
by empowering individuals and teams
to reach their highest potential.
They do this by
learning,
exhibiting,
teaching,
and coaching SAFe's Lean-Agile
mindset,
values,
principles,
and practices.
```
Among the SAFe competencies, Lean-Agile leadership is foundational. An orgnization's managers, leaders, and executives are ultimately responsible for the adoption, success, and ongoing improvement of Lean-Agile development. Only they can change and continously improve the organizational and operational systems.
source: What's New in SAFe 4.6 Presentation
150
Name the two primary responsibilities of Lean-Agile Leadership
1. Lean-thinking manager-teachers. Lean Agile Leaders become Lean-Thinking manager-teachers by exemplifying the Core Values and embracing a Lean-Agile Mindset and applying the SAFe principles.
2. Leading the transformation. Leaders must do more than instruct -- they also must guide their organizations through the SAFe transformation, making it clear at each step where they are, where they need to go next, and why is it important to keep going.
source: What's New in SAFe 4.6 Presentation
151
What are the five dimensions that enable building in quality
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: What's New in SAFe 4.6 Presentation
152
What are the three SAFe artifacts?
Epic
Feature
Stories
source: (about 4.5) http://projectmanager.org/images/downloads/PDC_2018_Presentations/cindy_lake_safe_in_a_nutshell.pdf
153
What are the three demo types in SAFe 4.5?
Solution Demo
System Demo
Iteration Review
source: http://projectmanager.org/images/downloads/PDC_2018_Presentations/cindy_lake_safe_in_a_nutshell.pdf
154
What are the four sub-dimensions of Release on Demand?
* Release - covers the skills necessary to deliver the solution to end users, all at once or incrementally
* Stabilize and operate - covers the skill needed to make sure the solution is working well from oth a functional and non-functional perspective
* Measure - covers the skills necessary to quantify whether the newly released functionality provides the intended value
* Learn - encompasses the skills needed to decide what should b done with the information gathered and prepare for the next loop through the continuous delivery pipeline with new hypotheses.
source: https://www.scaledagileframework.com/release-on-demand/
155
What are the three demo types in SAFe 4.5?
Solution Demo
System Demo
Iteration Review
source: http://projectmanager.org/images/downloads/PDC_2018_Presentations/cindy_lake_safe_in_a_nutshell.pdf
156
What are the four sub-dimensions of Release on Demand?
* Release - covers the skills necessary to deliver the solution to end users, all at once or incrementally
* Stabilize and operate - covers the skill needed to make sure the solution is working well from oth a functional and non-functional perspective
* Measure - covers the skills necessary to quantify whether the newly released functionality provides the intended value
* Learn - encompasses the skills needed to decide what should b done with the information gathered and prepare for the next loop through the continuous delivery pipeline with new hypotheses.
157
MTTR
Mean Time To Restore (or Repair)
A reliable leading indicator of high DevOps maturity.
The average time required to fix a failed component or device and return it to production status.
source: https://www.scaledagileframework.com/continuous-deployment/
158
Name the four sub-dimensions of Continuous Integration
* Develop - implement stories and commit the code and components to the trunk
* Build - create deployable binaries and merge the development branches into the trunk
* Test end-to-end - validate the solution in the staging environment
* Stage - host and validate the solution in a staging environment, prior to production
source: https://www.scaledagileframework.com/continuous-integration/
159
What is a good metric for progress during the Build phase, when teams are continuously integrating new code?
Passing versus nonot-yet-passing and broken automated tests are the real indicators of progress.
source: https://www.scaledagileframework.com/continuous-integration/
160
What is meant by a "gated commit"
Software must pass a gate such as unit test , performance test, and free of known defects, before being checked into the main codebase or trunk.
source: https://www.scaledagileframework.com/continuous-integration/
161
What is the benefit of trunk-based development
Trunk-based development helps to ensure the code can reliably be released on demand without the need for costly code freezes or hardening iterations.
Code that passes the gated commit is automatically integrated into the trunk, which removes the complications of managing multiple branches.
source: https://www.scaledagileframework.com/continuous-integration/
162
Blue/Green deployment
Blue-green deployment is a technique that reduces downtime and risk by running two identical production environments called Blue and Green. At any time, only one of the environments is live, with the live environment serving all production traffic.
To deploy, a switch is flipped (or a load balancer) and the idle environment becomes the staging environment, while the other becomes the new idle environment. This enables quick transition and recovery where necessary.
source: https://www.scaledagileframework.com/continuous-integration/, https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html
163
Explain Principle #1 of the Lean and Agile Principles - Take an economic view
Principle #1 uses economics to drive all decisions and ensures we include all relevant parameters in the decision process: development costs, production costs, delivery cycle time, value delivered, etc.
source: https://www.scaledagileframework.com/business-solutions-and-lean-systems/
164
Explain Principle #2 of the Lean and Agile Principles - Apply systems thinking
Principle #2 confirms that everyone understands and comuts to the common goals of the system and that all decisions optimize the whole solution, not individual components. I also calls out our responsibility to provide solution builders with the appropriate knowledge and alignment to make good, localized decisions that optimize the whole.
source: https://www.scaledagileframework.com/business-solutions-and-lean-systems/
165
Explain Principle #3 of the Lean and Agile Principles - Assume variability; preserve options
Principle #3 tells us that exploring alternatives is an investment in knowledge creation that leads to more optimal technical decisions. Better decisions minimize the costs and delays of downstream inefficiencies and rework.
source: https://www.scaledagileframework.com/business-solutions-and-lean-systems/
166
Explain Principle #4 of the Lean and Agile Principles - Build incrementally with fast, integrated learning cycles
Principle #4 tells us to use cadence-based learning cycles to evaluate these alternatives. While Agile teams use iterations to build "potentially releasable products", large systems also use increments to validate technical assumptions.
source: https://www.scaledagileframework.com/business-solutions-and-lean-systems/
167
Explain Principle #5 of the Lean and Agile Principles - Base milestones on objective evaluation of working systems
Principle #5 uses the demonstrable learning gained from each cycle as the only real measure of progress. Sequential, phase-gate models that value documents and specifications delay risk and assumption mitigation. Instead, measuring progress by validating technical assumptions and user acceptance via objective evidence reduces risk and provides better outcomes.
source: https://www.scaledagileframework.com/business-solutions-and-lean-systems/
168
What are the three phases of the BDD process?
1. discovery - writing acceptance criteria ("confirmation" of the 3 C's)
2. formulation - writing acceptance tests that are specific, clear, unambiguous examples of behavior
3. automation
In the BDD process the acceptance criteria are transformed into acceptance test that are later automated.
source: https://www.scaledagileframework.com/behavior-driven-development/
169
Read this about Scrum in SAFe and be able to comment
https://www.google.com/amp/s/www.agilesparks.com/blog/improving-safe-thru-professional-scrum/amp/
170
As part of the SAFe Implementation Roadmap, what must organizations do? (7 items)
Organizations must
• embrace a Lean-Agile Mindset
• understand and apply Lean-Agile principles
• identify Value Streams and Agile Release Trains (ARTs)
• implement a Lean-Agile portfolio
• build quality in
• establish the mechanisms for continuous value delivery and DevOps
• the culture must evolve as well
source: https://www.scaledagileframework.com/implementation-roadmap/
171
What are the 12 Steps to the SAFe Implementation Roadmap?
1. Reaching the Tipping Point
2. Train Lean-Agile Change Agents
3. Train Executives, Managers, and Leaders
4. Create a Lean-Agile Center of Excellence
5. Identify Value Streams and ARTs
6. Create the Implementation Plan
7. Prepare for ART Launch
8. Train Teams and Launch the ART
9. Coach ART Execution
10. Launch More ARTs and Value Streams
11. Extend to the Portfolio
12. Sustain and Improve
source: https://www.scaledagileframework.com/implementation-roadmap/
