About
MemoRanda, Keith Ray's notes to be remembered (Memorandum - from Latin, memorare, to bring to remembrance) on software development and other topics.
Send comments to:
keithray@mac.com
Powered by:
| Links |
| xpminifaq |
| Resume |
| AYE Conference |
| Lucien W. Dupont |
| Elisabeth Hendrickson |
| Johanna Rothman's Managing Product Development |
| Brian Marick's Exploration Through Example |
| Esther Derby's Software (Management) Improvement |
| Laurent Bossavit's Incipient(thoughts) |
| Dale Emery's Conversations with Dale |
| Martin Fowler's Bliki |
| James A. Robertson's Smalltalk With Rants |
| Creating Passionate Users |
Archives
Subscribe
RSS MemoRanda XML
2006.Mar.17 Fri
Often it has been said that "agile doesn't scale". This is a good, short, article by Dean Leffingwell on seven agile practices that do scale. They are:
- Iteration. "create tested working code in a small time box"
- Unified Define/Build/Test teams. "eliminating the functional barriers [...] there is no limit to the number of such teams that can be formed!"
- Smaller and more frequent releases. (see Creating Passionate Users on Ultra-fast release cycles/myspace)
- Two-level planning. the long and short view
- Concurrent testing. Unit testing, acceptance testing, [etc. ...] occur inside each iteration [....] that persists in the future as regression tests [...] in future iterations
- Continuous integration. "I witnessed one team of approximately 300 people building a large-scale systems infrastructure application reduce the integrate-build-regression test cycle time from a month to less than a day."
- Regular reflection and adaptation. "empowered, agile teams naturally address and eliminate the roadblocks [....] Since this process is not prescriptive, it can give some discomfort to project management [...] who tend towards documented, prescriptive and mandated processes.