About
Exploring Solution Spaces, Keith Ray's blog on Software development and other topics.
Send comments to:
keithray@mac.com
| For Agile Training, eLearning, or Coaching contact: |
| Industrial Logic, Inc. |
| 866-540-8336 (toll free) |
| 510-540-8336 (Berkeley, California) |
| Links |
| xpminifaq |
| Résumé |
| “Adopting XP” Article 2002 (pdf) |
| “ Refactoring” Article 2006 |
| AYE Conference |
| Lucien W. Dupont |
| Elisabeth Hendrickson |
| Johanna Rothman's Managing Product Development |
| Brian Marick's Exploration Through Example |
| Esther Derby's Insights You Can Use |
| Laurent Bossavit's Incipient(thoughts) |
| Dale Emery's Conversations with Dale |
| Martin Fowler's Bliki |
| Creating Passionate Users |
Archives
Subscribe
RSS Exploring Solution Spaces XML
2004.May.05 Wed
A Paper[pdf] by Amr Elssamadis of ThoughtWorks. Quotes:
...35 developers, 15 business analysts, and about 10 QA...
Unit tests and integrated builds - are ABSOLUTELY MANDATORY... As the application gets larger and larger it becomes almost impossible to add new code or refactor existing code without going through tests.
We originally had longer iterations - one-month ... had problems estimating [large stories] ... We are now doing two-week iterations ... estimations are closer to target....
Have an iteration planing meeting at the beginning of each iteration where the customer and developers split up in groups all day to discuss the latest story cards and estimate them. At the end of the day regroup and present your estimations and findings... This will keep the whole team in-the-know ... without burderning everyone with an extremely tedious and long meeting.
Frequent design meeting (lunch...) are very helpful....
It will always be tempting not to refactor and to just patch a solution, but if it is patched too much the team will be forced to make major refactorings later on.
...a group of individuals are needed to be the customer....