Delivery Teams
ArchRepo is an architecture repository, not a project management tool.
However, sometimes it is useful to document different delivery teams and their responsibilities.
This helps when documenting tasks around the different building blocks, associating those to different teams.
For example, you may have a front-end development team separate from a backend team.
You can then filter task kanbans by the different teams, providing a team-focused lens on activities related to each solution element.
Assigning work to a team
There are two ways a task ends up under a team:
- Assign the task to the team — link the task to the Delivery Team.
- Assign the task to a person — if that person is in the team’s Members, the task is reported under their team automatically.
Where someone belongs to more than one team and the task has no team assigned, it is reported as cross-team rather than attributed to either.
Do I need to license everyone in a team? Not to document one — you can record a supplier or partner team without any of its people being ArchRepo users.
Adding them as project users matters when you want more: Members lets ArchRepo report an individual’s tasks under their team and lets them sign off on the team’s behalf, and Notification Recipients sets who is emailed when the team is asked to review.