- Implement a step-by-step business and user requirements development methodology
- Write well-formed and accurate requirements within an engineering and business framework
- Elicit and organize requirements information to set and manage stakeholder expectations
- Analyze and derive requirements to keep the project focused on the desired results
- Develop requirements documentation to accurately target the problem domain
- Apply techniques to thoroughly validate, confirm and manage project requirements
In a series of case study-based workshops, participants work in small groups to apply the techniques learned throughout the course. Workshops include: - Practicing situational requirements elicitation techniques
- Using gap analysis techniques to derive new user scenarios
- Writing user requirements targeting the project scope
- Evaluating modeling approaches
- Addressing the impact of changing scope on baseline requirements
- Planning a requirements walkthrough meeting
- Building a business case for the project
- Designing traceability matrices to map the relationship between requirements
Successful projects within the development environment begin with a clear definition of business and user requirements. Specifying the business context and user needs ensures the outcome is beneficial to both the user and the wider organization. This course introduces a comprehensive, practical process for the step-by-step definition of organizational and user requirements. You apply real-world techniques to specify, elicit, analyze, validate and manage the requirements that create a framework for project success.
This course is valuable for those involved in managing and defining projects. This course is PMI-aligned for 23 PDUs. COURSE OUTLINE: - An iterative spiral model for requirements
- The five steps: specify, elicit, analyze, validate and manage
- Confirming, prioritizing and managing
- Documenting the resulting requirements
- Evaluating document layout & structure
- Determining the purpose and intent
- Quantifying functional and non-functional requirements
- Characteristics of effective requirements
- Applying the IEEE requirements checklist to ensure polished content
- Achieving project goals and objectives
- Defining levels of detail within the process
- Identifying the project environment, existing workflow and all stakeholders
- Harnessing multiple information sources to deliver quality requirements
- Tried-and-tested elicitation techniques
- Driving the process using questionnaires
- Incorporating iteration and feedback
- Employing techniques to uncover hidden needs
- Employing functional, top-down decomposition to elicit data
- Selecting classification approaches
- Negotiating conflicting requirements
- Choosing the best modeling techniques
- Building old and new scenarios
- Addressing stated, real and unknown requirements
- Overcoming management resistance
- Leveraging reviews and walkthroughs
- Prototyping and storyboarding
- Breaking the scope into logical subsets
- Assigning stakeholder roles
- Structuring the document using the IEEE Concept of Operations template
- Framing requirements to support customer strategy and justification
- Bridging from existing to new functionality using a gap analysis
- Structuring, deriving and organizing
- Evaluating industry templates
- Establishing requirements focus: user vs. system
- Creating and maintaining TMs
- Building traceability best practices
- Establishing backward and forward traceability matrices
- Basing traceability upon system hierarchy and document sets
- Transforming common sense activities into formal practice
- Evaluating requirements management processes
- Implementing effective mechanisms for managing change
- Policing unofficial requirements
- Recognizing future requirements
|
