Wiki for Development
I'm always excited to start a new development effort. There's always so much to learn about your new users, their domain, and the problems they're experiencing. At this stage, ideas to help solve these user problems are plentiful and the possibilities seem endless. The hard part is, what to do with all the ideas you can't fit into your first release? Often these get left on a white board, buried in an email, or forgotten in a Word document. My team had this exact problem a while back. We started using a wiki to track feature ideas. It was easy to update and enhance this list, eventually slotting these features into planned releases. The wiki became "The Place" to document design decisions, track progress, and even hold our user documentation (which we exported later and included with the release). It became a very valuable development resource. A Wiki is a great tool for teams to keep all your ideas and development artifacts in a central, easily a...