Quiz Archives - Yves Hanoulle

Last week I published an Agile Thursday Quiz about PairProgramming.
(You can found previous quizes at ATQ )

The quiz was created by Sallyann and you can find her answers below.

1. Which of the following has Pair Programming as a core practice?
b. Extreme Programming. Although pairing is useful in any other the others is it only described as a Core Practice in XP.

2. When pair programming, the most regularly used names to distinguishing which person is currently typing are:
c. Driver and Navigator. Some say the Driver types, while the navigator looks at the broader problem / real world level. I (Sallyann) dispute this though

3. In Jim Coplien and Neil Harrison’s book “Organisational Patterns”, pair programming is referred to as:
c. Developing in pairs. Illustrated with a lovely ‘Two Amigos’ picture.

4. Pair programming has not been shown to have a helpful effect on:
b. Pair programming has actually been shown to lengthen the amount of effort required to develop a feature, however this is considered a cheap price to pay for the eventual time saved through not having to fix the extra defects found in solo-developed code.

Do you want to learn more about PairProgramming?

Brian Marick wrote a nice post about pairing with Corey Haines
A Pair Programming Experience by Randal Jenson
You might want to spend a while on Wikiwiki: (If you have never been to the first wiki, make sure you take some time to look at everything written here.)

Research

Remote pairing:

//pairwith.us/ is nice if you want to see remote pairing in action
VS Anywhere (remote paring for Visual Studio)

Books:

You can also find these links and other on my delicious page for PairProgramming

Another Thursday that we have an ATQ. This time written by Sallyann Freudenberg. Some years ago, Sallyann has done reasearch around PairProgramming. Recently she started to reblog her research.
As a kind of publicity for her blog, I asked her, if she wanted to create an ATQ about PrairProgramming.
I hope you enjoy it, please write your answer in the comments.

1. Which of the following has Pair Programming as a core practice?

A) Scrum
B) Extreme Programming
C) Kanban
D) DSDM
E) Crystal Clear

2. When pair programming, the most regularly used names to distinguishing which person is currently typing are:

A) Parent and child
B) Master and Servant
C) Driver and Navigator
D) Coder and Designer
E) Teacher and Student

3. In Jim Coplien and Neil Harrison’s book “Organisational Patterns”, pair programming is referred to as:

A) Coding in Tandem
B) Delivering as a Duo
C) Developing in Pairs
D) Coding in Couples
E) Working in Twos

4. Pair programming has not been shown to have a helpful effect on:

A) The quality of delivered features.
B) The amount of effort (man-hours) it takes to develop a feature.
C) Knowledge-sharing.
D) Peripheral awareness via overhearing.
E) Problem-solving.

Last week I published the Agile Thursday Quiz about Retrospectives.
Here are the answers from Ben Linders. (who created these questions.)

1) When do you normally do a retrospective?
b is the best answer, all others are wrong or do not reflect the real intention of a retro.

2) Who should attend the retrospective?
a and c are both valid answers, this questions aims to trigger reaction if the PO should or should attend the retro.

3) What is the best way to do a retrospective?
a

4) What happens with the actions that come out of retrospectives?
b is the correct answer, e is not wrong but doesn’t emphasize enough that it is the team who takes action

Where to learn more about Retrospectives:

Book: Project retrospectives From Norm Kerth (If you are an independent consultant or like using your phone in your care, read his story.)
Book: Agile Retrospectives from Esther Derby & Diana Larsen

google University: Making Good teams great
My agile retrospective presentation: how to make retrospective the heart of your agile process

A few of my example Retrospectives

For this ATQ, Ben Linders helped me out with the questions.

1) When do you normally do a retrospective?

a) Just before the start of a sprint, to prepare everything that is needed to do the sprint
b) After the sprint review of each sprint, when you have all the input that is needed to reflect and decide upon actions
c) As a servant leader you only do it when the team asks for it, and as often as they think they need it
d) The retrospective is a part of the sprint review, where you reflect on the product and the process
e) Between the planning game and the sprint review, so that you can do improvements during the sprint

2) Who should attend the retrospective?

a) All team members
b) The scrum master and some of the team members
c) Everybody in the team, except for the product owner
d) Everybody who is attending the sprint review, to get as much feedback as possible
e) The product owner, team members, and their managers

3) What is the best way to do a retrospective?

a) There are many good ways to do retrospectives, the facilitor usually proposes a way to do it depending on the team needs and the issues at hand
b) You can use the the four key questions from retrospectives, as a minimum ask the team what went well and what should be improved
c) There is no best way to do a retrospective, as the purpose of a retrospective varies in agile projects
d) Team members should submit problems before the retrospective, and the scrum master decides what is most urgent to discuss
e) Most teams use sticky notes to collect actions what should be improved

4) What happens with the actions that come out of retrospectives?

a) They are given to the project manager so that (s)he can plan the actions and assign people
b) Team members will pick up these actions during the next sprint, to continuously improve their way of working
c) The scrum masters collects them and documents them in a report
d) There shouldn’t be much actions coming out, as the next sprint is already filled up with user stories
e) They are documented, and will be discussed in the next retrospective to check if they are finished

Please add your answers in the comments and on monday I’ll publish Ben’s answers.

Category: Quiz

Agile Thursday Quiz, Monday Answers: PairProgramming

Agile Thursday Quiz: PairProgramming

ATQ the monday answers: Retrospectives

Agile Thursday Quiz: Retrospectives

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Stay up to date