Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Scrum test > Scrum Events > Flashcards

Scrum Events Flashcards

1
Q

When do we finish each Sprint?

A

Exactly when the timebox is over; not when we are done with the items in the Sprint.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Can we change the timeboxed duration of Sprints?

A

We can revise it based on what we have learned in the project (e.g. from now on, let’s have 3-week Sprints instead of 2-week Sprints), but we shouldn’t change it in an ad-hoc basis (e.g. this time we have more to do, let’s have a longer Sprint this time {this is wrong}], and we shouldn’t change it during the Sprint.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Each Increment can be released (true or false?)

A

True. Each Increment should be potentially releasable. We don’t necessarily release them each time, but they should have this potential.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the Increment?

A

The latest version of our product at the end of each Sprint, which only includes the features that are 100% done in that Sprint, and the Sprints before.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Where do we store our plan for the Sprint?

A

Sprint Backlog.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Who should decide about the number of items we pick from the Product Backlog for the Sprint Backlog?

A

The Development Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How long is the Sprint Planning meeting?

A

8 hours for a one-month Sprint, and usually shorter proportionally for shorter Sprints.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How many Scrum Masters are there in Scaled Scrum?

A

There’s one Scrum Master role for each Development Team, and since this role can be part-time, one or a few people can occupy it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How many Product Owners are there in Scaled Scrum?

A

There’s only one Product Owner in each Scrum project, no matter how many teams you have.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Who’s responsible for calculating velocity?

A

The Development Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Delivering all items in the Sprint Backlog is the ultimate measure of success for the team (true or false?)

A

False! That creates problems because of the Parkinson’s Law, and it’s not even our real goal; the real goal is to generate business value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

How many people are in a Development Team?

A

3 to 9 developers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the two elements in the Sprint Backlog?

A

The Product Backlog items in the Sprint Backlog (e.g. user stories), and the tasks created for each item (aka “work”).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How many Product Backlogs are there in Scaled Scrum?

A

Just one! One product has only one Product Backlog, no matter how many teams are working on it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

The total size of items selected from the Product Backlog for the Sprint Backlog should be equal to the current velocity (true or false?)

A

False. Velocity is a guideline, and the developers usually pick a number of items with a total size that is close to the velocity, but it’s not necessary and they can pick fewer or more items.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How often should we measure the performance of the project?

A

At least once a Sprint (before the Sprint Review)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What’s the Definition of Done?

A

Everything we need to do for all Product Backlog items to call them “Done” (=complete).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

The Product Owner should not attend the Daily Scrum (true or false?)

A

False. The statement says that it’s not fine for the Product Owner to attend the Daily Scrum, but we know that anyone can attend any meeting if they don’t speak (only the Developers “participate”).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

The Product Owner can participate in the Daily Scrum (true or false?)

A

False! Only the Developers “participate”, other only “attend” and do not speak.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

How long is the Daily Scrum?

A

About 15 minutes. It’s not dependent on the length of the Sprint.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is a burn-down chart?

A

A chart that shows the remaining amount of work during time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Who can participate in the Daily Scrum?

A

It’s only for the developers, while others can be there, as long as they don’t speak. So, only the Developers “participate”, other can “attend”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Who owns the Sprint Backlog?

A

Development Team.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What are the two main things we do in the Sprint Review?

A

Demonstrate the Increment and tell the customer about the progress of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

When do we improve the product?

A

All the time, through refactoring.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Sprint Review is a formal meeting (true or false?)

A

False. It’s an informal meeting, meaning that we don’t expect formal approval from the customer.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

What is the adaptive delivery method?

A

Project is run in short steps, and each time, our understanding will be refined based on the feedback from the previous step, and the best plan for the next step will be designed based on our understanding. We “adapt” to the environment, instead of predicting how it behaves.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Agile is Scrum (true or false?)

A

False; Scrum is one way of being Agile, but not the only way. There are other methods available such as XP, DSDM, and Crystal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

What’s Incremental delivery?

A

The product is created and delivered in multiple steps. Each time is new version of working software with new features is made available; something that is potentially releasable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

What’s predictive delivery method?

A

The expectations are fully identified in the beginning, the product defined and planned, and then a full plan for creating that product is created.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

What’s the delivery approach behind Agile?

A

Adaptive.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

What’s the delivery approach behind “waterfall”?

A

Predictive.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Scrum is Agile (true or false?)

A

True; Scrum is one way of being Agile, but not the only way. There are other methods available such as XP, DSDM, and Crystal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

What are the two characteristics of Product Backlog items?

A

They should be non-technical and independent of each other.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

What’s the Product Backlog?

A

A dynamic list of things we want to add to our product sorted based on their business value.

36
Q

Why should the Product Backlog items be non-technical?

A

Because we also use them to create an understanding for the customer, who may be non-technical.

37
Q

Why should the Product Backlog items be independent?

A

Because we want to order them freely based on their business value.

38
Q

The Product Backlog should be completely defined in the beginning of the project (true or false?)

A

False. The Product Backlog is never complete; it’s a dynamic concept that is always changing to reflect our adaptation

39
Q

What are the different ways of ordering Product Backlog items?

A

Only based on business value

40
Q

Given that we don’t have technical items in the Product Backlog, what happens to the technical things we need to do in the project?

A

Those will be done as part of the normal, non-technical Product Backlog items: the first time we need them.

41
Q

Who’s ultimately responsible for the Product Backlog?

A

Product Owner

42
Q

Where do we store the non-functional features?

A

Mostly in the Definition of Done; sometimes in the Product Backlog.

43
Q

What’s the template for user stories?

A

As a {user}, I want to {do something} [, so that {purpose}]

44
Q

All Product Backlog items must be user stories? (True or False?)

A

False. It’s a good idea to compose them as user stories, but it’s not necessary in Scrum.

45
Q

What happens to the items that are not “Done” until the end of the Sprint?

A

They go back to the Product Backlog (not automatically to the next Sprint Backlog)

46
Q

Product Owner can be influenced by other people (true or false?)

A

True; e.g. the customer

47
Q

Do we still need to have a Scrum Master if the team is mature in using Scrum?

A

Yes, always. The least is that the Scrum Master removes their impediments.

48
Q

Product Owner can delegate some of their responsibilities to others (true or false?)

A

True. But not a good idea.

49
Q

What’s done in the Sprint Zero?

A

There’s no Sprint Zero, hardening Sprint, integration Sprint, etc. All Sprints are the same.

50
Q

Who decides when to release the Increment?

A

The Product Owner

51
Q

Who has the authority to cancel the Sprint?

A

The Product owner

52
Q

What’s technical debt?

A

The low quality aspects of the code that doesn’t create problems for its current features, but will make it difficult to change the code and add more features in the future.

53
Q

Does the Sprint Backlog change during the Sprint?

A

Yes; we always change the tasks (aka work)

54
Q

Is it fine to re-estimate?

A

Yes!

55
Q

What are the two main things a Scrum Master does?

A

Ensures that the Scrum framework is followed properly and removes impediments.

56
Q

Who’s the main contact point with the customer?

A

Product Owner

57
Q

What do we do between the two Sprints?

A

Nothing! Each Sprint comes immediately after the previous one.

58
Q

Is Scrum Master a manager?

A

Yes. They don’t manage people though, they manage the process.

59
Q

What are the two parts of Sprint Planning?

A

What / How

60
Q

We can add a Project Manager role if needed (true or false?)

A

False. We don’t have additional roles in Scrum.

61
Q

When do we improve the way we work?

A

All the time. At least once every Sprint, in the Sprint Retrospective.

62
Q

Who helps the Scrum Team members find proper techniques for their work?

A

The Scrum Master

63
Q

It is fine to have a part-time Product Owner?

A

Yes

64
Q

Who assigns work to the developers?

A

The developers themselves

65
Q

Who facilitates the meetings?

A

The people involved in the meeting. However, the Scrum Master can take over this responsibility as requested or required.

66
Q

What does it mean to say that the Development Team is cross-functional?

A

The team, as a whole, has all the skill needed for the project. Each person in side the team has one or a few skills, and the combination becomes cross-functional.

67
Q

Is it fine to compare the velocity of the teams?

A

No, because velocity is relative. On the other hand, the main measurement is only value creation.

68
Q

Is it OK to have a PMO?

A

Yes, if they are focused on program and portfolio management levels, or other things that do not disturb the project system.

69
Q

Who’s responsible for composing the Sprint Goal?

A

The whole Scrum team

70
Q

We don’t have testers in Scrum (true or false?)

A

We have people who are expert in and focused on testing, but we call them “developers”, not “testers”. “Tester” is a title, and we don’t have titles in Scrum.

71
Q

The forecast for the completion date of the project is calculated based on the trend line in a burn-down chart (true or false?)

A

False. That trend line is just a guide, and we should consider other elements too. On the other hand, using burn-down charts is not even necessary, so you may not have it in your project.

72
Q

What does it mean when we say that the Product Owner should be respected by everyone?

A

No one should allow themselves to override the decisions of the Product Owner (e.g. the other of items in the Product Backlog)

73
Q

Who makes the technical decisions in the project?

A

The Development Team

74
Q

What stays unchanged during the Sprint?

A

Composition of the team, quality goals, items in the Sprint Backlog (tasks always change), Sprint Goal, Definition of Done

75
Q

When user acceptance testing is done?

A

During the Sprint (not in the Sprint Review)

76
Q

How many Product Owners are there in Scaled Scrum?

A

There’s only one Product Owner in each Scrum project, no matter how many teams you have.

77
Q

What’s scaled Scrum?

A

When there are multiple teams working on the same product.

78
Q

What are the “opportunities to inspect and adapt, and enable critical transparency”?

A

Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; but not the Sprint itself!

79
Q

Do we have baselines in Scrum?

A

No

80
Q

The product is improved in the Sprint Retrospective (true or false?)

A

False. Sprint Retrospective is for improving the way we work. The product is improved by refactoring, which is done during the Sprint.

81
Q

What’s done in the hardening Sprint?

A

There’s no Sprint Zero, hardening Sprint, integration Sprint, etc. All Sprints are the same.

82
Q

What does it mean to say that the team is self-organized?

A

The find their own way instead of receiving orders.

83
Q

Who’s ultimately responsible for the work done during the Sprint?

A

All developers collectively

84
Q

The developers should be full-time (true or false?)

A

False. It’s highly recommended to have full-time, dedicated developers who only work on one project at a time, but it’s not necessary.

85
Q

Who helps the organization implement Scrum in the organization?

A

The Scrum Masters

Scrum test (8 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions