I have just been on summer vacation on Naxos in Greece, and i brought along uncle Bob´s (Robert C. Martin) book “Clean Code” to read on the beach. A couple weeks earlier i had been to NDC 2009 listening to him talk about what makes a developer or programmer a professional. This, the book  and all the other great sessions on code quality and agile development  got me thinking – what statement can i make as a programmer, developer and software engineer to show the world “I am a professional!” and what would be simple enough to not be constraining?

So, between the great door of Naxos and the mountain of Zeus i wrote down 6 simple guidelines in what i call “The agile developer´s manifesto“. These guidelines will help me improve myself as a developer, software engineer and solution architect.

These are guidelines, not rules that yield punishment if “broken”. I´ll try to follow them in my daily routine and also try to help others see the benefit of them. Continue Reading

On friday a colleague of mine wrote a nice article about how to writing agile use cases after we had a discussion about how we should write effective use cases that also maintain the need for documentation.

 We are both excited about working with agile methods and we will be writing some articles in our respective blogs about our effort to “agilize” our development projects.

This image is called  ”Software Engineering Explained”  It illustrates pretty good the different expectations stakeholders in a software project.