Scaled Agile SAFe-SPC SAFe Practice Consultant SPC (6.0) Exam Practice Test

Solution Management

Value Stream Engineer

Solution Architect/Engineer

Customer

Release Management

Assign business value to Team Objectives during PI Planning.

Participate in Post-PI Planning and assist trains in adjusting ART PI plans as needed.

Assign business value to Epics and Features.

Ensure that the Solution Demo occurs.

Determine the product Roadmap

ROAMing of risks.

Assignment of business value.

Management review and problem-solving meeting.

Team breakouts.

Hourly checkpoints.

True

False

So that team members collaborate better.

So that the team is able to meet its Iteration Goals.

So that teams continuously invest in the Architectural Runway.

It helps resolve conflicts between Feature teams and component teams.

So that the work can be better estimated.

Scrum Masters

Product Owners

Business Owners

Release Train Engineer

Release Management

Solution Management

Collect additional input from other stakeholders.

Take time to provide more detailed specifications for each Epic.

Use strategic themes to help the group understand how an Epic contributes to the realization of the enterprise business strategy.

Change the scale for WSJF parameters.

Split Epics into Capabilities, prioritize them, and combine those priorities back to the Epic level.

Make it easier to assess the state of smaller batches.

Decrease stress on the system.

Increase throughput.

Produce less measurement overhead.

Increase delivery reliability.

Business Capabilities

Portfolio Enabler Epics

Strategic Themes

Enabler Features

Spikes

Program Epics

Governance, strategy and investment funding, program management.

Program management, stakeholder management, PI Planning.

Lightweight business case, Epic specification workshop, Budget allocation.

Governance, investment funding, product strategy.

True

False

By understanding the full Value Stream.

By constant reduction of delays.

By reducing batch sizes.

By applying subjective governance.

On demand.

At the end of each Sprint.

At the end of each PI.

Mid-PI.

Spikes are strictly for internal learning of the team and do not need to be demoed.

Showing the functioning code in the production environment.

Showing the knowledge gained by the spike.

Showing a prototype produced for the spike.

Showing the quantitative data that will prove useful in developing future user stories.

Train Scrum Masters in servant leadership following "SAFe for Teams" training.

Make an initial presentation on SAFe to the organization.

Familiarize Release Train Engineers with the PI Planning process.

Familiarize executives with SAFe.

Train the teams prior to PI Planning.

Maintain development and test environments to better match production.

Deploy to staging every sprint.

Put everything under version control.

Start automating the actual deployment process.

Build and maintain a production-equivalent staging environment.

Continuously synchronize all Feature and team branches.

Create the ability to automatically build environments.

True

False

Involve representatives of department teams in Iteration Planning and Demos.

Make daily stand-ups more engaging and strictly timeboxed.

Review the burn-down chart at each retrospective to improve team estimating.

Increase unit test coverage.

Synchronization enables multiple perspectives to be understood, resolved, and integrated at the same time.

They enable systems builders to operate reliably and with certainty within a safety buffer.

Synchronization enables reduction in WIP.

Cadence limits variance.

Cadence enables variability and makes wait times predictable.

The acceptance Criteria for the Capabilities.

Job sequencing for the Epics in the Value Stream Backlog.

The Economic Framework for the Value Stream.

The environment in which the Solution is deployed.

The Customer is satisfied with the User Experience.

Nonfunctional Requirements are met.

Code is checked in and merged into main branch.

No must-fix defects exist.

All unit tests are passing.

Coding standards have been followed.

Extending the duration of a PI.

Changing total ART resources

Switching to a different PI cadence.

Reducing the scope of a Program Epic.

Prioritizing Features based on Cost of Delay.

User experience is indeed a different concept and the team should be exempt from working in Iterations.

Just like system architecture, the entire user experience should be fully designed before an implementation.

Since the team is working in timeboxes, this has been proven to be the most effective way to implement the user experience.

It's important to have an overall user experience vision before implementation, but the vision can be implemented iteratively for early feedback.

Lead time

Value stream budget

Return on Investment (ROI)

Risk

Development expense

Decentralization of control.

Transparency.

Reporting.

U-curve optimization.

Servant leadership.

Iteration Planning is required in every Iteration to enable fast learning cycles.

Teams that have no dependencies may choose not to do Iteration Planning once they have planned the PI.

Component teams require Iteration Planning in every Iteration, while Feature teams may or may not, based on dependencies.

Iteration Planning is required for all Iterations except for the first one, since there's nothing to cause a change in the PI plan yet.

When the teams define acceptance criteria during PI Planning, Iteration Planning is not strictly required during the PI.

True

False

Collaborate with Scrum Masters to establish the emergent design.

Collaborate with PMs, POs, and Agile Teams to establish the Architectural Runway.

Approve teams' increments into the mainline branch.

Approve all the design work of teams before they can implement their user stories.

Provide the designs behind each user story.

Demonstrate working software at each Solution Demo.

Develop her own Vision and Roadmap.

Attend key Value Stream events.

Product Owner

Business Owners

Scrum Master

COE

Product Management

True

False

Lead the teams

Proactively eliminate impediments.

Run successful Agile Release Trains.

Facilitate relentless improvement

Embrace the values of Lean.

Manage the most critical day-to-day activities of team members.

True

False

True

False

Funnel

Fixed date

Expedite

Standard

Accepted

Review