SAFE Agile

What are the SAFe core values? -commitment, compentency, culture, collocation - people and culture, transparency, responding to change, collaboration -transparency, Program Execution, Alignment, Built-in quality - code quality, fast feedback, trust, alignment

-transparency, Program Execution, Alignment, Built-in quality

Iteration Planning Flow

1) Establishing Capacity 2) Story Analysis and estimating 3) Detailing Stories 4) Developing Iteration Goals 5) Committing to Iteration Goals. Iteration Planning Timebox: 4 hours or less This meeting is by and for the team SMEs may attend as required.

Which statement is true about work in process (WIP) limits? 1. Higher WIP limits result in lower utilization 2. Lower WIP limits improve flow 3. Lower WIP limits result in fewer Stories being completed 4. Higher WIP limits provide richer feedback

1. Higher WIP limits result in lower utilization

What are two reasons Agile development is more beneficial than waterfall development? (Choose two.) 1. It allows businesses to deliver value to the market more quickly 2. It relies on external provider dependencies 3. It requires phase-gate approvals to ensure that everyone is moving together 4. It allows management to track project progress based on steering committees and metrics 5. It increases productivity and employee engagement

1. It allows businesses to deliver value to the market more quickly 5. It increases productivity and employee engagement

What is the benefit of separating release elements from the Solution?1. It allows the release of different Solution elements at different times 2. It allows the Agile Release Train to demo value every two weeks 3. It allows the Systems Team to integrate with ease 4. It allows Agile Teams to launch untested Features

1. It allows the release of different Solution elements at different times

Which statement is true about Iteration planning for Kanban teams? 1. Kanban teams publish Iteration goals 2. Kanban teams find high value in trying to plan the Iteration in detail 3. Kanban teams do not commit to service level agreements 4. Kanban teams estimate their velocity

1. Kanban teams publish Iteration goals

What is the goal of the SAFe House of Lean model? 1. Value 2. Innovation 3. Relentless Improvement 4. Flow

1. Value

Which two views does the Iteration review provide into the program? (Choose two.) 1. How the team is increasing empowerment 2. How the team did on the Iteration 3. How the team is doing on the Program Increment 4. How the team is demonstrating transparency of decision-making 5. How the team is responding to the stakeholders

2. How the team did on the Iteration 3. How the team is doing on the Program Increment

What is an example of a modified Fibonacci sequence? 1. ...1, 1, 3, 5, 5... 2. ...5, 8, 13, 21, 34... 3. ...5, 8, 13, 20, 40... 4. ... 2, 4, 5, 9, 11...

3. ...5, 8, 13, 20, 40...

The Inspect and Adapt event always starts with which activity? 1. Agreement on the problems to solve 2. Quantitative measurement 3. The PI System Demo 4. Retrospective and Problem Solving Workshop

3. The PI System Demo

Which statement describes one element of the CALMR approach to DevOps? 1. Build cross-functional Agile Release Trains around the flow of value to the Customer 2. Keep everything under version control 3. Decentralize decision making 4. Establish a work environment of shared responsibility

4. Establish a work environment of shared responsibility

Acceptance Criteria

Acceptance criteria provide the details of the story from a testing point of view. Acceptance criteria are created by the Agile team.

Behavior Driven Development: From ambiguity to precision.

Behavior is often first described in general terms, which can be ambiguous Specific examples of behavior provide better understanding. The examples can directly become tests, or they can lead to specific behaviors which then are transformed into tests.

Apply some common splitting techniques

Business rule variations (single variation, than remainder) Workflow Steps (for multistep stories) Simple/complex (search for single word, then for phrases). Scenarios (use case exceptions).

3C's

Card -> Written on a card in the tool and may annotate with notes Conversation -> The details are in a conversation with the product owner. Confirmation -> Acceptance criteria confirm the story correctness.

Enabler Stories

Enabler stories build the groundwork for future user stories. There are 4 types of enabler stories. Infrastructure -> Build development and testing frameworks that enable a faster and more efficient development process. Architecture -> Build the Architectural runway which enables smoother and faster development. Exploration -> Build understanding of what is needed by the customer to understand prospective solutions and evaluate alternatives. Compliance -> Facilitate specific activities such as verification and validation, documentation, signoffs, regulatory submissions, and approvals.

Features have a benefit hypothesis and acceptance criteria

Feature is an industry-standard term that describes a specific system behavior. Benefit hypothesis justifies Feature implementation cost and provides business perspective when making scope decisions. Acceptance criteria is typically defined program backlog refinement Features reflect functional and nonfunctional requirements. Features fit into one PI. Image: Feature: In service Software update. Acceptance Criteria: Nonstop routing availability. Automatic and manual update support. Rollback capability. Support through existing admin tools. All enabled services are running after the update.

Splitting Stories

In support of small batches for flow, decrease size to minimum. Split Stories into essential and non-essential parts and eliminate the non-essential Ensure you have something release-able. In support of feedback: Deploy small stories to get technical/user feedback quickly (maximize feedback) In support of iteration planning: Split stories so they fir into an iteration

INVEST in a Good Story

Independent -> Write stories that can be developed separately. Negotiable -> Write stories in which scope can be negotiated Valuable -> Write stories that are valuable to the customer. Estimable -> write stories that can be estimated. Small -> Write stories that can fit in an iteration. Testable -> Write stories that are testable.

Sequencing Stories

Primary economic prioritization happens in the Program Backlog. Agile Teams sequence work for efficient execution of business priorities. The Product Owner and the team sequence work based on. Story priorities inherited from program backlog priorities. Events, Milestones, releases and other commitments made during PI Planning. Dependencies with other teams Local priorities Capacity allocations for defects, maintenance, and refactors. Initial sequencing happens during PI planning. Adjustments happen at iteration boundaries.

Plan and Commit.

Purpose -> Define and commit to what will be built in the iteration Process -> The product owner defines what; the team defines how and how much; four hours max. Result -> Iteration Goals and backlog of the team's commitment. Reciprocal Commitment -> Teams commits to delivering specific value. Business commits to leaving priorities unchanged during the iteration.

What replaces detailed requirements documents? 1. Pair work 2. Stories 3. Unit tests 4. Task boards

Stories

What is typically included in the definition of done for the team increment? 1. Customer documentation is ready 2. Regression testing is done 3. Stories are accepted by the Product Owner 4. Stories are accepted by Product Management

Stories are accepted by the Product Owner

Why is transparency so important in SAFe? 1. Lean works when an organization is transparent yet finds a way to monitor access to information 2. To enable continuous delivery of value 3. Moderate improvements are achieved with ongoing transparency 4. Transparency creates trust, and trust is required for risk-taking

Transparency creates trust, and trust is required for risk taking

Finding the right trade-off: Feature and component teams

Use feature teams for: The fastest velocity, to minimize dependencies, and to develop T-shaped skills. use component teams in case of: High reuse, high technical specialization and critical NFRs. Creating each component as a potentially replaceable part of the system with well-defined interfaces.

SAFe House of Lean

VALUE - Respect for people and culture - Flow - Innovation - Relentless Improvement LEADERSHIP

User Stories are

short descriptions of a small piece of desired functionality, written in the user's language. Recommended form of expression is the user-voice form as follows: As a (user role), I want to (activity), so that (business value).

what is the role of the Release Train Engineer? - to serve as the content authority at the program level - to serve as the Scrum Master for the Agile Release Train - to coach teams to improve their results - to ensure the technical integrity of all development in the Agile Release Train

to serve as the Scrum Master for the Agile Release Train

which activity is key to successfully implementing a Scaled Agile Framework? -replace the PI Planning process with the Inspect and Adapt workshop when possible -Use the innovation and Planning Iteration instead of the PI Planning process -Remove block such as Portfolio estimation -use a cadence-based PI Planning process

use a cadence-based PI Planning process

Agile Release Train aligns teams to a common mission using a single vision and what else? 1. Weighted Shortest Job First 2. Team backlogs 3. Release on Demand 4. Program Backlog

Program Backlog

What is something an Agile Team would develop? 1. Firmware 2. Workflow steps 3. Program Increment (PI) Objectives 4. Work breakdown structures

Program Increment (PI) Objectives

Agile for teams: Kanban

Visualize work flow. Limit work in process. Improve flow.

The Agile Manifesto

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

Which three questions should each team member answer during the daily stand-up? (Choose three.) How I am contributing to an environment of continuous change? How am I splitting the Solutions into Capabilities and Enablers? How am I optimizing the full Solution? What will I do today to advance the Iteration goals? Are there any impediments that will prevent the team from meeting the Iteration goals? What did I do yesterday to advance the Iteration goals?

What did I do yesterday to advance the Iteration goals What will I do today to advance the Iteration goals? Are there any impediments that will prevent the team from meeting the Iteration goals?

Iteration planning, Iteration review, and backlog refinement are examples of which type of event? 1. Program Event 2. Team Event 3. Sync Event 4. PI Event

Team Event

The four levels of the Scaled Agile Framework Definition of Done include which elements? 1. Iteration Review, System Increment, Solution Demo, Release 2. Team Review, Inspect and Adapt, Solution Demo, System Demo 3. Team Increment, System Increment, Solution Increment, Release 4. Team Retrospective, System Demo, Solution Increment, Review

Team Increment, System Increment, Solution Increment, Release

If the PI System Demo shows the current state of the Solution, then who is this demo intended for? 1. The Business Owners 2. The Product Owner 3. The Scrum Masters 4. The Agile Team

The Business Owners

Agile Product Delivery provides the focus on customer and execution

The customer is the center of your product strategy Develop on cadence and release on demand Continuously explore, integrate, deploy, and innovate Images: Customer Centricity and Design Thinking Develop on cadence and release on demand DevOps and the continuous delivery pipeline

Enterprise Solution Delivery drives delivery of highly complex systems

Apply Lean system engineering to build really big systems Coordinate and align the full supply chain Continually evolve live systems Images: Lean System and Solution Engineering Coordinate Trains and Suppliers Continually Evolve Live Systems

A cumulative flow diagram focuses on which curves? 1. Implementation curve ("movement") and departure curve ("done") 2. Arrival curve ("to do") and evolution curve ("change") 3. Backlog curve ("work") and departure curve ("done") 4. Arrival curve ("to-do") and departure curve ("done")

Arrival curve ("to-do") and departure curve ("done")

Which factor helps unlock the intrinsic motivation of knowledge workers? 1. Autonomy 2. Pay-for-performance 3. Team performance incentives 4. Parallel development

Autonomy

SAFe Lean Agile Principles

1) Take an economic view 2) Apply systems thinking 3) Assume variability; preserve options 4) Build incrementally with fast integrated learning cycles 5) Base milestones on objective evaluation of working systems 6) Visualize and limit work-in-progress, reduce batch sizes, and manage queue lengths 7) Apply cadence (timing), synchronize with cross-domain planning 8) Unlock the intrinsic motivation of knowledge workers 9) Decentralize decision-making 10) Organize around value

Organize people in value streams

1) Operational Value Streams: Contains the steps and the people who deliver end user value using the business solutions created by the development value streams. 2) Development Value Streams: Contains the steps and the people who develop the business solutions used by operational value streams.

The Agile Manifesto Principles 1-6

1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2) Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3) Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4) Business people and developers must work together daily throughout the project. 5) Build projects around motivated individuals.Give them the environment and support they need, and trust them to get the job done. 6) The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

What is the role of the System Architect/Engineer? 1. To define the design for the system 2. To manage dependencies 3. To implement continuous improvement methods 4. To guide the teams and support the Architectural Runway

4. To guide the teams and support the Architectural Runway

What is the recommended size of an Agile Team? 8 - 12 people 3 - 5 people 10 - 15 people 5 - 11 people

5 - 11 people

The Agile Manifesto Principles 7-12

7) Working software is the primary measure of progress. 8) Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9) Continuous attention to technical excellence and good design enhances agility. 10) Simplicity--the art of maximizing the amount of work not done--is essential. 11) The best architectures, requirements, and designs emerge from self-organizing teams. 12) At regular intervals, the team reflects on how to become more effective, then tunes and adjust sits behavior accordingly.

Relentless Improvement

A constant sense of danger Optimize the whole Problem Solving culture Base improvements on facts Reflect at key Milestones

SAFe for Lean enterprises

A knowledge base of proven, integrated principles, practices and competencies for achieving business agility by implementing Lean, Agile, and DevOps at scale.

The power of a high performing team

A self organizing team dynamically interacts with itself and the organization. Team members create new points of view and resolve contradictions through dialogue The team is energized with intentions, vision, interest and mission Leaders provide autonomy, variety, trust and commitment.

Value

Achieve the shortest sustainable lead time with: The best quality and value to people and society High morale, safety, and customer delight

Roles on the Agile Team

Agile Team -> Create and refine user stories and acceptance criteria. Define, build, test, and deliver stories. Develop and commit to team PI Objectives and Iteration Plans. Five to eleven members. Scrum Master -> Coaches the Agile Team and facilitates team meetings. Removes impediments and protects the team from outside influence. Attends scrum of scrum meetings. Product Owner -> Defines and accepts Stories. Acts as the customer for developer questions. Works with Product Management to plan Program Increments (PI).

Build cross functional agile teams

Agile teams are cross functional self organizing entities that can define, build test, and where applicable, deploy increments of value. They are optimized for communication and delivery of value They deliver values every 2 weeks.

Lean Portfolio Management aligns execution to strategy

Align Strategy, funding, and execution Optimize operations across the portfolio Lightweight governance empowers decentralized decision-making

When are the tests written in a Test-driven Development environment? 1. While creating the Product Requirements document 2. Just before deployment ("Just in Time") 3. While the code is being written 4. Before the code is written

Before the Code is Written

Base Milestones on Objective Evaluation of Working Systems

Build the system in increments, each of which is an integration point that demonstrates some evidence of the feasibility of the solution in process. Milestones based on objective evaluation of working systems.

The ART and teams continuously deliver value.

C -> Culture of shared responsibility A -> Automation of continuous delivery pipeline L-> Lean Flow Accelerates delivery M -> Measurement of everything R -> Recovery enables low risk releases

3 C's of agile user story writing

Card Conversation Confirmation

During Iteration execution, a team's velocity tends to be most affected by what? 1. Productivity changes, team location, and innovation measures 2. Changing financial planners, a new Scrum Master, and new testers 3. Changing team size, team makeup, and technical context 4. Product Owner changes, changing estimations, and new Features

Changing team size, team makeup, and technical context

A co-located Agile Team is a key component of Agile Development.

Collocation is critical for the agile team to be effective Recommended for programs to have efficient product development flow. If you have distributed team members, development must be compensated with efficient remote interaction (video-conferencing, sharing, and collaboration tools, agile lifecycle management tools, etc.)

The Team Backlog

Contains all the work for the team. Created by the Product Owner and the team. Prioritized by the Product Owner Contains user and enabler stories. User stories provide Customers with value. Enabler Stories build the infrastructure and architecture that makes user stories possible. Stories in the backlog are prioritized. Stories for the next iteration are more detailed than stories for later iterations. Nonfunctional requirements (NFRs) are a constraint on the backlog.

The Scrum Master in the Enterprise

Coordinates with other Scrum masters, the System Team, and shared resources in the ART PI Planning meetings. Works with the above teams throughout each iteration and PI. Coordinates with other Scrum Masters and the release train engineer in scrum of scrums. Helps team understand and operate within its capacity. Helps teams operate under architectural and portfolio governance, system-level integration, and system demos. Fosters team adoption of Agile technical practices.

Organizational Agility provides the flexibility to change

Create an enterprise-wide, Lean-Agile mindset Lean out business operations Respond quickly to opportunities and threats Images: Lean-thinking People and agile teams Lean Business Operations Strategy Agility

Quality is first and foremost a function of what in a Lean-Agile concept? 1. Culture of shared responsibility 2. Deployment on demand 3. Preserving options 4. Empowered Solution authority

Culture of shared responsibility

The Agile Release Train (ART)

Each ART is a virtual organization of 5-12 teams (typically 50 - 125 people) that plans, commits, and deploys together. Agile Release Trains: Aligns teams to a common business and technology mission Deliver a continuous flow of value. Image: Define new functionality Implement Deploy Release and operate

James is a Product Owner. It is day seven of the Iteration and his team tells him that they may miss their Iteration commitment. What should James do? 1. Agree to add a person from the System Team to complete the work 2. Support adding an Innovation and Planning Iteration directly after the current Iteration 3. Support splitting a Story into a coding story and a testing story, and then moving the testing story into the next Iteration 4. Ensure the Iteration backlog is accurately prioritized

Ensure the Iteration backlog is accurately prioritized

What are the three levels of the Scaled Agile Framework?+ 1. Framework, Delivery, Iteration 2. Epic, Capability, Feature 3. Value Stream, Program, Team 4. Essential, Large Solution, Portfolio

Essential, Large Solution, Portfolio

The Product Owner in the Enterprise

Establishes the sequence of backlog items based on program priorities, events and dependencies with other teams. Operates as part of an extended Product management Team. Understands how the enterprise backlog structure operates with epics, capabilities, features, and stories. Uses PI Objectives and Iteration Goals to communicate with management. Coordinates with other Product Owners, the System Team and shared services in the PI Planning Meetings. Works with other Product Owners and the Product Management team throughout each Iteration and PI.

Continuous Learning Culture transforms the cultue

Everyone in the organization learns and grows together Exploration and creativity are part of the organizations DNA Continuously improving solutions, services and processes is everyone's responsibility Images: Learning Organization Innovation Culture Relentless Improvement

Quality practices provides the bases for Technical Agility.

Examples for quality practices inspired from eXtreme Programming (XP) Test Drive Development, Coding standards, Collective ownership, automated testing, continuous integration, Simple design, User Stories, Refactoring, pair work.

Seven Core Competencies of Business Agility

Execution: 1) Enterprise Solution Delivery 2) Agile Product Delivery 3) Team and Technical Agility Strategy: 4) Lean Portfolio Management, 5) Organizational Agility, 6) Continuous Learning Culture, Center Core: 7) Customer Centricity

Define Features for the Program backlog

Features are services that fulfill user needs: Feature is an industry-standard term familiar to marketing and Product Management Expressed as a phrase, value is expressed in terms of benefits Features are identified, prioritized, estimated, and maintained in the program backlog.

What is one of the typical Kanban classes of service for Agile teams?1. Funnel 2. Fixed-date 3. Review 4. Accepted

Fixed-date

SAFe Configurations

Four Configurations provide the right solution for each enterprise. Full Configuration Large Solution Configuration Portfolio Configuration Essential Configuration

Respect for people and culture

Generative culture People do all the work Your customer is whoever consumes your work Build long-term partnerships based on trust To change the culture, you have to change the organization

Team and Technical Agility is the engine

High-Performing, cross-functional Agile Teams Business and technical Teams build Business Solutions Quality business solutions delight customers Images: Agile Teams Teams of Agile Teams Built-in Quality

What is an important outcome of Inspect and Adapt? 1. Analyze and approve Program Epics 2. Identify improvement items for the next PI 3. Identify all out-of-scope work 4. Agree on what will be committed to in the next PI

Identify improvement items for the next PI

For the past week Lee has been late to the Daily Stand-up. What is the Scrum Master's best course of action? 1. Change the time of the Daily Stand-up until all participants can meet each day 2. Escalate the issue to Lee's functional manager and explain what is happening 3. Update the working agreements to clearly state the importance of the Daily Stand-up, and why the team is less effective if she misses 4. In a private conversation, work with Lee to identify a solution and explain why her presence is so necessary for success

In a private conversation, work with Lee to identify a solution and explain why her presence is so necessary for success

Inovation

Innovative people Provide time and space for innovation Go see Gemba Experimentation and feedback Innovation riptides Pivot without mercy or guilt.

Lean-Agile provides the foundation

Inspire others by modeling desired behaviors Align mindset, words, and actions to Lean-Agile values and principles Actively lead the change and guide others to the new way of working. Images: 1) Leading by Example 2) Mindset & Principles 3) Leading Change

How do Agile Teams strive to continuously integrate assets? 1. Integrate vertically sliced user stories 2. Leave as much as possible to the System Team 3. Avoid integrating hardware branches 4. Seek to physically branch software

Integrate vertically sliced user stories

Which statement is true about the PI Planning event? 1. It involves Product Management and Product Owners on the first day and the rest of the teams on the second day 2. It involves everyone in the program over a two-day period 3. It involves program Portfolio Management to prioritize the Stories presented by teams during the final plan review 4. It involves only the team members who are most qualified to estimate the work

It involves everyone in the program over a two-day period

Which statement describes a cadence-based PI Planning event? 1. As many team members as possible should attend remotely to reduce travel costs 2. It is very important and should be postponed until all participants can attend 3. It is an all-hands, two-day event with the goal to create alignment 4. It is not a required event but tasks move forward at higher velocity when the meeting occurs

It is an all-hands, two-day event with the goal to create alignment

What is an Iteration Retrospective? 1. It is used by Agile teams to reflect on the timebox just completed and to develop new ideas to improve the process 2. It is used to build the context that allows the Agile Release Trains and suppliers to create their plans during the Program Increment 3. It requires the Scrum Masters to gather ideas and possible solutions by reviewing past Program Increments 4. It gathers the stakeholders together to review past case studies from other companies

It is used by Agile Teams to reflect on the timebox just completed and to develop new ideas to improve the process

How does relentless improvement support value in the SAFe House of Lean? 1. It uses informed decision-making through fast feedback 2. It optimizes the whole 3. It allows teams to pivot without mercy or guilt 4. It builds long-term partnerships based on trust

It optimizes the whole

Why is the modified Fibonacci sequence used when estimating? 1. It results in greater precision 2. It can be used to predict unit test coverage 3. It reflects the uncertainty in estimating larger items 4. It serves as a way to estimate large ranges

It reflects the uncertainty in estimating larger items

Leadership

Lead by Example Adopt a growth mindset Exemplify the values and principles of Lean-Agile and SAFe Develop people Lead the change Foster psychological safety

Visualize and limit WIP, reduce batch size and manage queue lengths

Long queues: All bad. Includes longer cycle times, increased risks, more variability, lower quality, less motivation. Littles Law -> Average wait time = average queue length/average processing rate. Reduce batch size for higher predictability Apply cadence, synchronize with cross-domain planning. Cadence based planning limits variability.

What is critical to successfully implementing quality in a Lean-Agile environment? 1. Separation of Dev and Ops 2. A phased-gate rollout 3. Making quality everyone's responsibility 4. Component teams

Making quality everyone's responsibility

Organizing team around value

Maximize velocity by minimizing dependencies and handoffs, while sustaining architectural robustness and system qualities A team can be organized around: Features and components.

Flow

Optimize sustainable value delivery Build in quality Understand, exploit, and manage variability Move from projects to products.

PRACTICE EXAM

PRACTICE EXAM

Roles on the Agile Release Train

Product Management owns, defines, and prioritizes the Program Backlog Release Train Engineer acts as the chief Scrum master for the Train. System Architect/Engineering provides architectural guidance and technical enablement to the teams on the train. Business Owners are key stakeholders on the Agile Release Train. Product Management owns, defines, and prioritizes the program backlog. System Team provides processes and tools to integrate and evaluate assets early and often.

Which practices are demonstrated during the Inspect and Adapt event? 1. Reflect, problem solve, and identify improvement actions 2. Move forward, analyze future Stories, integrate, and iterate 3. New start, job sequence, funnel, and enable 4. Forward focus, develop, cross-domain plan, and expedite execution

Reflect, problem solve, and identify improvement actions

Agile for teams: Scrum

Roles: Agile Team, Scrum master, Product Owner Events: Iteration Planning, Daily Standup, Iteration Review, Iteration retrospective

Why SAFe and Benefits

SAFe business benefits are derived directly from case studies written by SAFe customers Engagement -> 10-50 % happier more motivated employees Productivity -> 20-50% increase in productivity Time-To-Market -> 30-75% faster time-to-market Quality -> 25-75% defect reduction

SLIDES

SLIDES

What is an example of a program event? 1. Daily stand-up 2. Scrum of scrums 3. Innovation and Planning 4. Iteration review

Scrum of scrums

How can a technical exploration Enabler be demonstrated? 1. Show the knowledge gained by the exploration 2. Demonstrate working systems in the production environment 3. Exploration Enablers do not need to be demonstrated 4. Show the acceptance tests written for the exploration

Show the knowledge gained by the exploration

Who or which group is responsible for providing architectural guidance to the Agile Release Train? 1. Product Management 2. System Team 3. Enterprise Architect 4. System Architect

System Architect

Which statement reflects one of the steps for setting initial velocity? 1. Identify work on technical infrastructure, tooling, and other systemic impediments 2. The team members assess their availability, acknowledging time off and other potential duties 3. Maintenance tasks do not need to be included in velocity; maintenance tasks fall outside this scope 4. Determining velocity is a new function in each Iteration; previous Iterations should not be transferred to a new Iteration

The team members assess their availability, acknowledging time off and other potential duties

Teams create and challenge norms

There is a creative chaos via demanding performance goals. The team is challenged to question every norm of development. Equal access to information at all levels is critical

What is the role of the Scrum Master? 1. To coordinate Portfolio Epics through the Portfolio Kanban system 2. To be a stakeholder who has the primary business and technical responsibility for fitness for use 3. To act as a servant leader who helps teams self-organize, self-manage, and deliver using effective Agile practices 4. To facilitate Agile Release Train processes and Solution Train execution

To act as a servant leader who helps teams self-organize, self-manage, and deliver using effective Agile practices

Why do Lean-Agile leaders try to connect the silos of business, system engineering, hardware, software, test, and quality assurance? 1. To allow friction between the teams 2. To align around value 3. To optimize vertical communication 4. To enforce organizational boundaries between functions

To align around value

Which two statements describe the responsibilities of the Product Owner? (Choose two.) 1. To coach the team 2. To ensure the team follows Agile principles and practices 3. To own and manage the Team Backlog 4. To be a single voice for the Customer and stakeholders 5. To protect the team from external forces

To be a single voice for the Customer and stakeholders To own and manage the Team Backlog

What is the purpose of the Iteration review? 1. To identify where there is too much work in the system and where the teams are being overloaded 2. To measure the team's progress by showing working Stories to the stakeholders and getting feedback from them 3. To show the backlog items and work on possible Solutions for the backlog items 4. To serve as a forecasting meeting where the work is estimated for the Program Increments

To measure the team's progress by showing working Stories to the stakeholders and getting feedback from them

When should a component team be used? * To gain the fastest velocity with well defined interfaces * To obtain high reuse and technical specialization with a focus on nonfunctional requirements * To develop T-shaped skills together with Continuous Integration * To create each replaceable component with minimized dependencies

To obtain high reuse and technical specialization with a focus on nonfunctional requirements

Which responsibility belongs to the Product Owner in the team? 1. To facilitate team meetings and drive Agile behavior 2. To foster adoption of Agile technical practices 3. To foster normalized estimating within the team 4. To sequence backlog items to program priorities, events, and dependencies

To sequence backlog items to program priorities, events, and dependencies

What visibility should Scrum Masters provide during the Agile Release Train Sync? 1. Visibility into system Solution Intent 2. Visibility into progress and impediments 3. Visibility into single source design decisions 4. Visibility into collaboration deployment

Visibility into progress and impediments

An Agile Team collects the Iteration metrics they have agreed upon during which part of the team retrospective? -during the qualitative part of the team retrospective -during the features agreement retrospective -during the quantitative part of the team retrospective -during the time and materials retrospective

during the quantitative part of the team retrospective