Community collaboration
Collaboration in the Government Digital and Data profession typically involves working in a multidisciplinary project team, and contributing to working groups and wider professional communities. It requires a broad understanding of the technologies, principles and perspectives of related professions.
Levels
- 1. Awareness
You can:
- understand the work of others and the importance of team dynamics, collaboration and feedback
- 2. Working
You can:
- contribute to the work of others
- motivate and empower teams
- create the right environment for teams to work in, and can identify the best team makeup depending on the situation
- recognise and deal with issues
- 3. Practitioner
You can:
- work collaboratively in a group, actively networking with others
- adapt feedback to ensure it’s effective and lasting
- use your initiative to identify problems or issues in the team dynamic and rectify them
- identify issues through Agile ‘health checks’ with the team, and help to stimulate the right responses
- 4. Expert
You can:
- solve and unblock issues between teams or departments at the highest level
- coach the organisation on team dynamics and conflict resolution, while also building and growing the community
Contains public sector information from the UK Government Digital and Data Profession Capability Framework (https://understand-digital-data-roles-skills.service.gov.uk/), licensed under the Open Government Licence v3.0. © Crown copyright.
Closest ESCO skills
Contains ESCO v1.2.1 data (https://esco.ec.europa.eu/). © European Union. Reuse authorised under Commission Decision 2011/833/EU.
Role levels that expect this skill
| Role level | Role | Band | Expected level |
|---|---|---|---|
| Configuration analyst | Change and release manager | 4 | Working |
| Change and release analyst | Change and release manager | 5 | Working |
| Change and release manager | Change and release manager | 6 | Practitioner |
| Enterprise architect | Enterprise architect | 8a | Working |
| Senior enterprise architect | Enterprise architect | 8b | Practitioner |
| Lead enterprise architect | Enterprise architect | 8c | Practitioner |
| Principal enterprise architect | Enterprise architect | 8d | Expert |
| Apprentice frontend developer | Frontend developer | 4 | Awareness |
| Junior frontend developer | Frontend developer | 5 | Working |
| Frontend developer | Frontend developer | 6 | Practitioner |
| Senior frontend developer | Frontend developer | 7 | Practitioner |
| Lead frontend developer | Frontend developer | 8b | Practitioner |
| Head of frontend development | Frontend developer | 8c | Expert |
| Incident manager | Incident manager | 5 | Working |
| Major incident manager | Incident manager | 7 | Practitioner |
| Problem analyst | Problem manager | 5 | Working |
| Problem manager | Problem manager | 6 | Practitioner |
| Program delivery manager | Program delivery manager | 8b | Expert |
| Senior program delivery manager | Program delivery manager | 8c | Expert |
| Associate solution architect | Solution architect | 7 | Awareness |
| Solution architect | Solution architect | 8a | Working |
| Senior solution architect | Solution architect | 8b | Practitioner |
| Lead solution architect | Solution architect | 8c | Practitioner |
| Principal solution architect | Solution architect | 8d | Expert |
| Associate technical architect | Technical architect | 6 | Awareness |
| Technical architect | Technical architect | 7 | Working |
| Senior technical architect | Technical architect | 8a | Practitioner |
| Lead technical architect | Technical architect | 8b | Practitioner |
| Principal technical architect | Technical architect | 8c | Practitioner |