This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Well, we also use story and epic cards in our Agile projects. For the requirements elicitiation we use questionnaires and also conduct workshops with a variety of games and customer/user profiling - who likes what, values what, etc. For progress analysis we use Kanban style WIP charts. These are very recently used though. Earlier it was good old doc. templates defined by the Quality gurus.
Java Pal - Your friend in technology and innovation...India.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: most creative/interesting requirements artifacts