Hacker News Reader

>product requirements definitely yes

No matter where I've worked, most product is basically no one knows what they want until its built and sitting in front of them.

View on HN

Yes that is exactly why lean agile development was invented. It should be standard practice in most development organizations by now, but yet people still want to believe that it's possible to reliably anticipate what customers want far in advance. Sometimes you can guess right but that's a risky proposition and seldom repeatable.

So what's the purpose of a product manager in an agile environment?

To keep you iterating, to ensure iterations are productive, to wrangle those disparate stakeholders into evaluating the "now" and to turn criticisms into the "next".

The SAFe definition is a good place to start. http://scaledagileframework.com/product--and-solution-manage...

Yet another definition of Agile?

Reply on news.ycombinator.com