Article by Suzanne Robertson about how to approach writing requirements when you are under constraints that prevent you from completing them.  Good article, very stimulating discussion in the comments.

Kathy Sierra discusses how to balance interface design between letting users do what they want, and making them do what you know they want - in the way you want them to.

…Is another man’s treasure. There are many different ways to document requirements when developing software. And there is a proliferation of requirements documents - MRD, PRD, SRS, FRS and design documents. Everyone has a perspective on what each document represents, and each person on the team has a unique perspective on what questions the document answers.

Product roadmaps can be powerful assets to leading a technology business – buy only if they are created and managed in the context of appropriate policies. In fact, the product roadmapping process a company uses can be as important to its business as the roadmap itself. In the Product Strategy Network’s roundtable meetings on product roadmapping, field-tested practices and policies are presented in detail by PSN Members. Here are a few of the highlights:

The article is written in the context of implementing knowledge management strategies and it talks about a quality approach to project execution and requirements management.

This includes the importance of reconciling the details with the strategic direction when documentaing and managing corporate knowledge.

This is a useful article for anyone getting involved in the development of Knowledge Management systems or Business Process systems and Repositories.

Peter Morville on information architecture and the user-experience honeycomb

I've been practicing information architecture since 1994, and from Gopher to Google have seen dramatic changes in the landscape of organization, search and retrieval.

Through these ten tempestuous years, I've found the infamous three circle diagram to be a great tool for explaining how and why we must strike a unique balance on each project between business goals and context, user needs and behavior, and the available mix of content.

 

Deep analysis of the tasks that must happen in an iteration - development, analysis, testing, etc.  Focus on the problems with staggering them too much, and suggestions on how to properly organize the team around those tasks.

When you define a product roadmap, you also define the release dates for your product. Change happens. Your market changes, your customers change, your requirements change. Unpredictable events happen. Your competitors release a new killer feature, your developers have an epiphany (or run into a roadblock). Should you change your release schedule?

Object oriented approach to estimating the effort for a software project.

Article compares different approaches to testing the workflow of an application - specifically a web application.  Detailed analysis of the maintenance & skill level tradeoffs for each approach.  Also touches on Selenium and Watir approaches.