Team development plan:
| Field | Entry |
|---|---|
| Test manager | |
| Team | |
| Period | |
| Reviewed with | Head of test |
1. Purpose
What the team needs to be able to do in 12 months to deliver the automation strategy (link to Automation strategy and metrics).
2. Team skills now
Aggregate only. Use counts, not names.
| Skill | Expected level for most of the team | Meet now | One level below | Two or more below |
|---|---|---|---|---|
| Test engineering | ||||
| Designing and executing tests | ||||
| Test analysis | ||||
| Managing, reporting and resolving defects | ||||
| Clinical risk management | ||||
| Information governance and data protection | ||||
| Health data interoperability |
3. Priorities
The two or three gaps that matter most for the team over the next 6 to 12 months.
4. Actions
| Action | Who (role, not name, in shared copies) | Type (programme cohort, pairing, course, community of practice, stretch task) | Owner | Due | How we will know |
|---|---|---|---|---|---|
5. Capacity
How protected learning time is found without harming delivery, and what delivery work is paused or moved.
6. Succession and resilience
Who can maintain each automated suite and pipeline if its main author is away. Aim for at least two people for each.
7. Wellbeing
How the team manages the pressure of learning while delivering. Agreed signs that someone needs more support.
8. Review
Review dates, and how progress is reported to the head of test.
View this document on GitHub materials/tracks/leading-automation-adoption/team-development-plan-template.md