You are on page 1of 14

The purpose of a WIP constraint is to ensure that a team has enough work to do.

TRUE
FALSE

Having smaller batch sizes are good practice since they ensure a higher throughput with lower variability.
TRUE
FALSE

Paavan is a good Product Owner. It's day 7 of the sprint and his team ("The A Team") tells him that they
may miss their sprint commitment. What does Paavan do?
He supports pulling a story which hasn't been started.
He agrees with adding a person from the system team to complete the work.
He supports adding an unscheduled hardening sprint directly after the current sprint.
He buys the team pizza so that they can work late and get back on track.
He asks that they skip testing and add a testing story to the next sprint.
He suggests that they rename themselves "The B Team."

Who is involved more with Acceptance Criteria than Acceptance Tests?


The Scrum Master
The Product Owner
The Developers
The Testers

This meeting occurs at the end of each team's sprint and its purpose is to identify opportunities for
continuous improvement
The Backlog Refinement Session
The Mid-Sprint Review
The Task Breakdown Meeting
The Sprint Retrospective Meeting
The Problem-Solving Workshop

The Sprint Demo


Inspect & Adapt
In SAFe, which backlog contains the user stories a team may be working on?
The Product Backlog
The Team Backlog
The Sprint Backlog
The Sprint Review Backlog
The System Backlog
The Portfolio Backlog

What are the three levels of the Scaled Agile Framework?


Portfolio, Program, and Project
Investment Theme, PI Objective, and Sprint Goal
Portfolio, Program, and Team
Epic, Feature, and Story
Story, Acceptance Criteria, and Task

All the following are XP practices except:


Bug Fixing
Pair Programming
Continuous Integration
Test-Driven Development

The responsibilities of the Scrum Master include all of the following except::
Facilitating discussions among the team
Removing impediments that are in team's way
Ensuring that everyone on the team is doing their job
Participating in the Scrum of Scrums

The Product Owner is involved in all of the following except:


Writing the user stories and their acceptance criteria
Clarifying user stories for the team
Determining whether the sprint needs to be extended in order to for the team to complete the
committed user stories
Defining the Sprint Goals
Engaging team stakeholders
Negotiating scope
All of the above are responsibilities
None of the above are responsibilities

Capacity allocation refers to what?


The balanced allocation of resources to users stories, refactors, and maintenance
The teams working on a feature during a PI
Adjustments made to the program backlog based on the release predictability report
The normalization of velocity during the Release Planning Meeting
The adjustments made to velocity based on time off

In SAFe, what is the recommended length of a Sprint?


1 week
2 weeks
4 weeks
It depends on the number of people on the team
It depends on the number of teams in the program

The "I" in INVEST stands for:


Improvement
Individual
Interaction

Infrequent
Intuitive
Independent
I don't care

What is the recommended size of a scrum team?


3 - 5 people
5 - 7 people
5 - 9 people
8 - 12 people

In creating agile teams, we first try to organize them by:


Features
Departments
Components
Subsystems
Layer in the system stack

The System Team is responsible for all of the following except:


Breaking down non-functional requirements into tasks at each program teams' sprint planning
meeting?
Building and supporting development infrastructure
Conducting end-to-end testing
Acting as an interface to deployment
Supporting the demonstration of the integrated solution to stakeholders

The Product Owner is a member of the agile team.

TRUE
FALSE

The Product Owner participates in estimating user stories:


TRUE
FALSE

Someone tells Mary the manager that the Lion team has "ba." She looks in on their Sprint planning
meeting and likely sees what?
Their Scrum Master leading the planning meeting with no impediments on the risk board
The product owner refining backlog while the team is waiting
The team vigorously discussing implementation details
The testers uncomfortably signaling for Mary to come in

When estimating size, story points should take into account all of the following except:
Complexity - how hard is it?
Priority - how important is it?
Uncertainty - what's not known?
Volume - How much is there?

Why do we use the Fibonacci sequence (1, 2, 3, 5, 8...) when estimating?


It reflects the uncertainty in estimating larger items
It results in greater precision
It can be used to predict unit test coverage
It serves as a way to communicate delivery date to upper management

We want to establish a team's initial velocity using normalization. A team has 2 testers, 3 developers, 1
full time Scrum Master, and a Product Owner split between two teams. What is their normalized velocity
before calculating for time off?
40

48
50
52
65

A user story specifies all of the following except:


Who
What
How
Why

In the context of a user story, a role can be:


A person
A device
A system
All of the above
A and B
A and C

The "3 C's" is a popular guideline for writing user stories. What do the letters stand for?
Cause, Clarify, Conform
Concept, Conversation, Confirmation
Card, Concept, Clarification
Card, Conversation, Confirmation
Concept, Conversation, Confirmation

John's Scrum team finishes coding all of their stories in the first six days of the sprint, tests them in the
following two days, and fixes bugs in the days remaining. John's team is...
Applying the practice of hardening

Applying the agile development practice of "separation of concerns"


Using highly incremental practices to build working software in a timebox
Waterfalling the sprint

Which of the following examples is NOT an acceptable way of splitting user stories to fit into a sprint?
Deliver only the happy path functionality
Don't develop for scalability
Implement only a portion of the business rules
Deliver only the portion of the code which has been tested
Limit the functionality to only one step in the workflow process

SAFE supports a simplified method of prioritizing user stories at sprint boundaries. This simplified
method should take into consideration which two variables?
Risk and Size
User Value and Risk
Risk and Time Value
Size and Time Value
User Value and Size

Tito the tester is finishing the acceptance criteria for a user story during sprint planning. The number of
letters in the acceptance criteria should be...
...more than the number of letters in the user story
...about the same as the number of letters in the user story
...less than the number of letters in the user story
None of the above. Acceptance criteria should not be written during sprint planning

In SAFe, Which of the following does NOT belong in the team backlog?
User Stories

Spikes
Epics
Refactors
Technical Stories

In addition to User Stories, what typically replaces detailed requirements documents?


Features
Unit tests
Spikes
Acceptance Criteria
Task Boards

Which of the following is typically NOT included in the definition of done for a user story?
All acceptance tests pass
All coding standards are followed
The story is accepted by the Scrum Master
The code is peer reviewed
All tasks are done

Which of the following is NOT a recommended or required output of the Sprint Planning Meeting?
A Sprint Goal in clear business language
A production deployment plan
Tasks with estimates in hours
Commitment
An updated list of dependencies and blocking issues

Subject Matter experts can attend the sprint planning meeting


TRUE

FALSE

The team learned about commitment in their training. On the eighth day of the sprint, they realize that
they will not complete 5 of the 13 user stories because they were waterfalling the Sprint. The product
owner says she cannot negotiate the scope of the remaining user stories any further. What is the team's
best course of action?
Have an emergency Sprint Planning Meeting
Communicate the status of the sprint to all stakeholders
Abort the sprint
Adjust the velocity of the sprint
A or C
A or D
None of the above

How long is the daily scrum meeting?


3 minutes per person on the team
15 minutes
30 minutes
As long as it takes

Alexandra the developer has been late for the past week to the daily Scrum. Of the following, which is the
Scrum Master's best course of action?
Change the time of the daily Scrum
Pull Alexandra aside and ask her why she's late
Update the working agreements to clearly state the penalty for arriving late
Escalate the issue to Alexandra's functional manager

Does the phrase "untested code" exist in the SAFe ScrumXP dictionary?
YES
NO

Dylan the developer is following SAFe code quality coding practices. How often is he checking his code
back into the baseline?
After every unit test he writes
After each "pass" he takes through a user story
After a user story is accepted by a product owner
At the end of a sprint
During the IP sprint

What type of Agile testing is business facing, critiques the product, and is often manual?
Component Testing
Functional Testing
Exploratory Testing
Unit testing

In test driven development, when are the tests written?


While creating the Product Requirements Document (PRD)
Before the code is written
While the code is being written
After the code is written
Just before deployment ("just in time")

Which of the following are the recommended mid-sprint events?


The mid-sprint demo and backlog refinement session
The backlog refinement session and the stakeholder management planning session
The backlog refinement session and the mid-sprint review
The mid-sprint demo and the mid-sprint retrospective

No events are recommended mid-sprint

Hamid plots the first point on the team's sprint burndown chart. The y-axis unit of measure is in:
Days
Hours
Story points
Time Value
Velocity
User Value

Spikes should be demoed at the sprint demo:


TRUE
FALSE

Paul is new to agile and is trying to put together the list of people to be invited to the Sprint
Retrospective. Who should be on the list?
The developers and testers
The Scrum Master
The Product Owner
The Business Owners
The Stakeholders
All of the above
A and B
A, B, and C
C, D, and E

When is the System Sprint Demo conducted?

After every sprint


Mid-way through the PI
At the end of the PI
On demand

What is the typical length of the release planning meeting?


1 hour
4 hours
1 day
2 days
As long as it takes to achieve commitment

Which activity should NOT happen in a IP Sprint?


Program backlog refinement
Completion of stories from the PI
Creation of the release deployment package
Finalization of user, deployment, and/or installation documents

Which is the correct way of splitting stories into smaller stories?


Implement database structure first and then implement business logic and the UI
Implement the simplest variant of the functionality first and then implement the rest as an
enhancement
Develop the functionality first and test it as a second pass
Develop the UI with mocked business logic and database access and then add the actual
functionality behind the UI

Sprint goals (select the right answer):

Allow management to load teams with work in every sprint


Give management an idea of what the teams work on
Provide management with a tool to track scope change over time

Release planning in SAFe (select the right answer):


Involves everybody in the program for two days of planning
Involves products management and product owners on day one and rest of the team members on
day two
Is done individually by teams and requires collective presentation of the plans to stakeholders
Involves only team members that can effectively estimate work

The system demo (select the right answer):


Can be demonstrated from multiple different branches of code
All finished features are demonstrated out of a single branch of code while those that are in progress
are in demonstrated from feature branches
Is demonstrated out of a single branch of code

Some business domains don't have first degree user persona, but only have 2nd
and 3rd.
True
False

Code review can substitute a demo for component teams

True
False