Over at the Product Management View, Joel St-Denis recently wrote : My personal opinion is that the Waterfall approach to development is better aligned with the responsibilities of solid product management, as it provides more reasonable periods of time to properly research your market and better define your requirements. While I agree that dedicating sufficient time to market research and requirements definition is important, I do not agree with Joel that a waterfall approach to product development is advantageous. In fact, I believe that a waterfall approach hinders valuable market research and requirements definition. Waterfall approaches assume a phase-by-phase sequence to product development. Your product manager researches the market and defines the requirements, and the development team analyzes the requirements and domain, designs the product, implements it, and tests it. By definition, once the team finishes a phase, it moves on to the next phase and does not revisit previou
"Smart product decisions"