Thursday, March 11, 2010

Help me : Bugs per 1000 line of code .. Agile dev aproach vs Traditional development aproach ??

I have come across some papers for same projects done based on traditional approach and Agile approach, which proves that Agile approaches have delivered significant better results. Some are from Starlabs SCRUM papers.

Im in the process of customising an Agile framework and curious about following.

Have you come across in any comparisons that the bugs per lines of code based on traditional software development vs agile development especially when test focused and test driven approaches are used. ?
Yeah I understand the complexity of the comparison based on iterative deliveries, but what Im looking at is the accumulated picture over the iterative deliveries throughout the project compared to the test results of the same project which is done with traditional approaches.
What I need to know is whether there is a significant difference in test results as we see many points that it should be..
Appreciate your help on this ..!

PS. thank you so much Buddhima sending me this

Its great. Thats About google techtalks - Agile testing.. I enjoy that so much..!


Peter said...

I have no idea about agile as much as you do, I can tell you from testers perspective that there is an average of 10 – 20 bugs per 1000 lines of code in Microsoft applications. Its an industry standard.
There is a technique called “Clean room development” which claimed to say the developers can reduce the number of bugs per 1000 lines of code to 3 -5 if you use it right.
If you find anything related to this topic, I wish you will share them here. Wish you luck with the research and framework!

koolb on 5:02 AM said...

Don't forget that TDD can be used with any dev approach. I think you have to compare TDD project against non-TDD project. Because testing is more related to engineering.

Thushara Wijewardena, PMP, CSP on 8:01 PM said...

Thanks Peter - I want to read about Cleam room development you mentioned. And sure I will share some itdeas when I have some.

Buddhima - I agree TDD can be used in any method. But TDD was 1st coupled with XP. and then Agilists made it a point to use it due to iterative deliveries. thats why I mentioned TDD in Agile aproaches.
Then Test focused development such as preparing test case with the user story itself and having test skills within the team, all get to elaborate requirement in to very detail level, getting team estimates etc. in Agile development - What I want to know is whether there is a significant difference in test results..

Project Management Software on 2:55 AM said...

I started the discussions with few prioritized issues we face in offshore projects when using agile, the very first was the challenges when it comes to project initiation with an onshore customer who is not in to agile.

Thushara Wijewardena, PMP, CSP on 4:39 AM said...

Yeah ..! I understand your challenge.. its always challenging when either side is not in to Agile.. Because I don't believe that its an overnight transition. !

Max_Headroom on 10:05 PM said...

Thushara, if you want to learn about "Cleanroom" technology, I think Capers Jones and the IBM Software Journal are good sources. Cleanroom actually came from IBM-Boca Raton (OS/2 development lab) and it was used by Watts Humphreys' of CMU-SEI for CMMi.


PROJECTIZED. Copyright 2008 All Rights Reserved Revolution Two Church theme by Brian Gardner Converted into Blogger Template by Bloganol dot com