RE02 Tutorials: T01 | T03 | T04 | T05 | T06 | T07 | T08 | T09 | T10 |
T01: "Just Enough Requirements Management (JERM)" (Alan Davis) |
Just Enough Requirements Management (JERM)Monday, September 9th from 900 - 1730 Abstract:Target Audience: Requirements practitioners, requirements analysts, requirements writers, requirements managers, systems analysts, project managers, marketing personnel Tutorial Outcome: Requirements engineers are bombarded repeatedly by larger & larger, more & more complex notations, methods, techniques, tools, and methodologies (collectively called "requirements management"). Proponents of each claim that their approach is somehow "better" than the previous generation's offerings. And yet, our ability to define systems does not appear to improve, at least not by using the only valid success metric: the degree to which the completed system satisfies its intended customers. This tutorial presents an unburdening, return-to-basics approach that calls for less, not more requirements management. The purpose of requirements management is to help identify the actual needs of stakeholders, decide which subset of those needs should be addressed realistically given available resources, and to document and manage the external characteristics (usually called "requirements") of a desired system. This tutorial will expose participants to how to do requirements management simply so that system development is accelerated, not brought to its knees, and more importantly helps you build the right system for your customers, rather than just forcing you to follow dozens of irrelevant steps. In summary, participants in this tutorial will be able to return to their work places armed with knowledge of how to do requirements activities with minimum protocol and maximum results. Topics Covered:
Alan Davis:
|
Last updated: 2002-05-14 |