When it comes to developing new features for a software product, every Product Manager is faced with the following dilemma: more new features are needed than there are resources to add them to the product. You can't possibly get all the features in that you want to put in. We are told to prioritize, which most ...

This article is a reprint of an oldie but goodie about Requirements. It will help you measure the expected return from Requirements so that you can reconcile competing needs and prioritize new capabilities for your product.

As your company gears up to start the next software release, a Product Manager reaches the point where carefully crafted requirements are ready to submit to the Engineering team. The Product Manager holds a long meeting with Engineering to review each and every requirement. Holding this meeting feels a lot like watching the beloved little lambs ...

With product requirements, one temptation a Product Manager has to fight is the desire to jump into the details. You already know what you want, lord knows you've heard what people want often enough, someone's got to actually put them on paper, and that someone is you, so you might as well get started. But there's ...

One thing I associate with product management is the need to keep marching through the many efforts required to design and build software, then launch it in the market -- no matter how difficult the times. And so we have this week's issue, as scheduled. Respectfully, Jacques Murphy, Feeling sad for the people of Iraq, Grieving for the ...

Today's issue is the first of two topics covering product requirements. Requirements, as the fuel that powers your company's software development engine, are an essential part of product management. Without this fuel, development doesn't happen. Too little or too much, too sparse or too rich -- all lead to a poorly running engine. It is essential ...

Requirements are the challenge every Product Manager faces. Each software company manages to deal with the requirements headache more or less successfully, and headache - or heartache - is exactly how many people look upon the whole process. Yet viewing requirements as a necessary evil can get you into trouble. After all, requirements are how your ...