Roles & Team Structure
Events & Cadence
Metrics & Estimations
Reporting & Tools
Wild Guess
100

Role that distinguishes between soft impediments and hard blockers, track in Jira for visibility and check that Agile Team adds Jira comments with follow up actions and owners

What is a Scrum Master?

100

Meeting set to finalize feature delivery for the current PI by confirming stories meet DOR for the final 3 sprints

What is Mid PI-Planning?

100

Measures team change % of last 3 sprints

What is Team Churn?

100

In which category we can allocate Automation metrics (Outputs,  Performance, Planning or Inputs & Progress)

Performance

100

Which is the newest version number of the SAFe Scrum Master and RTE certifications?

6.0

200

Role that connects with engineering leads, architects, and product team to flag major dependencies and architectural decisions needed during PI-Planning

What is a Release Train Engineer?

200

Meeting in which Product brings to each Agile Team features that meet Feature Ready for next 1.5 PIs, and collaborates with Engineering to identify dependencies

What is Pre PI-Planning?

200

Metric that provides visibility into development roadmap for upcoming PI

What is User Story & Requirements Readiness?

200

Business KPIs are considered part of which category (Outputs, Performance, Planning or Inputs & Progress)

Outputs

200

JIRA issue type in which requirements are written "as a <>, I want <>, so that <>" with acceptance criteria

What is a Story?

300

Role that conveys to balance between addressing immediate customer needs and aligning with long-term product strategy

What is a Product Owner?

300

PI-Planning session in which the RTE review previous PI velocity and review upcoming PI capacity

What is Readiness?

300

Metric that tracks open defects by severity / priority

What is High Priority Defects

300

Agile Maturity health check metrics are considered part of which category (Outputs, Performance, Planning or Inputs & Progress)

Inputs & Progress

300

It is calculated by Scrum Masters for each Agile Team based on story points and velocity

What is Capacity?

400

Consists of 4-12 people; to be highly effective team needs to maintain small groups dynamics

What is an Agile Team?

400

PI Planning session that carries out a qualitative and quantitative review, retrospective to discuss areas for improvement, and identify potential solutions

What is Inspect and Adapt?

400

Statement: “Buckets are okay; be specific and provide informed estimates”  True or False?

True

400

JIRA issue type that, among others, includes refactoring work

What is Technical Debt?

400

Target cadence for Backlog Refinements during a Sprint (answer is not as a question)

2 to 3 per week

500

Consists of 50-150 people or 5-12 Agile Teams, to limit cost of alignment and ensure that people know each other

What is an Agile Release Team?

500

Event that happens on Day 5, between Retrospective and PI-Planning Conclusion, in PI-Planning schedule

What is Future PI Review?

500

Statement: Story Points are relative and unique for each team. True or False?

True

500

JIRA issue type related to software defects on launched features or features in development

What is a Bug?

500

Consists of 150-750 people or 1-5 ARTs, to coordinate a large initiative tied to material value delivery in one or multiple streams

What is a Solution Team?

M
e
n
u