Better
requirements lead to better project results, find out what methods
champions use to improve their performance
Duration: Half-day
Target
Audience:Senior
Management, Project Managers, Clients, Business and Technical
Analysts, System and Design Engineers, Developers, Testers,
SQA Personnel
Description: Not
respecting the discipline of Requirements Engineering can be a
costly mistake.Rushing
through the first phase, Requirements Development, leads to
increased defects, re-work, and poor product quality.Not having processes in place during the second phase,
Requirements Management, can lead to uncontrolled scope creep
and the inevitable cost-overruns.
This overview is designed to
help you understand the various types of requirements, how to
document them and how to prioritize them. It examines what
tasks the business analyst should be doing and what techniques
analysts should use to improve their results. Finally, it
reviews the management goals, activities and measurements
which must be coupled with analysis and documentation
techniques to fully realize best practice results.
What
you will learn: Students will:
Understand that poor requirements are the source of most
software development project failures
Realize the risks inherent in a project with poorly
defined and managed requirements
Learn the value of taking enough time to formally elicit
requirements from customers
Examine the different types of models that can be used
to validate requirements
Come to understand the importance of using a formal
change-control procedure
Course Outline: Why do we need Better Requirements?
Historical data on requirements quality
Impact to business
Self-Assessment Test
Types of Requirements & the Project Time Line
Types of requirements
Typical project life cycle
Expanded requirements phase time
line
Requirements in the CMMI
Requirements Development
Elicitation
Analysis
Specification (a.k.a.:
Documentation)
Verification
Requirements Management
Requirements management overview
Change control
Automated tools
Exercise:Match Requirements Area to Techniques
Summary
Prerequisites:Familiarity with Software Development