Add a comment

 

Re: The conflict between agile and architecture (part 1)

@Mike, here's the list, apologies if the formatting is out.
  1. Developer Productivity
  2. Developer Perception
  3. Learning Curve
  4. Project Health
  5. Developer Availability
  6. Job Trends
  7. Templating
  8. Components
  9. Ajax
  10. Plugins or Add-Ons
  11. Scalability
  12. Testing Support
  13. i18n and l10n
  14. Validation
  15. Multi-language Support (Groovy / Scala)
  16. Quality of Documentation/Tutorials
  17. Books Published
  18. REST Support (client and server)
  19. Mobile / iPhone Support
  20. Degree of Risk

Re: The conflict between agile and architecture (part 1)


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).