...
SGB: We need to define roles we believe to be important and how each aspect of an Agile or XP process impacts each player. (see See bullets on Feedback below.)
"Agree as a team - including the customer - on an acceptable level of quality. Agree to consider that time and resources are fixed. The only remaining question is that of scope. What will be delivered? When will it be delivered? The customer will set priorities for individual features. You will work on them in turn. The software will always be kept in a releasable state." XPPG, p6
...
Perfect is the enemy of done. Aim for a solution that is good enough.
| Anchor | ||||
|---|---|---|---|---|
|
Feedback is fundamental to every XP practice. (XPPG, pp. 8-10)
- "Exposing the tradeoffs of changes to any of the 4 variables above leads to fewer surprises and smoother development."
- "The sooner you can get feedback, the more time you have to react to it."
- "It is only through actual work that you can understand your real obstacles."
- "For the customer, seeing a feature implemented leads to a better understanding of the software and how it works."
- "Feedback from testing helps you to be confident about making changes. Whether adding a new feature or improving the design of the code, knowing that a change in the last 10 minutes (or even 10 seconds) has broken a test reduces the amount of debugging detective work to manageable chunks."
- "Feedback from frequent releases gives the customer confidence in the value of the project."
- "The only way to recover from a mistake is to admit to it and to fix it."
...