A few days ago I was listening to an interview to an expert in the Kanban approach applied to software engineering. I’ve been reading about Kanban since a while now and I find it quite an interesting way to solve problems in the process of software production. The interview, though, raised some kind of existentialist questions in my head: the way the expert was talking was clearly oriented towards raising the curiosity into the listeners so to push them to buy his book. The expert was really careful not to go too deep in the details of the topic giving an overall uneasy impression.
Archive for the ‘Methodologies’ category
In my opinion, the interaction between real world and computers is one of the most exciting part of software development.
To see the world with an electronic eye and be able to add information to reality creating an augmented reality is really amazing.
One of the fields we are strongly focused at Calameda labs is Augmented Reality.
With this post I’ll complete the series about the Scrum Gathering in Munich. I started the third day of the conference by attending the presentation “Growing Self Organizing Teams” held by Harvey Wheaton of Supermassive Games (http://www.supermassivegames.com). Supermassive Games produces titles for the Sony PS3 and it was founded in 2008. After less than one year the company has already got nearly 60 employees.
The first presentation of day 2 was from Patric Palm, one of the founders of Hansoft (www.hasoft.se), the Swedish company behind a product with the same name meant to manage agile and lean projects. The title of the presentation was “Making Agile matter to the bottom line by understanding group dynamics”. An impressing thing is that Patric started Palm when he was slightly older than 20 and I found also interesting his experience in the Swedish military air force.
Second presentation of the day was “Good product owner panel discussion” moderated by Simon Bennet. A very interesting point made during this discussion regarded the prioritization of stories of the same importance belonging to the same Product Backlog but referring to different projects. A simple solution to such an issue is to reverse the question and consider instead what happens if that specific feature is not delivered. Sometimes replying to this question is much easier. (more…)