Article provides an overview of twelve rules for writing good requirements. Each rule has its own page (linked from this one).

Useful list of possible approaches to make up iterations in agile product development.

If you want to be a bad product manager, ask customers to tell you why they love your product. If you want to be a good product manager, ask customers to tell you why they hate your product.

rather a database than an article. useful, however!

... another benefit of having such a Knowledge Base System in place is that it is a valuable source of customer feedback. ... You, as a product manager, could be monitoring the system to understand better what your customers expect from your products...

Marissa Mayer, VP of search products at Google, tells Business Week how she runs meetings

An excellent introduction to, overview of and fairly comprehensive discussion on continuous integrations. Here's an excerpt from the page: "Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage."

Im Podcast Interview von Christian Höcht beleuchtet Dr. Gernot Starke die Aufgaben und das Zusammenspiel von Projektleiter, Software-Architekt und Analytiker. Ich finde das Interview hörenswert, weil Gernot Starke einige wichtige Aspekte der Projektarbeit in klaren Worten beschreibt. Außerdem der trockene Humor von Gernot Starke und die unkonventionellen Fragen von Christian Höcht.

Great introduction, overview, and explanation of personas by Tina Calabria of Step Two. This is a long article, and also includes a great 6-page pdf version for free download. Great introduction to the topic and how and why to create personas. Also suggests some uses for personas.

If you read the article I linked to in my last post you read that Peter Morris thinks the PMBOK is too limited and that a more holistic framework of managing projects for success is required. He believes the body of knowledge must go beyond the pure PM techniques and include what is necessary for success for it to be a truly useful PMBOK. Extending the idea further for business analysts; Is the IIBA making a mistake by constraining the BABOK to what is unique about the role. Is it unique anyway - see the SWEBOK as an example of overlap. Shouldn't the IIBA work out what the key success criteria are for BAs and make that the foundation of the BABOK?