- Powerful techniques for identifying, documenting, and verifying requirements
- The best of both the formal Plan-Driven and Agile requirements approaches
- Use the Product Vision as a roadmap to success
- How to elicit and document system requirements
- New skills with practical, interactive exercises
Clear, concise, and accurate requirements will help avoid late, over budget, or cancelled projects. Too much documentation or inflexible requirements can bog down a project. Find the right mix of formal written requirements and Agile documentation -- user stories, use cases, prototypes, and visual models -- that works best for you.
This practical, hands-on course will provide a flexible requirements development approach customized to your environment and the skills needed to successfully discover, analyze, communicate, and evaluate requirements.
Powerful Techniques for Identifying, Documenting, and Verifying Requirements
Many acknowledge that their processes need some improvement but feel helpless to do much about the problem. In this course you will learn how to fill the critical information gaps and freshen up those stale requirements processes in a highly practical way. Take away a new awareness of what "good" requirements are really about and the skills to help you complete your project on time and on budget.
The Best of Formal Plan-Driven and Agile Requirements Development Approaches
Learn how the Plan-Driven and Agile development approaches differ in terms of timing, depth, and documentation of these valuable references. The Plan-Driven approach values product and process documentation. The Agile approach values individuals and collaboration, working software, and the ability to swiftly accommodate change.
Practice New Skills with Interactive Exercises
This course offers interactive exercises to provide practical experience and improve your requirements development skills. Use a real-world case study to identify stakeholders, develop a vision statement, and produce concise, accurate, and usable requirements documentation. Find ways to transfer the newly learned techniques back to your organization’s requirements process and take away a framework for understanding business and user needs to develop a suitable software solution.
Who Should Attend
Whether you are a requirements or business analyst, software engineer, developer, test engineer, user, stakeholder, or a member of the QA staff responsible for gathering, analyzing, documenting, confirming, and maintaining requirements, this course is for you.