<aside>

</aside>

We strongly suggest that all apprentices taking part in the DevOps apprenticeship saves a copy of the Duties and KSBs (in whatever format suits) and works together with the employer to add supporting evidence of where they have met each criteria. This will enable both the apprentice and employer to be certain that when entering the EPA process, they have met all the criteria required for the apprenticeship and have examples to draw from during the assessment process.

Duties

DUTY	KSBS	Where is this met by FAC’s curriculum?	When has the apprentice met this during employment?	Supporting evidence
Duty 1 Script and code in at least one general purpose language and at least one domain-specific language to orchestrate infrastructure, follow test driven development and ensure appropriate test coverage.	K4 K5 K6 K7 K8 K11 K12 K13 K14 K20
S9 S11 S13 S14 S16 S17 S18 S20 S22
B2 B3	All of 12 week training block
Duty 2 Initiate and facilitate knowledge sharing and technical collaboration with teams and individuals, with a focus on supporting development of team members.	K4 K9 K10 K18 K19 K23
S1 S2 S4 S8 S16 S21
B1 B2 B4	All of 12 week training block
Duty 3 Engage in productive pair/mob programming to underpin the practice of peer review.	K4 K6 K7 K9 K20
S1 S8 S13 S14 S17 S18
B1 B3	All of 12 week training block
Duty 4 Work as part of an agile team, and explore new ways of working, rapidly responding to changing user needs and with a relentless focus on the user experience. Understand the importance of continual improvement within a blameless culture.	K4 K6 K9 K10 K18 K19 K22 K23
S1 S2 S3 S4 S8 S11 S21
B1 B3 B4	All of 12 week training block
Duty 5 Build and operate a Continuous Integration (CI) capability, employing version control of source code and related artefacts.	K1 K2 K7 K14 K15 K24
S4 S9 S12 S15 S16 S18 S20
B3	- All weeks BUT we need to cover in greater depth in weeks 7-12. In process of introducing explicit learning goals for Dev Ops apprentices.

Apprentices to take Dev Ops for every project across programme. | | | | Duty 6 Implement and improve release automation & orchestration, often using Application Programming Interfaces (API), as part of a continuous delivery and continuous deployment pipeline, ensuring that team(s) are able to deploy new code rapidly and safely. | K1 K2 K7 K15 K17 K24 S4 S5 S9 S12 S15 S16 S18 S20 B3 | - Saturday Unschool sessions and will be incorporated in weeks 7-12 | | | | Duty 7 Provision cloud infrastructure using APIs, continually improve infrastructure-as-code, considering use of industry leading technologies as they become available (e.g. Serverless, Containers). | K1 K2 K3 K7 K8 K11 K12 K13 K14 K15 K17 K21 K24 S4 S5 S6 S9 S12 S15 S16 S18 S21 S22 B3 | - Looks like Saturday Unschool sessions - added to week 7-12 | | | | Duty 8 Evolve and define architecture, utilising the knowledge and experience of the team to design in an optimal user experience, scalability, security, high availability and optimal performance. | K1 K3 K4 K6 K7 K8 K9 K10 K11 K12 K15 K21 K24 S1 S2 S4 S8 S9 S10 S11 S15 S16 S17 S18 S21 S22 B1 B3 | - Looks like Saturday Unschool sessions - add to week 7-12 | | | | Duty 9 Apply leading security practices throughout the Software Development Lifecycle (SDLC). | K3 K4 K5 K6 K7 K8 K9 K10 K11 K12 K16 S3 S4 S9 S10 S11 S14 S16 S17 S18 B1 B3 | WIP | | | | Duty 10 Implement a good coverage of monitoring (metrics, logs), ensuring that alerts are visible, tuneable and actionable. | K4 K6 K7 K10 K11 K13 K24 S3 S4 S6 S7 S9 S11 S16 S17 S18 S19 B3 | WIP | | | | Duty 11 Keep up with cutting edge by committing to continual training and development - utilise web resources for self-learning; horizon scanning; active membership of professional bodies such as Meetup Groups; subscribe to relevant publications. | K4 K9 K10 K22 K23 K24 K25 S4 S16 B1 B2 | All of 12 week training block | | | | Duty 12 Look to automate any manual tasks that are repeated, often using APIs. | K1 K4 K6 K7 K8 K11 K13 K14 K15 K17 S4 S5 S7 S12 S15 S17 S18 B3 | All of 12 week training block | | | | Duty 13 Accept ownership of changes; embody the DevOps culture of 'you build it, you run it', with a relentless focus on the user experience. | K4 K6 K9 K10 K22 K23 K24 S1 S2 S4 S6 S7 S8 S11 S17 S18 B1 B3 B4 | All of 12 week training block | | |

KSBs

<aside> 💡 During each Progress Review, we will be asking apprentices to share their progress against each of the KSBs with FAC and their line manager.

Prior to attending the review apprentices must complete the survey sent out by the Relationships Lead. In this survey, apprentices will select at least 1 (but no more than 3) of the criteria for the knowledge, skills and behaviours required in the portfolio.

Please be prepared to talk through your evidence for at least 1 knowledge, 1 skill and 1 behaviour at the Progress Review. The evidence can be via your portfolio, or other relevant documentation

</aside>

Knowledge

[ ] K1: Continuous Integration - the benefits of frequent merging of code, the creation of build artefacts and ensuring all tests pass, with automation throughout - including common tooling.
[ ] K2: The principles of distributed Source Control, including how to exploit the features of the tool, such as branching.
[ ] K3: How to use data ethically and the implications for wider society, with respect to the use of data, automation and artificial intelligence within the context of relevant data protection policy and legislation.
[ ] K4: The business value of DevOps in terms of Time, Cost, Quality, with an emphasis on building in internal Quality throughout the lifetime of the product.
[ ] K5: A range of modern security tools and techniques - e.g. threat modelling, vulnerability scanning and dependency checking, with a general awareness of penetration testing - in order to deal with threats and attack vectors within code and across the cyber domain.
[ ] K6: A range of problem solving techniques appropriate to the task at hand, such as affinity mapping, impact maps, plan-do-check-act/Deming.
[ ] K7: General purpose programming and infrastructure-as-code.
[ ] K8: Immutable infrastructure and how it enables continuous refreshing of software, namely the updating of the operating system, container and security patching.
[ ] K9: Different organisational cultures, the development frameworks utilised and how they can both complement each other and introduce constraints on delivery.
[ ] K10: How the user experience sits at the heart of modern development practices in terms of strategies to understand diverse user needs, accessibility and how to drive adoption.
[ ] K11: Monitoring and alerting technologies and an awareness of the insights that can be derived from the infrastructure and applications - collecting logs and metrics, configuring alerting thresholds, firing alerts and visualising data.