Delivery Team Fields

1. Description

• What it’s for: A description of this delivery team and their role in the solution.

• What to include:

  • What the team is responsible for building or delivering.
  • Which part of the solution they own.
  • Any relevant context — e.g. a third-party supplier team, an offshore team, or a specialised platform team.

• Examples:

  • "Core platform team responsible for the API gateway and shared authentication services."
  • "Data engineering team responsible for the ingestion pipeline and data warehouse build."

2. Members

• What it’s for: The project users who belong to this delivery team.
• What it does:
  • Task reporting — a task assigned to a member is reported under their team, with no separate team assignment needed. Where someone belongs to two teams and the task has no team assigned, it is reported as cross-team rather than attributed to either.
  • Sign-off — when this team is named as an approver, any member can record the team’s decision.
• Leave it blank if: you are documenting the team for reference only. It then has only the tasks assigned to it directly, and no one can sign for it.

3. Notification Recipients

• What it’s for: Who is emailed when this team is asked to review something.
• What to include: The people who should receive review requests — typically a lead or delivery manager, rather than the whole team.
• Leave it blank and no one is emailed. ArchRepo reports the team as un-notifiable when a review is requested, and you record its decision manually.
• Only Members can be nominated: anyone chosen here who is not in Members is ignored.

Relationships

Work