Earlier quoted context omitted.
Fair enough. Reading this: http://en.wikipedia.org/wiki/User_story I'm trying to get my head around "buying into XP". At what point do you describe the thing that you're about to build? I don't believe huge requirements gathering phases, requirement documents, or any heavy weight processes are required. However, I don't know how an engineer can write code without at least being able to fully understand the problem, a…
The piece thats missing for me with tracker is the conversation. As atomical points out, there are times where you want the story to have some vaguer requirements to allow it to breathe and evolve on its own. During times like these, it grows through the conversation and chair-spin between developers, product owners, etc. On tracker, the comments system is abysmal, so you either end up with a long unreadable conversa…
I like this balance and aim for brief story titles with descriptions which include the "As a , I want so that " style requirements, implementation concerns, and other acceptance criteria. I could certainly see a place for a more opinionated story writing tool though. Especially for team who struggle to produce actionable stories.
I also see a Tracker story as a placeholder for a conversation which needs to happen. Not as a good tool for mediating that conversation in the story comments and attachments.