/
Terminology when referring to ourselves
Terminology when referring to ourselves
Status | Decided |
Decision leader | @Andy Nash (Unlicensed) |
Contributors |
|
Date | Jan 4, 2023 |
Outcome | Documentation of different ways of referring to ourselves |
Various terms are being used to describe us / sections of the overall team.
Came up as an issue on an Admin Product Team Retro.
This is a starter for 10 proposal for comment.
Actions
Review proposal and comment
Brainstorm any scenario where we think we may want/need to sub-divide the TIS Team in any other ways
(hopefully this will trigger a discussion to determine whether the team feel in those scenarios it is valid to have a more 'exclusive' group, or whether those scenarios would benefit from a more 'inclusive' approach)
(hopefully this will trigger a discussion to determine whether the team feel in those scenarios it is valid to have a more 'exclusive' group, or whether those scenarios would benefit from a more 'inclusive' approach)
Outcome
TBC
, multiple selections available,
Related content
Decision log
Decision log
Read with this
Documentation, Communications and Support
Documentation, Communications and Support
More like this
Agile / Scrum / Kanban / basics
Agile / Scrum / Kanban / basics
Read with this
Copy of 2022/3: Q3 | Admin Team Review#6 (2023-01-17 to 2023-01-31)
Copy of 2022/3: Q3 | Admin Team Review#6 (2023-01-17 to 2023-01-31)
More like this
Roadmap - current work and priorities
Roadmap - current work and priorities
Read with this
2022/3: Q4 | Admin Team Review#1 (2023-01-31 to 2023-02-14)
2022/3: Q4 | Admin Team Review#1 (2023-01-31 to 2023-02-14)
More like this
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213