Session: DevOps is not a role, its a culture
For decades, software folks have had separate roles as developers or testers or DevOps or automation engineers. But what if today one could be all? Now is the time to rethink the way we work and take end-to-end responsibility for our work. During my talk, I would like to introduce DevOps and how one can be anyone or all in a team. Did you know that DevOps is not a role but a team culture? With +7 of work experience in both traditional and DevOps cultured teams, I want to share why we need DevOps culture today more than ever. DevOps culture is an ultimate solution to quench the thirst of SDLC knowledge. The best time to switch to DevOps culture was yesterday and the second-best time is now. In my lightning talk, I would share five key changes that can be made today by the teams willing to adopt DevOps culture.
- A closer look at DevOps its definition and importance.
- Key benefits of working in a DevOps team vs traditional
- Understanding how devOps can reduce bottlenecks in process and expedite product delivery
- Recommendations on incremental changes that can be made to overcome silos within a team.
- Even though a sudden cultural shift is not possible, understanding the required changes is a viable starting point
Technology enthusiastic with 7+ years of experience and graduate in MIS from Carnegie Mellon. Passionate about UI development and improving UX for the products while solving clients problems. Strongly follow and teach best coding practices and industry standards. I promote quality over speed in product delivery. I love pair and mob programming and brainstorming technical problems. While I allocate some time every week to learn something new, I share my existing knowledge in design and architecture discussions. In the future, I would like to be a Software Architect in 5 years and my longer term goal is to be a CTO.