From the Intranet Journal: a handy tip list for how/who to best generate and manage a requirements specification for a project.
Perhaps the most important piece of any application development project is requirements gathering. After all, if you're not clear on where you're going, how will you know when you get there? So why do most intranet teams spend so little time focusing on developing the skills necessary to do this piece well?