Writing passionate requirements is not about writing with passion. It is about writing the requirements that cause people to be passionate about your product. Find the most important problem, for your most important customers. Understand the essence of what is important to solve that problem, for only those people. Then write passionate requirements.
Tag Archives: writing passionate requirements
Quick Post on Passion
topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F11%2F10%2Fpassion%2F”, “style”: “big”, “title”: “Quick Post on Passion” }); Why Passion is Important Thanks Kathy for Two Simple Words of Passion… I distinctly remember some eye-rolls when we posted Writing Passionate Requirements as part of the Big Ten Rules to Writing Good Requirements series. When we are excited about our product, and believe [...]
Writing Passionate Requirements
One of the ten big rules of writing a good MRD is writing passionate requirements. What in the world is a passionate requirement [they were all wondering]? When you believe in the product, are committed to the work, and aren’t bored, you can write passionately. The goal of a requirement is to create sustained understanding. A dry document can create understanding, but an engaging document will sustain it.
Posted in Product Management, Requirements, Software requirements specification, Writing
Tagged business requirements documentation, good requirements, managing data, passionate requirements, product requirements, requirements documentation, software requirements, writing business requirements, writing passionate requirements, writing requirements
9 Comments
Latest Articles
Comments on all Articles
