Our agile approach to writing artifacts in Requirements That Work has been working since 2000... but what else? What is missing? What should we remove? What should we improve?
-
4 votes
help w/migrating from traditional rqmnts to problem stmts
Most feature request/issue tracking systems contain "the system must" statements. How can a new product manager leverage these systems and the prioritizing of requirement process that Pragmatic teaches (using problem statements)?
-
0 votes
-
0 votes
spend more time on traditional requirements
None of this agile stuff for me. I love IEEE. A requirement should always have the verb "shall." I recommend that you spend more time on illustrating good and bad requirements following the traditional method.
