DevOps Issue Board
=====> ISSUE BOARD <=====
Workflows
Training
Training Criteria List
Automation implementation
"Automation is a core principle of DevOps. So, the implementation of said automation clearly falls on the shoulders of DevOps teams. It’s the responsibility of everyone from the data team to the frontend team to automate tasks and improve the efficiency of engineering and IT. By constantly automating mundane tasks, you’re able to focus more on strategic development and driving business value."
Maintaining CI/CD pipelines
"Being part of a DevOps team means you have a responsibility for building a CI/CD pipeline and optimizing processes, people and tooling. DevOps-minded engineers will see ways they can constantly improve the pipeline – from people to processes. The team will shift testing and QA further left into the development cycle, allowing the team to continuously test without restricting speed."
Application and infrastructure planning, testing, and development
"The entire DevOps team is in charge of application and infrastructure planning, testing, and development. Sharing the responsibility for the development and release pipeline leads to more reliable services. Being part of a DevOps team doesn’t mean you have an entire team made up of “DevOps Engineers” – but, a DevOps-oriented company will spread the accountability for application development, testing and release across the entire engineering and IT organization."
Monitoring
"DevOps teams are responsible for the implementation of actionable monitoring solutions. The organization needs to collect data and know how they can take action with it. The DevOps team (aka everyone) is responsible for exposing blind spots in their applications and infrastructure, and then figuring out how they can monitor those services. Monitoring is just one small step into building highly observable systems – but it’s an important start for building reliable systems."
On-call, incident response, and incident management
"With shared accountability and code ownership, DevOps teams need to take on-call responsibilities and incident management work. But, the more time the DevOps team spends responding to incidents in production, the more they learn about their systems. So, over time, developers start to write code that better fits into their applications and infrastructure – leading to fewer incidents. And, IT teams gain more influence in the development lifecycle, helping them proactively deepen the reliability of services being deployed."
Evaluation
Automation implementation
- Member can determine which task can be automating and use suggest tools.
- Member can implement scripts for automating mundane tasks.
Maintaining CI/CD pipelines
- Member can implement a pipeline for a simple workflow, including build and deploy.
- Member can implement a pipeline that including automation testing jobs (unit test, integration test, security test).
- Member can optimize pipeline.
Application and infrastructure planning, testing, and development
- Member can propose a plan for deploy an application.
- Member can test the deployed infrastructure.
- Member can create infrastructure documents and plan for improvement.
Monitoring
- Member can use common monitoring tools.
- Member can implement monitoring metrics into source code while not affect any business logic.
- Member can implement alerting based on implemented metrics and collected data.
On-call, incident response, and incident management
- Member can determine the source of problems.
- Member can perform actions to resolve the problem and provide solutions for future improvement.
Grading scale
WIP
Outcomes
TODO
