Skip to content

Category: paperSyndicate content

Scrum in a Multiproject Environment

August 6, 2008 by Artem

Artem Marchenko and Philippe Kruchten

Today I presented the paper written by me and Pekka Abrahamsson. The paper tells about our experience in adopting Scrum in a multi-team multi-project environment within a large corporation and in a research intensive team. We focus on particular challenges to expect when adopting Scrum in such an environment, check the paper out if you are about to try Scrum in a multi-project situation - there is a concrete list of what to pay attention to. What I personally love most about the article is that since it has been officially approved by my daytime employer I can now freely talk in public about a part of my experience and don't need to hide behind "what a known telecommunication company could do".

Paper: Predicting Software Defect Density

June 21, 2007 by Artem

Predicting Software Defect Density: 
A Case Study on Automated Static Code Analysis

 Artem Marchenko1 and Pekka Abrahamsson2 

 1 Nokia, Hatanpäänkatu 1, FIN-33100 Tampere, Finland 
2 VTT Technical Research Centre of Finland, 
P.O.Box 1100, FIN-90571 Oulu, Finland

Presented on XP2007.

Abstract. The number of defects is an important indicator of software quality. Agile software development methods put an explicit requirement on automation and permanently low defect rates. Code analysis tools are seen as a prominent way to facilitate the defect prediction. There are only few studies addressing the feasibility of predicting a defect rate with the help of static code analysis tools in the area of embedded software. This study addresses the usefulness of two selected tools in the Symbian C++ environment. Five projects and 137 KLOC of the source code have been processed and compared to the actual defect rate. As a result a strong positive correlation with one of the tools was found. It confirms the usefulness of a static code analysis tool as a way for estimating the amount of defects left in the product.