Last week I was attending the seminar on Agile SW Development Practices in Vantaa (
Agenda in pdf).The seminar was very nice with a lot of speakers, talking about their own very practical experience in agile-related SW development. Most probably I'll highlight several seminar topics in the coming posts.
At the moment I can present my main impression: all the agile methods are about is truth and visibility. Don't lie to yourself; don't overplan, what you are not going to implement; don't pretend the project is 95% ready, if you are expecting endless bugfixes and don't hide the current situation from your customers. That's it. All the remaining details are about how to implement these principles in practice. I.e. how often and in which terms to report to customers so that they understood you and weren't overloaded with the unnecessary details, how to prevent yourself from overplanning, etc.
Bookmark/Search this post with:
On the 7th of September I was visiting the Nokia Research Center in Helsinki, where the Second Agile Finland seminar was hosted.
The popularity of the Agile methods among the software developers is growing all over the world. My first university degree was focused on the ways of constructing large software systems. So I've been always curious about different trends in the design methodologies. I could not miss a chance to discover more about this area.
The presentations were very impressive. What particularly excited me was the great amount of statistical and historical background presented by Craig Larman from Valtech. You all know, that "waterfall" is a devastating way to go. It was amazing to discover, that it was considered harmful from the very first time it was mentioned (!). But not so many readers of the article, where the waterfall was introduced and thoroughly described bothered themselves to read to the part, where it was criticized and iterative methods were offered instead.
2nd and 3rd presentations were devoted to the success stories about using Scrum methodology - lightweight iterative way to design software. It proved to be really simple, controllable and effective.
If you want to improve the software development at your company, have a look at Scrum. I will definitely try using some elements of it - its backlog and burndown chart seem to be very simple and at the same time effective and even fun tools to use.
Craig Larman starting the seminar
Bookmark/Search this post with: