2

Question 1

What is an iteration?

Answer 1

Time boxed, never extended.
Fixed duration of weeks
Each iteration has the same construction :

Start|Realise | evaluate
Which is basically:
Plan |Develop|retro

Question 2

What is product backlog ?

Answer 2

The list of all work items is called the product backlog

Question 3

What is Iteration backlog

Answer 3

The list of work items selected in each iteration is called iteration backlog

Question 4

Key points in iteration :

Answer 4

Expressed in story points
Story points are related size and effort of work items

Question 5

What are story points?

Answer 5

Are relative values / figures

Question 6

Key factors of story points:

Answer 6

The amount of work to do
Complexity
Risk and uncertainty

Question 7

What is the scrum process?

Answer 7

Scrum: Iterative and incremental process.
Iteration (Sprint): Realization activities.
Increment: Shippable output of an iteration.
Inspection: Daily team review, inspection of activities, and adaptation.
Product Backlog: List of project-driving requirements.

Question 8

What are the 4 types of meetings for inspection and adaptation?

Answer 8

Sprint planning
Daily scrum
Sprint review
Sprint retrospective

Question 9

What is product backlog?

Answer 9

Definition: List of project-driving requirements.
Purpose: Guides the development process.
Dynamic: Evolves throughout the project lifecycle.

They involve items called user stories

Question 10

What is a user story?

Answer 10

Definition: Functional chunk providing value.
Purpose: Breaks down system requirements for incremental delivery.
Focus: Describes desired customer experiences.
Components: User type, desired outcome, and rationale.

Question 11

What is a template of user story?

Answer 11

StoryAs a < type of user >, I want < some goal > so that < some reason >.
For example, As a user, I want to be able to indicate folders not to ba

Question 12

User story vs requirement

Answer 12

User Story:
Focuses on user experience.
Example: “As a customer browsing through the holiday website, I always want to have a ‘Check Availability’ button on any holiday page.”

Requirement:
Defines functionality or constraint.
Example: “The holiday website must include a ‘Check Availability’ button on every holiday page.”

Question 13

Product backlog structure

Answer 13

ID:

Definition: Unique auto-incremented number for tracking.
Purpose: Prevents loss of story tracking during renaming.
Description:

Format: “As a <type>, I want <some> so that <some>."
Purpose: Specifies user needs and motivations.
Priority:</some></some></type>

Format: Product owner’s rating (e.g., 10, 150; 1 = highest importance).
Purpose: Determines story importance.
Initial Estimate:

Format: S, M, L, XL (later converted to story points).
Purpose: Provides initial assessment of story size.

Question 14

Who’s responsible: product backlog?

Answer 14

The product owner maintains the backlog

The team and product owner can contribute to the product backlog

The product owner is the only one who’s allowed to prioritise user stories

Question 15

Good stories (INVEST MODEL)

Answer 15

Independent: Stories can be done separately.
Negotiable: Can be adjusted during development.( the best user stories can be written in a sentence or 2)
Valuable: Adds value to users or stakeholders.
Estimable: Effort can be estimated.
Small: Can be finished in one go.( stories need to be of a size which you can build a few of them in each iteration)
Testable: Can be tested for completion.

Question 16

What are epics?

Answer 16

EPICS are user stories that do not comply with the INVEST model

An EPIC is a large User Story that can be split into smaller user stories

Question 17

Split the epic” as a manager I want to manage the accounts of my clients “

Answer 17

As a manager, I want to search client accounts by name or ID so that I can quickly find specific accounts.

Question 18

Initial Estimation of User Stories

Answer 18

• Timing: Begin estimating when writing stories.
• Epic Identification: Identify large or complex stories (epics) for further breakdown.
• Example:
  
  • Ambiguous Story: “It should be easy for the user to diagnose a failure.”
  • Clarification: What does “easy” mean? What action triggers diagnosis?
  • Customer Interaction: Seek clarification on user expectations and actions.
  • Refinement: Break down large stories into smaller, estimable tasks.

Question 19

What is t shirt estimation?

Answer 19

Each member has 4 cards : S M L XL

All members choose one

Then show their card to each member simultaneously

Question 20

What is backlog refinement meeting?

Answer 20

a meeting where the team, scrum master and product owner work on refining the product backlog

Question 21

3 steps of backlog refinement?

Answer 21

1. Estimate the effort of user stories
2. Clarify the user stories
3. Identify epics and breakdown down

Question 22

What is plan it poker

Answer 22

An estimation tool for estimating S M L XL