tag:blogger.com,1999:blog-6488575.post2010421134318776250..comments2008-10-08T08:25:07.436-05:00Jeff L.http://www.blogger.com/profile/10499693020049210645noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6488575.post-18147869851224492082008-10-08T08:25:00.000-05:002008-10-08T08:25:00.000-05:00I believe it is okay to make task tracking a requirement for tool selection since it is useful. I also understand where you are coming from that if the whole culture "requires" it, there might be a problem.<BR/><BR/>We use VersionOne because it handles both. We use task tracking heavily. As we work towards appropriately sized stories, we may need this less... but for now it helps us compensate for some other issues.Kevin E. Schlabachhttp://www.blogger.com/profile/06707944667176547115noreply@blogger.comtag:blogger.com,1999:blog-6488575.post-41629054802292081902008-10-08T08:07:00.000-05:002008-10-08T08:07:00.000-05:00Note that I didn't say "task tracking was evil." It's one way of working, and if it works for you, go for it. However, the better way is to structure things so task tracking becomes irrelevant. If you feel like you have to track tasks, your stories are probably taking too long to complete within the iteration.<BR/><BR/>Spread-out tasks are also a violation of lean principles.Jeff L.http://www.blogger.com/profile/10499693020049210645noreply@blogger.comtag:blogger.com,1999:blog-6488575.post-16433551990325646642008-10-08T04:02:00.000-05:002008-10-08T04:02:00.000-05:00I don't agree that task tracking is an evil. For example, we at TargetProcess use tasks as Definition of Done. We have tasks for each user story like Implementation, Create Acceptance Tests, Testing, Code Review, etc. <BR/><BR/>Definitely tool should make it possible to disable task tracking, but it brings value as well.Michael Dubakovhttp://www.blogger.com/profile/07679773973314266590noreply@blogger.comtag:blogger.com,1999:blog-6488575.post-71672274921976068492008-10-07T20:51:00.000-05:002008-10-07T20:51:00.000-05:00definitely agree. <BR/><BR/>Our VersionOne tool met both requirements for us. We could start with task tracking if absolutely necessary and turn off at any point in the future with the click of a single check box. We actually started with task tracking turned off and never looked back.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6488575.post-45561649786952305892008-10-07T19:07:00.000-05:002008-10-07T19:07:00.000-05:00couldn't agree with you more. We use scrumworks and you assign a point person to a story/pbi. <BR/><BR/>Then you add or delete tasks as needed.<BR/><BR/>we went to a csm class with danube too. the trainer said "are you in the business of keeping people busy or producing product?" I think this is the point of your blog postings.Anonymousnoreply@blogger.com