Friday, January 31, 2014

Moving on to

The blog moves to and will be continued there. Please follow us there!

Tuesday, January 7, 2014

Co-changes in source code - change periods are usually 20-40 hours....

The article describes the co-changes in code for a number of open source projects (e.g. ArgoUML).

What is interesting is that they have found that in open source projects the change periods are usually 1/2 - 1 week in duration. This is an interesting finding when mining related changes from software repositories.

Looking forward to industrial evaluation of the tool.


Saturday, November 9, 2013

Visualization of Defect Inflow and Resolution Cycles: Before, During and After (review)...

Visualization of Defect Inflow and Resolution Cycles: Before, During and After Transfer$file/BTH_Visualization_of_Defect_Inflow_and_Resolution_Cycles.pdf

When making decision about outsourcing there is always some degree of uncertainty what the effects will be. Will the quality be the same? Will the cost be lower? ....

In this paper the authors looked at the efficiency of defect management/resolution processes and visualized them. The results show that during and immediately after the transfer the defect inflow is higher, bottlenecks are more visible, and defect resolution cycles are longer.

The authors identify a set of factors which can explain some of the trends in the defect inflow/removal processes - e.g. competence, unstable maintenance team, etc.

Very interesting article with a solid empirical focus.

Monday, September 16, 2013

What's important for continuous integration...

What's important for continuous integration...
review of "Modeling Continuous Integration Practice Differences in Industry Software Development",

I've got this article on ScienceDirect alerts and was a bit skeptical to the method - literature review - but when I read the paper it turned out to be great stuff.

The authors look at what is important in continuous integration - see top 3:
- build duration
- build frequency
- build triggering

and they also looked at  the meaning of common phrases - e.g. what is a failure or success of continuous integration. Turns out not that simple...

Generally very interesting article with a lot of insights.

Friday, August 23, 2013

A teamwork model for understanding an agile team... review

A teamwork model for understanding an agile team...

I came across an article which analyzed a number of situations in a single Agile/Scrum team. I was skeptical in the beginning, but after I got to browse it my attention was drawn to the quotes from the team.

In the end I've read the whole paper and liked the retrospective of the team. For example how they evolved to work together in the first project, shared risks and opportunities. and a few more.

really recommend!

Sunday, June 30, 2013

Sensing high performance software teams

Interesting article on measuring team performance

The article shows a design of a survey that would help to continuously monitor software teams and their performance. Sounds a bit like the old fashioned PSP or TSP, but might actually work. Looking forward to more case studies with this method. 

The article contains two case studies, but more wild be welcomed and their more thorough analysis together with the proper description of the center would be great. 

Clone detection at Microsoft

Detecting clones at Microsoft seems to be a planned and well executed activity...

I was looking at the clone detection research recently and found a new development from Microsoft. It seems that the company puts a lot of effort to reduce the waste in their source code and work with refactoring. They report an impressive number of downloads if the tool and show why they use it. 

Unfortunately no real results of how much improvement was introduced thanks to the tool. Perhaps that will come later.