Capturing Implied Requirements


meeting turned into three hours. I questioned John extensively on what he wanted to see, how the drivers normally used the Help system, and how he would like to see the Help system work. John was absolutely delighted that the person actually producing the Help system was there listening to him explain his dissatisfactions and his needs.

Three weeks later at release, the Help system looked completely different. It now included specific common-usage walkthroughs, much different cross-referencing, reorganized tables of contents designed in conformance with user workflow, and a design-structure table of contents as a secondary view.

My boss and the CEO of the company received phone calls from John expressing his appreciation for the meeting with the "Help guy" and for the much improved system. Within six months, I received a bonus and a promotion. I cannot say for sure that those rewards were a direct result of the revised Help system, but I am sure it was a factor. The most important moral of the story, however, is that you need to capture implied requirements if you want to deliver the product that the customer wants to use.

About the author

Robert Rose-Coutré's picture Robert Rose-Coutré

Robert Rose-Coutré is a consultant with Trellist Marketing and Technology, serving as Digital Project Manager creating multilanguage country sites globally for DuPont. Robert started as a professional proofreader in 1986 and started managing teams in 1987. He has built, managed, and edited commercially successful websites; led SD QA efforts; helped launch and manage the Test/QA website in 2000, directed publishing in several industries; and once in a while writes for enjoyment. Robert earned an M.A. in English Literature and Letters, and published two books. Memberships include Senior Member - Association for Software Quality, British Museum, Mensa, and the World Intelligence Network. Contact

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!