Why are big stories considered an anti-pattern?

It makes it difficult to apply iterative, incremental DEV

If a team insists that big stories cannot be split how would the SM coach them to do otherwise?

Demonstrate story-splitting techniques using a specific case

What is a recommended story-splitting technique for agile teams?

Implement the happy path first and the other scenarios later

What is an example of an organizational structure anti-pattern?

The Dev team's manager is also the Product Owner

What is an example of an anti-pattern a Scrum Master might face?

Developers do not work collaboratively on stories

What is NOT a team retrospective anti-pattern?

When the team commits to working on 1-2 improvement items

What is a typical anti-pattern with Product Owners?

PO design a solution before bringing the intent to the team

What is an example of team tasking anti-pattern?

The team focuses on task completion over acceptance criteria

What anti-pattern can emerge during the Scrum of Scrums?

SM report on the teams´ tasks status each day

studbud

SASM - 03. Exploring Agile and Scrum Anti-Patterns

10 termsStudBud Administration108 plays

A SASM practice test

Flashcards10 cardsFPractice quizPHost liveL

Questions 10

Answers

1
Why are big stories considered an anti-pattern?
It leads to oversimplified designs
The Fibonacci estimation scale is harder to apply
It makes it difficult to apply iterative, incremental DEV
They require Product Manager approval because of multiple AC
2
If a team insists that big stories cannot be split how would the SM coach them to do otherwise?
Emphasize that the rules of Agile methods require splitting
Demonstrate story-splitting techniques using a specific case
Establish incentives to encourage story splitting
Invite the Dev Manager to a team meeting to emphazise it
3
What is a recommended story-splitting technique for agile teams?
Validate design w/stakeholders and build functionality later
Implement the happy path first and the other scenarios later
Start with data structure, later the business logic & UI
Implement the story UI first, build the business logic later
4
What is an example of an organizational structure anti-pattern?
The Scrum Master runs backlog refinement
The Dev team's manager is also the Product Owner
Dev team members rotate the role of the Scrum Master
There is 1 Product Owner for 2 teams
5
What is an example of an anti-pattern a Scrum Master might face?
Teams that keep stories small to suppor team iteration
A product owner representing the "voice of the customer"
Developers do not work collaboratively on stories
Teams coordinate with other teams
6
What is NOT a team retrospective anti-pattern?
When the team's people manager comes to observe
When the team commits to working on 1-2 improvement items
When the SM decides the topic and directs on specific items
When only part of the team attends
7
What is a typical anti-pattern with Product Owners?
PO design a solution before bringing the intent to the team
PO brings the business problem to the team & asks a solution
PO ask the team to help in writing user stories
POs facilitate story gromming sessions with the team
8
What is an example of team tasking anti-pattern?
The team closes the story only after all tasks are complete
The team focuses on story completion over task completion
Members work separately on individual tasks for the same US
The team focuses on task completion over acceptance criteria
9
What is an anti-pattern to motivation?
Market disruption
Individualized compensation
Maximizing purpose
Team goals
10
What anti-pattern can emerge during the Scrum of Scrums?
SM bring risks and impediments for escalation
SM report on the teams´ tasks status each day
SM work with the RTE to resolve risks and impediments
SM have a daily 15-min meet-after with the RTE

SASM - 03. Exploring Agile and Scrum Anti-Patterns Flashcards | StudBud