Requirements management
The ability to collect, align and record requirements so that implementers understand what to do, the customer knows what they will get and changes remain manageable.
Definition
BT360 v2.0.0The ability to collect, align and record requirements so that implementers understand what to do, the customer knows what they will get and changes remain manageable.
What is it made up of?
3 INDICATORS- 01Collecting and clarifying requirements
- 02Aligning and recording
- 03Managing requirement changes
Behavior levels 0–5
MANAGER'S GOAL - 3| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | Requirements are verbal and contradictory; implementers guess; changes are uncontrolled; the result does not match expectations. |
| 1 | Poorly developed | Collects wishes; records them superficially; does not surface contradictions; accepts changes without assessment; the customer and the implementer understand things differently. |
| 2 | Underdeveloped | Compiles a list of requirements; aligns the main ones; processes changes with a delay; acceptance criteria are vague. |
| 3 | Normally developed leader's goal | Collects and clarifies requirements; surfaces contradictions; records acceptance criteria; aligns the parties; manages changes. |
| 4 | Highly developed | Works with conflicting requirements; finds the true need; ensures traceability; manages changes and priorities; reduces the risk of rework. |
| 5 | Overdeveloped | Requirements turn into bureaucracy: endless approvals and documents, changes are not accepted; speed drops; the customer walks away. |
How is it measured?
coating BSJT - BT360 situational test: provides a hypothesis about judgments in work situations and does not replace observation, 360 and interviews.
There is no direct test; communication competence is indirectly related to requirements gathering. The level is confirmed by the quality of the specification.
Development Actions
5 CATEGORIESPractical task: collect requirements for a case, surface contradictions, record the criteria.
Course 'Requirements management': collection, clarification, criteria, changes, traceability.
Run requirements collection for one project and defend the specification to the customer and the team.
Review with implementers: where the requirements were ambiguous.
Introduce a template for requirements and acceptance criteria in the team.