How to guarantee product failure
How to guarantee product failure from
Roger Cauvin lists five fatal mistakes product managers make when writing requirements. It's a fast read, and well worth the time.
The article hit home with me: I'm reviewing our development process right now. Although we do a good job of writing requirements, many of the roadblocks to shipping on time stem from the fact that we then immediately write a specification and the rest of our process is driven by the specification instead of the functional and non-functional requirements.
Labels: agile