From the article:
What is the Point of the Project?
I'm just guessing, but I think the point of most software development projects is software that works, and that has the most features possible per dollar of investment. I call that notion Running Tested [Features], and in fact it can be measured, to a degree.
Imagine the following definition of RTF:
- The desired software is broken down into named features (requirements, stories) which are part of what it means to deliver the desired system.
- For each named feature, there are one or more automated acceptance tests which, when they work, will show that the feature in question is implemented.
- The RTF metric shows, at every moment in the project, how many features are passing all their acceptance tests.
4 comments:
Just found the blog. :)
I would greatly appreciate if it was possible to switch to a more read-friendly font.
/Fellow CSM
problem is you have to create the tests up front to the development, now you have a backwards phased project. (waterfall with the test automation in front)
In reply to Anonymous, I disagree that creating tests upfront is a problem.
Each ticket should have some acceptance tests defined prior to development - a) how else do you know when the ticket is completed? b) How can the tester understand the goals of the ticket?
Just some thoughts..
I liked the article. Checkout http://scrumdev.blogspot.com/ for additional information on SCRUM
Post a Comment