This course builds on the best practices for Scope Management already taught in the PMP^® Exam Preparation Course. The course teaches students how to put the theories taught by the PMP^® Exam Preparation Course into practice. The course focuses on how to create and implement a requirements management plan, how to distinguish between needs and wants, how to tailor your plan to suit your SDLC methodology. This is a 3 day course using classroom lectures, visual aids, examples, and exercises to enhance learning. This course will provide the student with 22.5 PDU’s.

Day 1:

• Introductions, 3 day agenda and course overview, identifying student goals and objectives for the course.
• A review of CMM, RAD, RUP, and Waterfall SDLC methodologies and the impact of each on Requirements Management.
• Crafting the Requirements Management Plan including: requirements gathering activities, identifying roles and responsibilities, identifying the proprer sign-off authority on requirements documents, document version control, integrating the plan with the MS Project plan, and the difference between software requirements and project scope.

Day 2:

• Requirements gathering techniques including: storyboarding, commercial specs, prototypes, and brainstorming.
• How to identify the stakeholders who should contribute requirements, how to verify requirements, and breaking the work down (creating the Work Breakdown Structure, or WBS).
• Creating effective commercial specifications and the subject matter experts who should contribute, creating effective functional specifications and the subject matter experts who should create them, and creating the detail design documents and the subject matter experts who should create them.
• An exercise requiring the class to group together in teams of 4 or 5 students to read analyze a case study and propose solutions which they will present to the class.

Day 3:

• Implementing the Requirements Management Plan including: conducting design document walkthroughs, conducting code walkthroughs (or reviews), and how to implement a change to the scope baseline.
• Verifying project requirements: identifying various types of tests (unit, function, thread, system, and performance), load and stress testing, identifying tests with requirements, communicating test results to stakeholders, and how to convince your stakeholders that requirements have been met at the final gate review.
• Review of the students goals & objectives, questions and answers.