Question 1

Sprint Backlog

Accepted Answer

The Sprint Backlog is one of the Scrum artifacts that creates transparency of the work of the current Sprint.

It is set of Product Backlog Items selected by the Developers for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

Question 2

Sprint Goal

Accepted Answer

Sprint Goal is the single (overarching) objective for the Sprint, achieved through the Increment.

Sprint Goal communicates why the Sprint is valuable to stakeholders, creates coherence and focus.

Collaboratively defined by the Scrum Team during Sprint Planning.

Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it.

The progress toward the Sprint Goal is inspected on daily basis during the Daily Scrum.

If the Sprint Goal becomes obsolete, the Sprint could be cancelled.

Question 3

Swarming

Accepted Answer

Swarming is a simple way where as many team members as possible work simultaneously on one highest value item. All team members focus on completing this one item before picking the next highest value item.

Working on many items / initiatives at a time increases work in progress, that causes delays and eventually waste of time.

Question 4

Sprint Review Attendee Satisfaction

Accepted Answer

Sprint Review Attendee Satisfaction is a measure of how satisfied the stakeholders, and customers, are with the outcomes and demonstrations presented during the Sprint Review. It helps the team gauge whether their work aligns with the stakeholders' expectations and if improvements are needed.

Like a movie rating, it's not possible to get 10/10 rating from everyone. It's important to observe a pattern, rather than individual rating and make adaptations as needed.

Question 5

Forecast

Accepted Answer

Forecast is selecting how much work can be completed within a Sprint. Developers use empirical information to forecast their Sprint scope during Sprint Planning. Forecast is not a guarantee.

Also see: Sprint Planning

Question 6

Stakeholders

Accepted Answer

Anyone with a stake / interest in the Scrum Team and it's outcomes could be a stakeholder to the Scrum Team. Stakeholders could be internal as well as external to the organization.

Internal stakeholders may be people from various functions / departments of the organization such as: finance, sales-marketing, infrastructure, customer support, release management, etc.

External stakeholders may include clients, paying customers, end users, consumers, prospects, etc.

Question 7

Product Roadmap

Accepted Answer

Product Roadmap visually represents the strategy and vision of the Product Owner. It may contain the high level requirements in order of customer value, and the direction of the product over time.

Question 8

Timebox

Accepted Answer

Timebox is a maximum duration allocated for an activity / event. Scrum Events are Timeboxed to keep everyone focused on the agenda of the event. Timeboxing also reduced risk by limiting the time a team would spend on a particular activity.

Question 9

Sprint Planning

Accepted Answer

Sprint Planning is one of the prescribed Events within the Scrum framework. Conducted at the beginning of every Sprint where the work to be performed for the Sprint is planned.

Sprint Planning addresses the Why, What, and How of the sprint work.

Question 10

Return on Investment (ROI)

Accepted Answer

Return on Investment (ROI) is a ratio of the gains from an investment over the investment.

ROI = Gains / Investment

For Example: Implementing a set of features required an investment of $100K, and after implementing those features, the product generated additional $300K in profitability.

In this case the ROI = ($3,00,000 / $1,00,000) = 3.

Question 11

OKRs

Accepted Answer

Objectives and Key Results (OKR) is a goal-setting framwork to establish focus towards delivering results that truely matter and to direct all initiatives toward measurable strategic outcomes.

OKRs are goal-setting metrics that are meant to be measurable, time-bound, achievable, relevant, and specific.

OKRs are expressed in a format that employees can easily understand. The use of OKRs allows all employees to focus on what’s most important to the company as a whole.

Question 12

Tools

Accepted Answer

The purpose of using any tool in a Scrum implementation is to create transparency.

Which tool is used by a team / org does not matter, as long as it's simple and serves the team's purpose.

From surveys, the most teams (83%) use MS Excel or Google Sheets.

Here is a list of some of the tools used:

MS Excel / Google Sheets
Jira
Trello
Digital.ai
MS Azure DevOps
Rally
IBM Rational

there are about a million tools out there etc.

As long as one knows how to use Excel well, one should be able to use the tool used by their organization.