#1512 Re-align level descriptions for Requirements Definition and Management (REQM) change request pending
Par-down expectations at lower levels and provide clearer distintinctions between levels
Need a level for those who capture requirements but don't then go-on to manage requirements ... perhaps level 3 and below should focus on the gathering, and 4+ on the management (as lv4 is generally where we see responsibility for quality coming in)
'management' of requirements might be extended into sprint refinement
Proposed change applies to Requirements definition and management
Current status of this request: pending