[wpietri]

There's a conflict in what you say. If people don't read documents and will ask when they need something, why invest in creating heavy tickets filled with the text they don't want?

My team (and many XP teams) gets by just fine organizing things with cards that have a modest number of words on them (5-10, normally). When we need something, we ask. It works fine for us. We're a distributed team that has never met in person. But it also works fine for in-person teams: https://williampietri.com/writing/2015/the-big-board/

[tibiahurried]

I called it ticket, you can call it card. I did not say it to be heavy. But should also contain enough info to get started or at least point to the right person.

[wpietri]

What you are describing is definitely heavier than what I'm describing.

And I disagree it should contain those things. In the XP tradition story cards (which are conceptually different than tickets, but I'm fine with either term) are tokens for conversations. The more documentation you add, the more it drives people away from conversation. As you say, when people need something, they'll ask. And I think that's a strength, not a weakness.