Week 6

Question 1

What is Extreme Programming (XP)?

Answer 1

Started off as a payroll system at Chrysler. Customer-focused approach.
More detail than Scrum. It’s like a methodology rather than a framework like scrum.

Question 2

What do you need to do before you start writing implementation code?

Answer 2

write user acceptance tests.

Question 3

How many rules are in XP?

Answer 3

29 rules

Question 4

What makes a good design?

Answer 4

• Simplicity
• Choose a system metaphor rather than a vast document
• use CRC (class, responsibility, collaboration) card for design sessions to represent objects in the system. Nowadays people use UML diagrams instead of CRC.
• Create spike solutions (throwaway code) to explore options
• Never build anything into the system before it’s needed
• Refactor whenever and wherever needed.

Question 5

What is a spike?

Answer 5

a user story that will not make it into the final product. It is scheduled like any other user story. It produces throwaway code and resolves uncertainties.

Question 6

What are integration bugs?

Answer 6

When code is added, it can create new bugs with the stuff that’s existing.

Question 7

What is collective ownership?

Answer 7

Everyone owns all the classes (i.e. no one person is responsible for the class)

Question 8

What are the XP values?

Answer 8

They are the ethos of the teams.

1) Communications - convo should be frequent in the team
2) Simplicity - design and code for now rather than designing everything first
3) Design for now
4) Practices - pair programming, test driven dev, continuous integration, programmer welfare