| In an ideal world, eliciting, analyzing, validating, and writing accurate requirements, and delivering them to the project team would be sufficient. In the real world, this is just the start of the process. The baseline document that you have delivered will accrue changes as you move to the construction phase of the project, and requirements often change post-delivery. The degree to which you control these changes, and accurately assess their impact on the project, is a major element in project success. This course develops your ability to control the requirements package through baselined requirements, change control, and traceability. Together these make up industry-standard best practice, as defined by the International Institute of Business Analysis (IIBA), Project Management Institute (PMI), and the Software Engineering Body of Knowledge (SWEBOK). Participants will learn how to: Create the criteria by which changes to your baseline requirements will be prioritized and decided, Use traceability matrices and requirements capture tools to understand how change impacts related requirements, Select appropriate techniques for each stage of the change control process, Prioritize new requirements by your identified criteria and a range of prioritization techniques, Handle requirements changes in both agile and formal projects, Manage changes to the requirements documentation. Details
|
Login/Create account
checkout
view cart (
0
)
