The document discusses lessons learned from developing a DevOps platform. It notes that businesses expect the platform to never break down, be highly available, automatically scale to meet demand, have automated infrastructure and CI/CD pipelines covered by tests, and permanently meet all developer requirements without needing support. The solution architect questioned how realistic these expectations were. It suggests formalizing a knowledge sharing process and checklist to transfer DevOps knowledge and responsibilities from the DevOps team to development teams as the DevOps toolkit evolves rapidly.

1. DevOps platform development –
lessons learned.
Victoria Basarab, Technical PM at
Ring Ukraine

2. What business expects from us:
Platform which:
- never breaks down
- highly available
- scales automatically to meet demand
- Infrastructure automation, CI/CD covered with tests
- Platform permanently covers all Devs requirements
(Product of any nature/ any programing language)
and NO SUPPORT NEEDED !!!!

3. What did my Solution architect think about it?

5. How does Platform and other software differ?
Statement 1: PO in Dev Teams mainly works with functional requirements and
DevOps Team mainly works on non-functional stuff.

7. Statement 2: DevOps toolkit evolves too rapidly

8. Statement 3:
Platform introduction to its end users - Developers
Output: Formalized knowledge sharing process. Implementation of some kind of DevOps
knowledge checklist - which provide possibility of transfer knowledge and ownership to Dev Teams.

9. Why we do it?