Duration: 3 Days
In this course, you will gain a better understanding of the nature of requirements risk and the need to control it. You will learn to prepare for requirements risk management by formulating a baseline requirements development process, providing tools, developing defect and root cause profiles, and conducting requirements retrospectives.
What You Will Learn
- Avoid requirements-based
failures by reconfirming needs and feasibility, managing customer expectations,
prioritizing requirements, and incrementally committing to a project
- Mitigate the impact of requirements-based defects by requiring frequent demos,
decoupling vision from build, and building in multilane cycles
- Minimize communication problems using rich definitions, algebraic formulas, spec
patterns, and picture requirements information
- Monitor requirements status by tracking requirements instability and growth, the
accuracy of assumptions, and stakeholder participation
- Identify unclear, imprecise, and missing information using requirements analysis
and reviews with stakeholders
- Build a cross-functional team and practice team success factors for requirements
development by
- Plan for
requirements risk management by eliciting meta-requirements, by brainstorming
risks, risk indicators, and root causes
- Develop a requirements risk management strategy
Audience
- Project sponsors
- System
users
- Development directors
- Project managers and leads
- Requirements managers, leads,
and analysts
- System
architects
- Functional
designers
- Verification and
test leads
- Quality
assurance staff
- Process
improvement leads
Prerequistes
Course Outline
1. Requirements Development
- Challenge of communication
- Why review and analysis don't fit find most defects
- Role of human factors
- Requirements are dangerous
2. Types of
Requirements Risk
- Application risk
- Stakeholder risk
- Process
risk
- Resource risk
- Change risk
- Implementation
risk
- Defect risk
3.
Requirements Risk Management
- Recognizing requirements risk
- Forecasting project-specific dangers
- Developing a strategy
- Monitoring reality
4. Safety Tactics 1:
Avoiding Requirements-Based Failures
- Reconfirming reality of stated needs
- Triage and prioritize requirements
- Managing customer expectations
- Reconfirming project feasibility or reduce scope
- Identifying and resolving conflicts early
- Committing incrementally
5. Safety Tactics 2:
Mitigating Impact of Requirements-Based Problems
- Requiring frequent demos of understanding
- Decoupling vision from build
- Prototyping unfamiliar functions and interfaces
- Subdividing project scope
- Building in multilane cycles
6. Safety Tactics
3a: Minimizing Communication Problems.
- Maintaining a climate of safety and respect
- Documenting assumptions
- Marking intentional imprecision
- Using rich definitions
- Using derived values rather than "magic numbers"
- User types and creating user personas
- Clarifying with examples and measures
- Structuring information with spec patterns
- Picturing requirements information
- Capturing context
7. Safety Tactics 3b: Minimizing
Other Problems
- Improving results of current requirements development process
- Identifying minimal sets of marketable features
- Focusing on quality and environmental requirements early
- Identifying impacts and mitigation strategies
- Analyzing benefits, risks, priorities, and costs of proposed requirements and
changes
8. Safety Tactics 4: Monitoring Requirements
Status
- Monitoring
requirements instability and growth
- Monitoring accuracy of assumptions, expectations, and priorities
- Monitoring stakeholder participation
- Using workshops to find issues early
- Incrementally review long specifications
- Unclear, imprecise, and missing information
- Estimating defect risk
- Verifying satisfaction arguments of derived requirements
- Tracking requirements defects
- Analyzing and classifying requirements defects and root causes
9.
Safety Tactics 5: Staffing for Requirements Development
- Building cross-functional team
- Supplementing with outside knowledge, skill, and experience
- Replacing underperformers and disruptors
- Training stakeholders in technical communication
- Immersing stakeholders
10. Safety Tactics 6: Planning
for Requirements Risk Management
- Eliciting meta-requirements
- Brainstorming risks and tactics
- Risk indicators and root causes
- Customizing requirements development and specification strategy
- Customize, carry out, and monitor requirements risk management strategy
11.
Safety Tactics 7: Preparing for Requirements Risk Management
- Formulating baseline requirements processes
- Systematizing change management, requirements defect, and failure tracking
- Providing tools supporting safer requirements
- Developing requirements defect and root cause profiles
- Conducting requirements retrospectives
12. Safety Tactics 8:
Compensating for Requirements-Based Problems
- Estimating and tracking requirements-based rework
- Adjusting for surprises
Exercises:
Exercise 1: Identify
requirements risks
Exercise 2: Identify challenges of incremental commitment
Exercise 3: Create rich definitions, including a derived value, quality
profile, and action contract
Exercise 4: Replace a "magic number" with a
derived value
Exercise 5: Create a state transition table and then share with
the entire group
Exercise 6: Requirements change measures
Exercise 7:
Brainstorm risks and tactics for a case study
Exercise 8: Tactics usage
process
Course Labs
