Thursday Feb 26, 2009

Software projects grow over time. They get bigger, more stuff is added, patches added and bugs fixed. New features added, and removed and code removed. But who keeps track of the changes and ensures that your source code repository stays clean? That they are no old undeleted files, no missing unittest, that all dependecies are correct? In short: that they are no broken windows (link) and a nice clean environment a engineer can checkout, compile and run within minutes? 

I'm using the ReInCheck tool for that. Currently it is customized to support a multi module maven project which consists of OSGi bundles. But it should be easy to adopt it to your needs.

I have always been a fan of improving software development processes. The last couple of days I had a deeper look into Scrum. I worked with Agile development methods for some time now, and I like to point you to this scrum link from Softhouse: http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf. Very rough, but gives a nice overview.

Here is a slideshare version:

Learn Scrum Engineering in 5 minutes

View more presentations from guest035e0d. (tags: scrum engineering)

This blog copyright 2009 by Thijs Metsch