Will Read's dashboard

The way I've been using it at Pivotal, is the developers finish the story, then it enters the Accept/Reject state. In our case, the product owner checks out the feature and says if it meets her standards or not. I fyou had separate QA, I'd put them in at this point to accept or reject the story/bug. This works well when there are only a handful of stories finished each day (team of 4) and the QA/PO are only one or two people. What's your situation like where you're using Tracker? – Will Read, on March 13, 2009 06:04