Agility & Extreme Programming

Question 1

Agile Development

Answer 1

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Question 2

Agile Development Principles

Answer 2

Agile development is a mindset, not a framework. Key principles include:
1. Satisfy customers with early, continuous delivery.
2. Embrace changing requirements.
3. Frequently deliver working software.
4. Build around motivated individuals.
5. Keep it simple.

Question 3

XP - Practices: Planning game

Answer 3

• Customers decide the scope and timing of releases based on estimates made by programmers
• Programmers implement only functionally demanded by stories in this iteration

Question 4

XP - Practices: Small releases and short release cycles

Answer 4

• Working system early
• Releases anywhere from daily to monthly

Question 5

XP - Practices: Metaphor

Answer 5

A story that customers, programmers, and managers can tell about how the system works

Question 6

XP - Practices: Test driven development

Answer 6

• Programmers write unit tests
• Customers write functional tests

Question 7

XP - Practices: Refactoring

Answer 7

• System evolves though transformations of existing designs
• A change that leaves system behavior unchanged, but enhances its quality

Question 8

XP - Practices: Pair programming

Answer 8

All code is written by two people at one screen, keyboard, mouse

Question 9

XP - Practices: Continuous integration

Answer 9

Not more than one day between code integration

Question 10

XP - Practices: On-site customer

Answer 10

A customer sits with the team full-time

Question 11

XP - Practices: Collective ownership

Answer 11

Every programmer improves any code anywhere in the system at any time if he sees the opportunity

Question 12

XP - Practices: Coding standards

Answer 12

Sign up to follow team rules

Question 13

XP - Practices: 40-hour weeks

Answer 13

No one can work a consecutive week overtime

Question 14

XP - Benefits

Answer 14

• Changing requirements are handled
• A useful system version is developed early

Question 15

XP - Problems

Answer 15

1. Lack of central and important documents
   - Requirement specification, system design:
   a) Are test cases able to substitute requirements
   b) The architecture is only in the heads of the architects
2. Traceability
   - Changing requirements and new design decisions imply modified and new test cases
3. Test cases have to be maintained very well
   - expensive!