2/3 - Agile Processes and Extreme Programming

Question 1

Test Driven Development

Answer 1

1. Testing first clarifies the task at hand
2. Forces you to think in concrete terms
3. Helps identify and focus corner cases
4. Testing forces simplicity
   a. Your goal is to pass the test
   b. Avoids premature optimization
5. Test acts as a useful documentation. Expose the programmer’s intent.

Question 2

Bug Fixes

Answer 2

1. Fail a unit test
2. Fail an acceptance test (user story)
3. Fail on beta testing

Question 3

Bug Fix for Unit Test

Answer 3

Fix the code to past the test

Question 4

Bug Fix for Acceptance Test (User Story)

Answer 4

Add a functional test to fix the code

Question 5

Bug Fix for Beta Testing

Answer 5

1. Add user stories, acceptance tests

2. Make one or more tests from failing scenario

Question 6

When do we need to write code to fix tests?

Answer 6

ALWAYS write code to fix tests

Question 7

Refactoring

Answer 7

1. It is done to make code easier to read, use and extend
2. Change how code does something
3. Tests should work as before
4. Refactoring is also done to remove duplicated code
5. Comprehensive suite is needed for refactoring
6. Only refactor working code
7. Plan it to allow frequent regression tests

Question 8

How should tests work during refactoring?

Answer 8

Tests should work AS BEFORE

Question 9

What does refactoring do to duplicated code?

Answer 9

Refactoring REMOVES duplicated code

Question 10

What kind of suite is needed for refactoring?

Answer 10

A COMPREHENSIVE suite is needed for refactoring

Question 11

Which kind of code can be refactored?

Answer 11

Only refactor WORKING code

Question 12

What’s Different About XP

Answer 12

1. Every XP programmer participates as an analyst, tester, programmer, architects
2. No complete upfront design and analysis
3. Infrastructure and framework is developed as you develop the app
4. Quick delivering business value

Question 13

When are infrastructure and framework developed in XP?

Answer 13

Infrastructure and framework is developed as you develop the app

Question 14

What do you use XP for?

Answer 14

1. Dynamic project done in small teams
2. Project requirements prone to change
3. Customer is available

Question 15

When do you NOT use XP?

Answer 15

1. Cost of late changes is very high

2. Customer is not available