Some of my scrum team members came up with nice anti-agile manifesto that I at least found really hilarious. Especially as it highlights some of the things that are present in process-oriented organizations.

Manifesto for Fragile Software Development

We are uncovering worse ways of developing
software by writing about it and telling others about it.
Through this work we have come to value:

Messed-up processes and enterprise tools over people
Unfrozen and unfinished specs over working software
Hopelessness over happiness
Following an undetermined plan over responding to change

That is, while there is no value in the items on
the right, we only value the items on the left.



TODO: we need some signatures

Excellent takeaways from Agile Architecture training

Agile Architecture course given by James O. Coplien was really interesting. Here's summary about my learning experience:

• Model-View-Controller pattern should be described as Model-View-Controller-User as the user is vital for communicating the pattern to others.
• TDD can ruin your architecture, Coplien has written an thought provoking article about that.
• Architecture is about "What the system is" and "What the system does". Extreme agilists usually concentrate only on the latter.
• Object-Oriented Programming is rather about Roles than Classes. Jim has written nice blog about that as well.
  

I have been following the TDD dicussion taking place on various blogs and now it is getting really interesting. I have actually started doing an experience report for XP2008 about my personal findings in my current Scrum team with help of my good friend Ari Tanninen.