Some interesting thoughts borrowed from my notes of the “How to Become an Agile Architect” talk presented yesterday by Uwe Friedrichsen from Codecentric at the Jazoon 2011 conference in Zurich.
* Architecture is a set of skills and not a role: if you don’t have these skills available for your project, you might get quickly in trouble.
* Becoming an architect is a journey: you should leave your comfort zone and programming expertise area to explore and learn about the other software development domains like requirements, operations or testing.
* An architect focuses …

Dan Leffingwell proposes eight principles for the development and maintenance of enterprise-class architectures in the lean and agile enterprise:
1. The team that code the system also design the system
2. Build the simplest architecture that can possibly work
3. When in doubt, code it or model it out
4. They build it, they test it
5. The bigger the system, the longer the runway
6. System architecture is a role collaboration
7. There is no monopoly on innovation
8. Implement architectural flow
Source: “Agile Software Requirements”, Dean Leffingwell, Addison-Wesley, 489 pages, IBSN 978-0-321-63584-6
Get more details on this book …

Blog: Avast Combining the ScrumMaster and Product Owner, Matey!
Blog: What’s Wrong with “HTML5″
Blog: Maintainable Systems 2
Blog: How To Adopt Getting Results the Agile Way
Humour: You Know That You Are on a Software Project
Article: Evolutionary architecture and emergent design: Building DSLs in JRuby
Article: Static Analysis Is Not Just for Finding Bugs
Tools: JUnitum – JUnit extension for system test
Tools: Dancer – Perl framework
Video: What the #@%# is cloud computing?
Video: Adding Sanity to Your Agility
Video: User Scenario Testing for Android
Find more interesting links on the software development links directory, the software …

This book presents the influence of architecture in the software development process. The interesting aspect of this book is that is it a thoroughly presentation of the architecture role in the software development activities, not only at initial analytic stage but also at the subsequent tasks like software testing or configuration management. The book is very well structured and is certainly an excellent text book for students or for developers that are interested in getting an extensive presentation of software architecture. What I missed in the book is the presence …

Methods & Tools is a free e-newsletter for software developers, testers and project managers. Spring 2009 issue’s content:
* How to Build Articulate Class Models and get Real Benefits from UML
* When Good Architecture Goes Bad
* Finding a Partner to Trust: The Agile RFP
* Database Locking: What it is, Why it Matters and What to do About it
* Code Generation for Dummies
80 pages of software development knowledge that you can download from
http://www.methodsandtools.com/mt/download.php?spring09