Scrum, XP Flashcards

1
Q

What does scrum call the daily standup meeting?

A

The daily scrum

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

What three questions are asked at the daily scrum?

A

What work have you done since the last meeting? What are you planning to do today?
What obstacles are you encountering?

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

What happens at the sprint review meeting?

A

This half-day meeting is attended by the team and key stakeholders the purpose is to show the new product functionality why discussing features for next sprint

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

What happens at a sprint retrospective?

A

In this meeting the ScrumMaster works with the team to tune it’s own development process. Since teams are self organizing and self managing they focus on what worked and what needs improvement and make necessary adjustments the Scrum framework.

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

Who writes the user stories in scrum?

A

The product owner

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

Who has primary responsibility for the product backlog, grooming, and prioritizing it?

A

The product owner

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

What works better on a scrum project generalist or specialist?

A

In a scrum project teams are self organizing and self managing. Their primary job is to develop the product. Ideally team members are generalist and highly interchangeable

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

Who is ultimately responsible for results on a scrum project?

A

Team

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

Who helps the team files from processes?

A

The scrum master

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

What are the three pillars of scrum?

A

Visibility, inspection, and adaptation

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

Who created scrum and when?

A

Ken Schwaber and Jeff Sutherland in the early 1990s

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

Who developed XP?

A

Kent Beck

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

What do both programmers do when doing extreme programming on a XP project?

A

One programmer works on writing the code and the other program observes with a focus on higher level issues such as integration and functionality. Think Pilot and Navigator

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

Is test driven development part of XP?

A

Yes after the planning meeting programmers work in pairs using the acceptance criteria to build test cases this is known as test driven development

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

Would you see a swarm of an XP project?

A

Yes after the test is defined the team “swarms” the task in the pairs to develop them.

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

What are the 12 practices of extreme programming?

A
  1. Continuous integration
  2. Re-factoring
  3. Planning game
  4. Small releases
  5. Testing
  6. Pair programming
  7. Simple design
  8. On-site customer
  9. Collective code ownership
  10. Coding standards
  11. Metaphor
  12. Sustainable pace
    Stop sock cum stains
17
Q

What are the six basic principles of extreme programming to begin with?

A
  1. Continuous integration
  2. Re-factoring
  3. Planning game
  4. Small releases
  5. Testing
  6. Pair programming
18
Q

what are the seven principles of lean?

A
  1. Decide as late as possible.
  2. Amplify learning
  3. Deliver as fast as possible
  4. Build integrity in
  5. Empower the team
  6. Eliminate waste
  7. See the whole
19
Q

Who invented lean ?

A

lean software development was adapted from Toyota and their revolutionary manufacturing program

20
Q

What is meant by the lean principle of eliminate waste?

A

Lean is ruthless about eliminating waste. Waste may take on many forms. It may be in the form of excessive meetings, planning, documentation, testing, or any function. The key question is could we have achieved a positive result without doing the step. If the answer is yes it should be eliminated.

21
Q

What is meant by the lean principle of amplify learning?

A

The pursuit of lean is marked by continuous learning and improvement, and no matter how good the team gets, there are always opportunities to improve.

22
Q

What is meant by lean principle build integrity in?

A

Re-factoring is also a part of building integrity in. When re-factoring, you are a sensually reorganizing the code, and aligning it conceptually with the solution.

23
Q

What is meant by the lean principle see the whole?

A

The solution the team creates should look and feel like a solution and not like ten separate solutions cobble together. This is accomplished by seeing the entire solution, and this includes more than just the technical components.

24
Q

What are the seven main types of waste in Lean?

A

The seven main types of waste are transportation, inventory, motion, waiting, overproduction, overprocessing, and defects.

25
Q

What type of waste is email?

A

The waste type extra motion. If excessive or unnecessary emails and documents get forwarded it multiple times sometimes with large attachments due to multiple distribution groups it constitutes waste of type motion.

26
Q

What is the waste type extra transportation?

A

Extra transportation refers to unnecessary motion or movement of raw materials or goods such as a work in progress being transported from one operation to another.

27
Q

What is the meaning of Kaizen?

A

The word Kisaan means continuous improvement it is a system of continuous improvement in quality technology, process, company culture, productivity, safety, and leadership. It comes from the Japanese word “Kai” which means “change” or “to correct” and “zen” which is “good”

28
Q

What does the word jidoka mean?

A

Jidoka is a Japanese term used for automation meeting “intelligent automation “or “humanized Automation” In practice it means that an automated process it is sufficient “aware” of itself so that it will detect when the desired quality is produced, detect process malfunctions, detect product defects, stop itself and alert the operator. A future goal of automation is self correction.