Requirements define the future. They express conditions that their author expects the future to fulfill. Unfortunately, the word "requirement" has become a four-letter-word in many organizations, particularly when the requirements define a future Information Technology (IT) application. The reason? Nearly every independently executed, root-cause analysis of IT project problems and failures in the past half-century have identified "misunderstood or incomplete requirements" as the primary cause. This has made writing requirements the bane of many projects. The real problem is the subtle differences between "understanding" someone else’s requirement and "sharing a common understanding" with the author.
"Writing Requirements in Plain English" gives you a set of 4 simple rules that will make your requirement statements more easily understood by all target audiences. The focus is to increase the " common understanding" between the author of a requirement and the solution providers (e.g., in-house or outsourced IT designers, developers, analysts, and vendors).
The rules we present in this course will reduce the failure rate of projects suffering from poor requirements. Regardless of your job title or role, if you are tasked with communicating your future needs to others, this course will help. It is interactive (includes exercises with instant feedback), instructionally designed (based on modern adult learning theory), and "intellimated™" (uses animated visuals with an accompanying audio track) to hold your interest and increase retention.
View Course Outline with Lesson Previews
Anyone involved in capturing, writing, analyzing, or understanding requirements for Information Technology solutions, including (but not limited to):
- Subject Matter Experts (SME)
- Agile Product Owners
- Business Process Managers
- Business Process Users
- Business Analysts
- and anyone wearing the BA hat
Upon completion of this course, you can:
- Write requirements that focus on the business need
- Test the relevance of each requirement to ensure that it is in scope for your project
- Create and maintain a question file to reduce the impact of incorrect assumptions
- Minimize the risk of scope creep caused by missed requirements
- Confirm that each audience shares a common understanding of the requirements
- Use our Peer Perception technique to find ambiguous words and phrases that can lead to misunderstandings
- Reduce the ambiguity of a statement by adding context and using standard terms and phrases