Transitioning to Scrum

Question: What is the recommended Sprint duration when working with Scrum for the first
time?
Ans: Two weeks

Question: After the Sprint review, another meeting is held in which the Scrum Team has an
opportunity to examine how the last sprint went, identify things that went well and areas for
improvement. What is this meeting called?
Ans: Sprint retrospective

Question: Which of these are recognized as key values of Scrum?

Ans: Respect
Courage
Openness

Question: What are the three key Scrum roles?

Ans: Scrum master
Product owner
Dev team

Question: Which of these are recognized as main Scrum activities?

Ans: Sprint planning
Daily Scrum
Sprint retrospective

Question: What are the three primary artifacts in Scrum?

Ans: Increment
Product backlog
Sprint backlog

Question: The Scrum Master is a servant-leader for the Scrum team. Who does the Scrum
Master serve?
Ans: The Organization
The Development Team
The Product Owner

Question: Which meetings are considered to provide valuable inputs into Sprint planning
sessions?
Ans: Sprint retrospective
Sprint review

Question: Which of these statements accurately describe Scrum?

Ans: Teams work concurrently
Increased code quality
Scope is variable

Transition to Scrum: Agile Foundation to Scrum

Question: What are some of the common pillars between Agile principles and traditional
project management principles?
Ans: They both have Requirements, Design, Coding, Testing and Deployment steps

Question: Which of the following statements is a common misconception about Scrum?

Ans: Scrum is unmanaged

Question: How do Scrum and Lean agree?

Ans: Cooperation, focus on product, continuous improvement, similar mechanisms
Question: Which of the following best describes the overlap between Agile, Scrum, and Lean?
Ans: Agile and Lean are culture and mindset based, Scrum is an agile methodology

Question: How do Scrum and Agile differ?

Ans: Agile does not propose any timebox iteration length and cadence

Question: What is a common structure used to remember the Scrum Framework?

Ans: 3 roles, 5 events, 3 artifacts

Question: Which of the following is an example embracing the Agile mindset with Scrum?
Ans: The team always delivers the customer’s highest value item as a priority every sprint

Scrum Team Velocity: Exploring Team Velocity

Question: During a sprint, 15 story points were allocated to user stories in our sprint backlog.
Three story points were rolled over to the next Sprint. What then is our team’s velocity for the
completed sprint?
Ans: 12

Question: When is velocity calculated?

Ans: At the end of an iteration

Question: Which of these are valid metrics when calculating team velocity?
Ans: Story points
Hours
Days

Question: When completing a sprint in JIRA, you can select where all incomplete issues for a
sprint should be moved. What options are present on the complete sprint dialogue in the Move
to drop-down list?
Ans: New sprint
Backlog

Question: How can a Scrum Master help improve a Scrum team’s velocity?
Ans: By ensuring that the team works on one story at a time
By working with the product owner on user stories
By isolating the team from external noise and pressure

Question: Which of these are reasons that velocity is such a useful metric?
Ans: It gives the average amount of work a team can accomplish during sprint

Question: In the case study involving 729 solutions, what two things did the client want with
respect to their projects?
Ans: Accuracy
Flexibility

Question: Which of these statements accurately describe why Scrum Burndown charts alone
are not enough?
Ans: Burn down charts can’t distinguish velocity and scope change on a sprint

Question: As a measure of performance what does team velocity indicate?

Ans: The amount of functionality that a team can deliver within a sprint

Question: What productivity tool can be used for application integration to help improve team
velocity?
Ans: Zapier
 Lean in Scrum: Lean Development Practices
Question: The most successful innovations come when you carry out what tasks in an
organization?
Ans: Take insights from different business units
Gather intelligence

Question: What aspects of a sprint-based approach can assist with deferring commitment?
Ans: Feature driven development

Question: What are the most effective ways for a team to create and retain knowledge?
Ans: Documentation
Code Reviews

Question: The 7 wastes of Lean includes which of the following?

Ans: Defects
Motion

Question: The principles of respect and compassion need to be extended to what aspects of
an organization?
Ans: Process improvement
Recruiting and onboarding

Question: Which of the following is an example of Unnecessary Waste?

Ans: Waiting

Question: Which of the following are some common time-wasting scenarios in product
development?
Ans: Spending too much time planning ahead

Question: Building quality into products requires the utilization of what tools?
Ans: Pair programming
Automation

Scrum Master: Scrum for the Team

Question: What is a likely characteristic of a large team?
Ans: The Daily Scrum cannot fit into a 15-minute time block
There are many communication channels
The team participates in Scrum of Scrums

Question: What is a responsibility of the Scrum Master?

Ans: Remove impediments on behalf of the development team
Coach team members on Scrum best practices

Question: How does the Scrum Master provide service to the Product Owner?
Ans: Explains the importance of meeting attendance
Helps to prioritize the product backlog

Question: What are valid reasons to measure team velocity?

Ans: To forecast the number of sprints needed to complete the project
To estimate the amount of work that can be completed in a sprint

Question: What is an Agile principle?

Ans: Deliver frequently
Welcome change
Question: Rank the levels of planning from the highest coarse-grained level to the lowest fine-
grained level of detail.
Ans: Product vision
Product roadmap
Release planning
Iteration planning
Daily planning

Question: Who are the members of the Scrum Team?

Ans: Scrum Master
Product Owner
Development Team

Question: What is a characteristic of a Scrum team?

Ans: Self-organizing
Empowered
Cross-functional

Question: What is considered a pillar of Scrum?

Ans: Transparency
Adaptation

Question: What is an example of a Scrum artifact?

Ans: Sprint backlog
Burn-down chart
Scrum: Product Development Framework
Question: Which of the following is not a pillar of empiricism?
Ans: Planning

Question: A well formatted hypothesis contains what traits?

Ans: Can be tested in specific conditions
Quantifiable and measurable

Question: Which scrum events are times where we can identify and test assumptions?
Ans: Sprint Retrospective
Sprint Review

Question: The distance between the lines on a burn-up chart shows what?
Ans: The amount of work remaining

Question: The ideal user interview takes place with which individuals?
Ans: Two UX researchers and one user

Question: Identifying market needs requires which steps?

Ans: Establishing product uniqueness
Researching competitors

Question: When is a sprint review normally held?

Ans: At the end of a sprint

Question: Which of the following is the closest definition of MVP?

Ans: MVP is a strategy for testing your hypothesis and learning about your customers with minimal
investment

Question: It is essential to have which item(s) prepared for a successful sprint review?
Ans: Sprint Goal

Question: What did Dropbox’s successful MVP look like?

Ans: A 3-minute demo video
 Scrum Concepts & the Product Owner
Question: Match the product owners’ role or contribution to the different scrum events.
Ans: Sprint Review or Demo- Record feedback on sprint results and update the backlog
Sprint Retrospective- Share experience and expertise, contributing to continuous improvement
Sprint Planning- Explain prioritized product backlog user stories to the scrum team
Daily Scrum or Stand-up- Listen to the updates shared by the team
The sprint- Provide clarity and answer questions on the sprint backlog

Question: Match the scrum team member role to an aspect of that role’s collective product
ownership
Ans: Product manager- Program backlog and roadmap
Product owner- Backlog prioritization and vision
Scrum Master- Scrum process and coaching
Development Team- Delivery of user stories in a sprint

Question: Match the following estimation and idea generation tools to their methods
Ans: Poses questions to define the product- Vision Statement
Group like items for prioritization or estimation- Affinity Grouping
Allows for a range in level of agreement when yes or no is not enough- Fists of Five Voting
Excellent for determining yes/no opinions- Roman Voting
Determine most complex or most preferred option- Dot Voting

Question: What are the roles and responsibilities of the Product Owner?
Ans: They support the scrum team by clarifying requirements
They own and prioritize the backlog
They translate business needs into user stories

Question: What elements of the Scrum framework provide for effective development?
Ans: A prioritized product backlog
Daily standups to report on progress
A sprint planning session where sprint backlog is agreed to by scrum team

Question: What are some qualities that a strong product owner should possess?
Ans: Have strong leadership and team player skills
The ability to communicate with business and technical stakeholders
The ability to differentiate between end user needs and wants
Are available to the team and engaged throughout the release cycle

Question: What are some ways in which the product owner can define value for the scrum
team and process?
Ans: Work with stakeholders to determine current market priorities and trends
Thoroughly define ad decompose user stories including acceptance criteria and definition of done
Balance business and technical requirements

Question: How does a scrum product differ from a project?

Ans: A product is driven by a prioritized backlog
A product owner drives team direction rather than a project manager
Products can adapt to quickly change market demands

Question: In what ways can open ended-ended questions lead to product idea generation?
Ans: It can guide initial research areas and product focus
It provides insight into a user’s unique perspective
Respondents can think critically and provide honest opinions
 Applying Scrum Development Practices

Question: How can Scrum practices for retrospective meetings enable process improvement?
Ans: Meeting is facilitated by Scrum Master
Suggest improvements
Discuss failures and successes
Address 3 crucial questions

Question: Which Scrum practices can help better manage what is produced?
Ans: Task prioritization
Use a Scrum board
Setting Sprint goals
Estimating backlog items

Question: Which Scrum practices can help improve quality?

Ans: Collaboration tools
Release burndown chart
Sprint burndown charts
Plan to velocity

Question: What are benefits of adopting Scrum in a software development project?

Ans: Team decision making
Execution speed
Customer involvement
Direct value

Question: What Scrum practices can help improve team performance?

Ans: Involve stakeholders
Workshops
Keep team together
Teambuilding

Question: What Scrum practies can enable effective meetings?

Ans: Ask 3 questions
Set goals
Mandatory team member attendance
Choose location wisely

Product Development Practices

Question: What is an example of a practice that really helped the collaboration with a remote
team?
Ans: Co-location for start of the project to agree on process
Question: Which is not a benefit of refactoring?
Ans: Take very little time to do

Question: Which Product Owner best practice means to not take over other team member’s
responsibilities?
Ans: Stay in the middle

Question: What are two views on the primary goal of TDD?

Ans: Specification, programming technique

Question: What are the three steps in TDD?

Ans: Write failed test, write code to pass the test, refactor

Question: Which of the following is a benefit of continuous integration?

Ans: Robust code

Question: What does “everyone, everyday” mean in continuous integration?

Ans: Everyone commits their code to the baseline everyday

Question: Which is an expectation of the Scrum Master from the Product Owner’s
perspective?
Ans: Obtain team buy-in on the process

Question: Which of the following charts give a fuller big picture view of sprint and release
progress overtime?
Ans: Epic, product, and release burndown report

Scrum: Product Backlog

Question: What are the commonly used ordering techniques?
Ans: MoSCow model
Priority poker
Kano model

Question: What are the criteria for Product Backlog ordering?

Ans: Cost of implementation
Cost of delay
Change in business conditions

Question: What are the methods to manage different stakeholders for collectively agreeing on
value?
Ans: Start saying no to stakeholders
Stop treating all stakeholders equally
Focus on most important stakeholders

Question: What steps are involved in measuring value using bubble sort?
Ans: Compare story values one at a time
Move the lower value stories down one position
Start at the top of the list of stories

Question: What are the other names for Pareto principle?

Ans: 80/20 rule
Principle of factor sparsity
Law of the vital few

Question: What are the key differences between output and outcome?
Ans: Products delivered on-time and on budget represents Output
Outcome represents feelings of the user and is hard to be measured
Output can be measured easily
Question: What are the different attributes in Kano model?
Ans: Excitement attributes
Performance attributes
Threshold attributes

Question: What are the different ways to maximize Product Backlog value?
Ans: Ordering
Refinement
Definition of Ready

Question: What is the purpose of Product Backlog?

Ans: Ordered list of everything needed in the product
Evolves with the product
Single source of requirements

Question: What are the different collaborative ordering techniques?

Ans: Whole product
Mood++
Agile game incubator

Question: What are the guidelines for delivering business value?

Ans: Measure value regularly
Determine value initially
Release early and often

Scrum: Creating Effective Product Backlogs

Question: What are the benefits of using the minimum viable product method?
Ans: Address key risks
Gain knowledge
Faster launch

Question: What are the different ways to keep smaller backlogs?

Ans: Periodically review the product backlog
Maintain ready items only
Don't add far-off items

Question: What are the benefits of product backlog refinement?

Ans: Better forecasts
Reduced dependency
Improved value

Question: What are the steps for release planning?

Ans: Update the plan every sprint
Add a degree of confidence
Sketch a preliminary roadmap

Question: What are the key benefits of a prioritized product roadmap?

Ans: Brainstorm ideas
Identify priorities
Stakeholder buy-in

Question: What are the different communication methods in Scrum?

Ans: Product backlog
Meeting notes
Burndown chart
Question: Who is responsible for managing and adding to the product backlog?
Ans: Scrum master
Product owner
Development team

Question: What are the best practices for creating product backlogs?
Ans: Reorder the backlog frequently
Make the product backlog visible and easily accessible
Manage the size of the backlog

Question: What are the different categories of product backlog?

Ans: Technical debt
Business requirements
Features

Scrum Product: Defining the Why & How of the Product

Question: What are some strategies for mitigating potentially negative impact by external
influences?
Ans: Facilitate meetings and workshops to build consensus and make decisions
Include a broad range of stakeholder perspectives to ensure a well-rounded product direction
Communicate product vision, strategy, roadmap, and results widely and regularly

Question: What are some methods product owners can use to engage the customers when
grooming the backlog and documenting user requirements?
Ans: User interviews
Questionnaires
Focus groups

Question: Which of these questions are most helpful for defining a product in Scrum?
Ans: Who will use the product?
What is the value to the organization?
What need does the product solve or provide a solution for?

Question: What product discovery techniques help to deliver successful products?

Ans: Get a minimum viable product in front of users for feedback
Prepare a cost estimate and plan
Create a product vision

Question: What are some effective ways to conduct customer research for defining the
product?
Ans: Focus groups
Questionnaires
Interviews

Question: Match the stakeholder to their most relevant product requirement.

Ans: Product goals and targets- Management
Product requirements- Vendor
Product priorities- Influencer
Usability and user experience- Customer

Question: Which elements should be part of an evolving product strategy?

Ans: Understanding of the market and competitors
Defined product value and benefits
Statement of user community

Question: Which of the following elements contribute to a complete user story?

Ans: Definition of Done
Acceptance Criteria
Statement of what the user wants to do and the resulting value

Question: What are the elements of an empathy map that help the product owner and team
better understand the customers?
Ans: What does the user think about?
How does the user feel?
What does the user need to do?

Question: Map the responsibilities or artifacts to the correct role or owner

Ans: Scrum master- Scrum process, Removal of impediments
Product owner- Product backlog, Product strategy
Development team- Minimum viable product, Test and build automation

Scrum Artifacts and Investment Guidelines

Question: What is sequential dependency as it applies to the Scrum process?
Ans: Even with the sequential dependency on existing infrastructure, each user story should contain
an independent feature slice
It's expected when each story is somehow dependent on functionality or architecture being in place

Question: What are examples of PBI that might be contained in a product backlog?
Ans: A user story describing a feature
Risks or ideas
A defect or SPIKE
An epic describing an entire functional area

Question: The "V" in the INVEST guidelines for writing high quality user stories stands for
Valuable. What does valuable mean in terms of each user story?
Ans: Defines something that is of value to the end user

Question: What does the burn down chart illustrate?

Ans: The velocity of a sprint
At a glance, the initial amount of work taken in the sprint planning meeting
The estimated amount of work that's still remaining to complete during the sprint

Question: How are SPIKES used in the Scrum process?

Ans: Specifically intended for research, learning, and discovery
Not meant to implement any completed work for the product increment so SPIKEs do not have user
story points
Have clear objectives and an outcome

Question: Which statements describe the estimable criterion in the INVEST guidelines?
Ans: Every team member needs to agree on the estimate
The team is solely responsible for estimating the level of effort
The team will not be able to estimate the level of effort if the user story is not clearly defined

Question: The "N" in the INVEST guidelines for writing high quality user stories stands for
Negotiable. What does this mean as it applies to the Scrum process?
Ans: A good user story should capture the essence of the customer's requirements but not an explicit
contract
The team, product owner, and stakeholders need to negotiate what each user story is trying to
express

Question: Match the four Scrum artifacts to their basic roles in the context of the Scrum
process.
Ams: Items are ordered in a single queue with a single highest-priority item and often contain
user stories to capture product features- Product backlog
A graph, posted in a location visible to all, that's used to show the progress of the current
sprint- Burn down chart
Contains the items that will be worked in the next sprint and it's then frozen- Sprint backlog
Potentially shippable working code that has been tested and includes documentation- Product
increment

Question: Which symptoms could be indicators that a PBI is fat and requires splitting?
Ans: Any attached documents
Use of words like "all," "any," or "every"
Lots of information – for example, a very large description

Question: Which statements describe the product backlog?

Ans: The product backlog represents requirements, so every one of these items is saying what needs
to be done
User stories are refined and split into smaller user stories during the backlog grooming meeting
The product backlog items do not say how the team should fulfil the item

Question: What is one way of ensuring that a user story is testable?

Ans: Have the customer that submitted this user story tell the team how to test it

Question: Which criteria accurately describe high-quality user stories according to INVEST?
Ans: Stories should be sized appropriately at the top of the product backlog
The story is complete early allowing QA to test it during the sprint
The team are able to estimate and complete a good user story very quickly
A good user story is focused and easy to understand

Question: What is the definition of "Done" defined as in Scrum and what are its implications?
Ans: The definition of "Done" is used by the product manager to decide when completed work should
be included in the product increment
A combination of the acceptance criteria included in the user story and the best software practices
The team's definition during development to gauge when a task is finished
Only "Done" user stories gain the team the user stories' velocity points

Question: Which statements accurately describe the Scrum sprint backlog?

Ans: The team selects the highest-priority items and moves them from the backlog to the sprint
backlog at the sprint backlog meeting
The sprint backlog is updated each day by the Scrum master after the Scrum meeting
When the sprint backlog is at capacity, it's frozen