June
2008 "Hot Button" Survey Results
In June we asked, "What are your favorite formats to document requirements for a product development team?"
Product managers use a variety of formats -- on average, each
respondent indicated that they use 3 or more formats. Highest: functional requirements list (62%); lowest: user stories (4%).
A wise product manager shared this tip: "Functional requirements listed
with unique project ID numbers helps to establish requirement
accountability for development."
People who use scenario-based requirements are likely to combine them with diagrams and use-cases.
"I really believe telling a story is more powerful than just talking
about the features," wrote one respondent. "A story will tell the 'why'
and also create a picture for those I am talking to about the
requirements."
Other product managers switch between formats and combine them as the situation dictates.
"The format I choose depends in part on the product or the project and
in part on the team -- what will make the most sense to the individuals
with whom I'll be working. Typically I'll use some sort of combo of a
couple formats."
Several respondents shared their frustration with the requirements
process. "Too much room for interpretation, but not enough resources to
provide more detail," one said. Another put it more succinctly: "Our
current process takes soooo long."
There's no doubt that successful product managers know and use a
variety of methods to communicate requirements. That's why Pivotal
Product Management's Product Management Intensive and User-Based Requirements courses give students a toolkit of formats to choose from. Do you have all the tools you need? The next Pivotal PM course, Software Product Management Intensive on Sept 24-25, will provide tools and skills you can use immediately.
Thanks to everyone who responded and commented! Contact
us to suggest a future Hot Button topic. We'd love to
hear your ideas! |