Sometimes a blog post talks about a tool and it sounds like an ad. Othertimes, it provides good information and then it mentions a tool. Such was the case when I read this post from Stephen Walther. The explanation of time-tracking (second paragraph) really hits home when trying to promote why it should be used. I've been working with Microsoft's TFS for the past few years and one of the challenges has always been getting people to track time. If they don't see a real benefit to it, it's often perceived as a negative performance measurement tool. They have to get over that mindset. As the post says " the Product Owner needs to know when the work on a story has gone over the original time estimated for the story. The Product Owner is concerned with Return On Investment... a legitimate reason to halt work on the story and reconsider the story’s business value." "if your team is spending 75% of their time doing testing then you might need t
Solutions for Today; Ready for Tomorrow. Andrew MacNeill's blog about development, technology, Visual FoxPro, databases, community and occasionally, some off-topic discussions.