High level overview of the processes that make up the bulk of requirements management work.

By writing better requirements

Provides comparison and understanding of looking at products in terms of what the products can do, versus what the user can do with the products.

Managing prioritization with a whiteboard, and the Happy Brian List.

From the article (by Scott Ambler):

UML 2 activity diagrams are typically used for business process modeling, for modeling the logic captured by a single  use case or usage scenario, or for modeling the detailed logic of a  business rule.  Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you don’t require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of  flow charts and  data flow diagrams (DFDs) from structured development. 

Peter Merholz discusses sources of value to justify investment in design.

Project management for incremental delivery / iterative development projects by Johanna Rothman

A rolling wave plan is a continuous detailed schedule that's only a few weeks long. As you complete one week of detailed schedule, you add another week to the end of the schedule. With a four- week rolling wave schedule, I never have less than four weeks of detailed schedule, and I never have more than four weeks of detailed schedule.

Discussion of agile vs traditional requirements management

If you want to be a bad product manager, create new products based on business desires and existing assets. If you want to be a good product manager, create new products that fill customer needs that are not currently being met.

This article is an informed and wide ranging history of the profession/role of the business analyst.  Written by a developer for developers to help understand the role and how to work with them.