Task: Agree Output Requirements
This task provide the customer side of the customer-supplier agreement processes for agreeing transverse requirements from one development team to another and for agreeing requirements that are flowed down from one level to the level below.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

This task is the dual of the task "agree input requirements" and essentially takes the “customer” role in the customer-supplier agreements that deals with the following sources of requirements:

  • Requirements from Level Below.
  • Requirements from Specialist Domain.
  • Requirements from Other Teams at the same level.

For each different sources, there is a slightly different approach to handle reviewing and agreeing the requirements in order for the customer's side to produce the input requirements for this level. The following paragraphs will provide details for each approach.

Agree Requirements with the Lower Level:

This task provides the customer side of the customer supplier agreement between two adjacent levels in the flow down of requirements.
This process identifies those requirements at this level that are relevant to a specific development team at the level below. The process may use an allocation (often termed “pre-allocation”) approach in which the Team at this level makes an initial suggestion about the requirements that should be given to each Team at the level below. Alternatively, the process may use a bidding approach in which each Team at the level below proposes which requirements they should address.

The Team at the level below may wish to change the wording of any relevant requirement. This can be because it is unclear as currently worded and the change can lead to a common understanding of the intent. Changes can also be suggested because the Team at the level below knows from experience that is will be impossible to implement it or that the cost/risk would be too high.

Agree the Requirements Baseline being cascaded to each team at the level below from this level

Agree Requirements with the Lower Level

Agree Requirements with the Lower Level

Agree Requirements from Specialist Domains:

Within the project hierarchy, requirements are cascaded down. However, the Transverse Specialist requirements exist in ‘parallel’ to the project cascade and at the appropriate point in the hierarchy, these Transverse requirements must be incorporated into the design. The documentation that defines these Transverse requirements is usually ‘multi granular’. That is, there are varying degrees of detailed requirements.

Agree Requirements from Specialist Domains

Agree Requirements from Specialist Domains

Agree Requirements for Other Teams:

As indicated earlier, it is sometimes necessary for one team to generate requirements for another team. Such requirements are generated in the "Create output requirements" task. This task provides the customer side of that agreement. It therefore takes the output requirements generated and agrees them with the intended recipient in "agree input requirements".

Agree Requirements for Other Teams

Agree Requirements for Other Teams

Steps
Identify the Requirements Baseline.

In case of specialist domain requirements, do the following:

1. Identify the set of specialist requirements that are relevant to each development team at each level.
2. Propose a set of uniquely identified incoming transverse requirements for each development team at each level
3. Establish traceability from each input transverse requirement to the relevant specialist requirement(s)

Agree Requirements.
Identify and Agree intended MoC for each requirement.
Agree the rationale for each requirement.
Is the need for the requirement really justified?
Sign (Authorise) the document or specification.

This signing is between:

  • this level and the level below.
  • this level and Transverse team(s), the other teams.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable