In this tutorial, we will learn how to improve your sprints and common rookie mistakes to avoid. Take a quick look at Confessions Of A DevOps Engineer: Sprints.
On Sprint days we reflect on our accomplishments (or lack thereof) for the previous 2 weeks. It’s about 20 minutes before we jump on zoom and share our thoughts and reflect. I look at our board. I filter for my name, and I see the same tasks I started two weeks ago all “In Progress”.
I can easily justify why I wasn’t able to complete the sprint tasks. The justification always included something about requirements changing or some unforeseen roadblock or lack of data or some other “reasonable” excuse. My tasks are simply different than what everyone else is working on, right?
The truth is that my tasks are not that different than anyone else's. The only difference is my lack of experience. Experienced engineers can more accurately measure how long a given task will take and then complete the tasks accordingly.
Here I will try and describe some rookie mistakes I made and some pointers for creating tasks to complete during sprints.
DevOps and Cloud computing are joined at the hip, now that fact is well appreciated by the organizations that engaged in SaaS cloud and developed applications in the Cloud. During the COVID crisis period, most of the organizations have started using cloud computing services and implementing a cloud-first strategy to establish their remote operations. Similarly, the extended DevOps strategy will make the development process more agile with automated test cases.
What is DevOps? How are organizations transitioning to DevOps? Is it possible for organizations to shift to enterprise DevOps? Read more to find out!
What is DevOps? What are the goals it helps achieves? What are its benefits? This article has answers!
The year 2020 has arrived, and its arrival brings a lot of innovations and transformations in the Information and Technology (IT) sector to DevOps technologies.
DevOps is supposed to help streamline the process of taking code changes and getting them to production for users to enjoy. But what exactly does it mean for the process to be "streamlined"? One way to answer this is to start measuring metrics.