Day2 Flashcards

1
Q

What is used to provide simple medium for gathering basic info about stories, recording high level requirements, developing work estimates and defining acceptance tests?

A

Story card

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

Using EVM should be measured at which level?

A

Release

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

A technique showing kanban work stages by comparing counted features over a time interval is called

A

Cumulative flow diagram

It visualizes progress of work. Team can monitor flow of work through its stages

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

Activity uses sequence of numbers 0,1,2,3,5,8,13..

A

Indicating priority of a story

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

3 criteria should be looked at when setting iteration length

A

Time frame to release, cost and team acceptance of the stories

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

Team velocity is used to:

A

Predict schedules for mature teams

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

An agile team best ensures product quality through

A

More frequent inspection after each iteration

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

Kaizen is change for the

A

Better

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

Estimating story based on its relationship to one or more other stories is

A

Triangulating

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

Team estimate they should complete 30 storypoints in iteration. Partway they realized they will complete 50. The team should:

A

Release members to meet the estimated velocity

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

Which of seven principles best to solve problem of inventories causing hidden errors

A

Eliminate waste

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

What do project reports show during the sprint review meeting?

A

ROI

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

Purpose of setting the stage in retrospective is:

A

Restate the goal of the meeting and create an open atmosphere

There are five phases:

  1. Setting the stage
  2. Gather data
  3. Generate insights
  4. Decide what to do
  5. Close the retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When facilitated and managed well, the primary benefits of retrospective:

A

Allow team to get ahead on release planning

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

Primary purpose of retrospective

A

Discuss what went well, what didn’t and ways to improve

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

For one month sprint, sprint planning meeting should be

A

8 hours

17
Q

Not a role on CP team

A

P.O.

18
Q

What type of breakdown structure used in agile?

A

Feature breakdown structure

19
Q

XP practices

A

Pair programming

Planning game

Continuous process

Coding standards

TDD

20
Q

Not lean principle

A

Time box events

7 lean principles: eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower team, build integrity and see the whole

21
Q

Kanban in Japanese means

A

Visual card

22
Q

First step in setting up kanban is

A

Map your current flow

23
Q

Which framework adopts and tailors methods such as scrum, xp, kanban and others in order to support scaling

A

Disciplined Agile Delivery (DAD)

24
Q

What is a product roadmap

A

A view of release candidates

25
Q

INVEST stands for

A

Independent

Negotiable

Valuable

Estimable

Small

Testable

26
Q

Self organizing team have the ability to:

A

Make local decisions

27
Q

3 week sprints, how many sprint review sessions?

A

3 hours

28
Q

Sprint review and sprint planning meetings durations

A

For sprint review, one hour each week

For sprint planning, 8 hours each month

29
Q

A report of all work that is “done”

A

Burndown

30
Q

The primary measure of progress

A

Working software

31
Q

User stories are

A

Negotiable

32
Q

Attributes of a product backlog

A

DEEP (detailed, estimated, emergent and prioritized

33
Q

Roles in pair programming

A

Driver and navigator