Communication / Product Management / Requirements / Software requirements specification / Writing

Requirements Documents – One Man’s Trash

Posted on:

…Is another man’s treasure. There are many different ways to document requirements when developing software. And there is a proliferation of requirements documents – MRD, PRD, SRS, FRS and design documents. Everyone has a perspective on what each document represents, and each person on the team has a unique perspective on what questions the document answers.

Communication / Requirements

Everything I Needed To Know I Forgot in Kindergarden

Posted on:

“WHY?” is the central theme, the underlying cause, and the most important element to developing a successful product. And it plays an important role in documenting requirements. Without knowing why a product is valuable or why people will use it, or why it needs to be done in 3 months instead of 6, you aren’t likely to make the right decisions about what to include, when to include it, or how to market it.

Communication / Presentation / Requirements / Requirements gathering

Active Listening and Cultural Cues – When No Means Yes

Posted on:

Without good communication skills, you won’t understand what the stakeholders want. And you won’t structure and describe the requirements in a way that the developers will implement what you intend.

For a given project, there are three sets of requirements – the requirements you are given, the requirements you document, and the requirements that are interpreted by the delivery team.