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.

…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.

An article on testing strategy for non-functional requirements that stimulated a fantastic discussion about functional vs. non-functional requirements. Great points are made both to eliminate and to highlight the distinctions. The strategy for developing a test plan is good, and worth reading alone, but this article is fun in that it went in a completely different direction with a very well informed debate.

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.

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.