Writing Good Requirements Course Session 0: Introduction

Poorly-written requirements are the norm in systems and software engineering; a problem that has been recognized for more than 30 years, as a major cause of project failures (cost and schedule overruns as well as cancelled projects) and in spite of numerous courses, Standards, textbooks and INCOSE symposium papers on producing good requirements, the situation hasn’t changed. An all the commercial requirements management tools I’ve seen still can’t tell you if a requirement is poorly-written.
I pondered the problem of the perennial problem of poor requirements using a little system thinking and beyond and came up with a reason and a way to overcome the problem. It requires an innovative new kind of course both in content and way of teaching.
On completion of this course, you should be able to:
1. Write good requirements more than 90% of the time
2. Write well-requirements more than 96% of the time
3. Elicit good requirements from stakeholders
4. Better understand stakeholder needs
5. Convert more than 90% of poorly-written requirements to well-written requirements
6. Understand the importance of stakeholders
7. Identify and manage 85% of all pertinent stakeholders
8. Understand why writing good requirements has been so difficult in the past
Can any other course promise you these outcomes?
Notice some new terminology in the list of outcomes? They are there because I found out that existing books and courses do not teach you what you need to know, and even worse, some of what you are taught is misleading if not wrong.
Check out the course at therightrequir...