| | Book ShopNew | Testing Tools | Testing Books | Testing Directory | Testing JobsNew | Testing CertificationsNew | |
testingsense.com
A forum to discuss Software Testing
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Software Testing Jobs
Only Software Testing Jobs
And Nothing Else
What Should the RTF Curve Look Like?

 
Post new topic   Reply to topic    testingsense.com Forum Index -> metrics
View previous topic :: View next topic  
Author Message
deepshikha



Joined: 31 Aug 2007
Posts: 22

PostPosted: Sat Sep 15, 2007 12:41 pm    Post subject: What Should the RTF Curve Look Like? Reply with quote

What Should the RTF Curve Look Like?
Back to top
View user's profile Send private message
stone



Joined: 29 Aug 2007
Posts: 16

PostPosted: Sat Sep 15, 2007 12:47 pm    Post subject: RTF Curve Look Like.. Reply with quote

With any metric,we need to be clear about what the curve should look like. Is the metric defects? We want them to go down. Is it lines of code? Then, presumably, we want them to go up. Number of tests? Up.

RTF should increase essentially linearly from day one through to the end of the project. To accomplish that, the team will have to learn to become agile. From day one, until the project is finished, we want to see smooth, consistent growth in the number of Running, Tested Features.

*Running means that the features are shipped in a single integrated product.
*Tested means that the features are continuously passing tests provided by the requirements givers -- the customers in XP parlance.
*Features? We mean real end-user features, pieces of the customer-given requirements, not techno-features like "Install the Database" or "Get Web Server Running".

Running Tested Features should start showing up in the first week or two of the project, and should be produced in a steady stream from that day forward. Wide swings in the number of features produced (typically downward) are reason to look further into the project to see what is wrong.

But our purpose here is to provide a metric which, if the team can produce to the graph, will induce them to become agile. A team producing Running Tested Features in a straight line from day zero to day N will have to become agile to do it. They can't do big design up front -- if they do, they'll ship no features. They can't skip acceptance testing -- if they do, their Features aren't Tested. They can't skip refactoring -- if they do, their curve will drop. And so on.

It might be possible to game RTF. My guess, however, is that it would be easier just to become agile. And the thing is, it would take a truly evil team to respond to demands for features with lies. And I don't think there are many evil teams out there.

The reason that XP and Scrum and Crystal Clear work is that they demand the regular delivery of real software. That's what RTF is about.

By Ron Jeffries
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    testingsense.com Forum Index -> metrics All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
| | Book ShopNew | Testing Tools | Testing Books | Testing Directory | Testing JobsNew | Testing CertificationsNew | |