This repository is home to the Operations Engineering's tools and utilities for managing, monitoring, and optimising software development processes at the Ministry of Justice. • This repository is defined and managed in Terraform
As a member of the Operations Engineering team
I want to understand how to approach building, maintaining and de-commissioning new and old services
so that I can easily create tickets that support the work for new projects/ideas
and analyse whether an existing system needs to be considered for de-commissioning
This ticket is to document a practical MvP process the team can follow to ensure we are building services using agile methodologies.
Value
To formalise our approach to building new projects and maintaining existing services to ensure they provide value and can be critically analysed later.
Formalising and explicitly documenting our approach will also enable us to critically analyse the approach itself during retrospectives, allowing us to make incremental changes over time to ensure we have a process that meets the teams and organisational needs.
Functional Requirements:
Documented in our runbooks
Non-Functional Requirements:
The document should be easy to read, understand and reference
We should use the GOV.UK Agile Delivery Guidance in the Service Manual as a reference for building a more applicable approach for our team.
Acceptance Criteria:
[ ] An MvP document added to our runbooks, detailing our approach to building and maintaining services
AntonyBishop
commented
1 week ago
User Need
As a member of the Operations Engineering team I want to understand how to approach building, maintaining and de-commissioning new and old services so that I can easily create tickets that support the work for new projects/ideas and analyse whether an existing system needs to be considered for de-commissioning
This ticket is to document a practical MvP process the team can follow to ensure we are building services using agile methodologies.
Value
To formalise our approach to building new projects and maintaining existing services to ensure they provide value and can be critically analysed later.
Formalising and explicitly documenting our approach will also enable us to critically analyse the approach itself during retrospectives, allowing us to make incremental changes over time to ensure we have a process that meets the teams and organisational needs.
Functional Requirements:
Non-Functional Requirements:
Acceptance Criteria:
Notes: