Lesson finished
Up next: Agile Values, Principles, Waterfall Comparison and DevOps Careers
Unlock all 24 lessons of DevOps FundamentalsFull course ₹40,000 · paid
DevOps Toolchain Categories and Agile Scrum versus Kanban
A free lesson from Skill-Lync's DevOps Fundamentals course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 2 Part 1”
What will you learn in this free DevOps Fundamentals lesson?
Surveys DevOps tools by category, including monitoring, configuration management, CI/CD, testing, code review, build and source repositories. Then introduces the agile methodology as a way to deliver faster and compares Scrum and Kanban on handling changing requirements and metrics.
- Tool categories such as Nagios, Ansible, Jenkins and Selenium
- Why tools matter for DevOps implementation
- Agile's goal of faster delivery
- Scrum velocity versus Kanban cycle time and throughput
What comes after lesson 2?
The next free lesson is lesson 3, “Agile Values, Principles, Waterfall Comparison and DevOps Careers” (24 min). Later in Skill-Lync's DevOps Fundamentals course (paid): lesson 4, Week 2 Session 1; lesson 5, Week 2 Session 2; lesson 6, Week 3 Session 1. The full course has 24 lessons (10 h 27 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Now let's talk about the DevOps tool chain here. Very important thing because we can understand that the DevOps implementation processes is one thing, is one aspect. But without the tool, it's just an empty or a kind of partial implementation. If you don't have the specific tools implemented, if you don't have the proper tools implemented, you're always going to face some issues in the overall implementation. So when we talk about the DevOps tool chain, so we are going to talk about certain processes, certain automations in place. Now there is a huge tool chain which is available over here. If you talk about this, that there are some couple of tools which is coming up over here in this one. Now when I talk about the DevOps tool, so there are different categories of tools which is available right away. Starting off from the top, we do have a monitoring tools like Nikios, Prometheus, Ragoon.
These are some couple of monitoring tools which is available there, which is taking care of the overall monitoring of the systems of the infrastructure. Then we also have an orchestration tool. Now the purpose of orchestration tool is to perform the deployments or orchestration things for you. So that's also another category of tool which is available there. We do have the configuration management tool and automation tools like Puppet, Chef, Ansible, Terraform, Solstack, AWS Code Deploy, Microsoft Azure. These are a couple of configuration management tools are available there. There are also some tools like Azure DevOps and GitLab which provides the CI, CD automations workflows which can cover more than one aspect of the DevOps.
And when we talk about the deployments, the same configuration management tools can be used for that. But again, we have the specific tools like Urban Code Deploy, Fabric, Capstreno. So these tools are the specific deployment tools which is available there. From the continuous integration and delivery also, we have Jenkins, Bamboo, Travis CI, these different tools which is available there. From testing, we have the Selenium, Jmeter, these are the different tools available. From the code review and analysis, we have the code climate, the SunarCube, these are the tools available there.
From the build perspective, we have Gradle and Mabel tools available. And for the code repository, the source code repository, we have got Apache server version. These are the different tools which is available for us and we can handle this stuff here. So these are the different tools and the implementations which we are talking about which really helps us to see like how the code development can be handled and we can take care of these different kind of implementations as such here. So these are the different DevOps toolchains which is available with us and which is taking care of all the different functionalities and the implementations as such here.
So that's the DevOps toolchain implementation all together. Now, what is the Agile methodology? Now, let's talk about the Agile a little bit because when you talk about DevOps, Agile automatically comes into the picture. It's a kind of a pre-request for the DevOps implementation. One cannot expect to implement DevOps without the Agile and similarly, Agile is a basis of the implementation of DevOps. Now, here when we talk about the Agile methodology, so we have certain processes to be discussed like if we talk about the overall SDLC cycle, which you guys have, you know, talked about there.
Now, Agile is all about the iterations like it's something which take care of the requirement in the same iterative approach. In this case, you can see there is a requirement analysis, the requirement gathering, which is available there. Then after that, we take care of the design phase, like we take care of like how the design can be managed. We also take care of the iterations, demo and feedback. That's also like something which we take care of during the development process. We also identify the defects, bugs and resolve the issues.
So it's also like about these different things that what kind of problems and issues we are handling up there. The production and technical support, that is also something which is available with us. So we are taking care of the development process. And once the overall implementation is done, the overall deployment is done, it's delivered to the client. This whole activity will be again repeated back in the next iteration. So it's an iterative approach which keeps on repeating itself and it's going on again in the loops, again and again, again and again over here.
So that's a kind of a scenario, that's an implementations which we are trying to look upon over here. And we are looking forward for the different standards as such here. So that's a kind of a standard approach which we are following and we are considering those things up here. So this is an agile methodology which is very, very important for anyone who wanted to go for the agile implementation and the agile development as such. Now, agile methodology is something which is developed around 2001. It's kind of a discussion which was happening within some group of experienced software developers like Ken Bank, Martin, Ron, Ken and Jeff.
So they all came up with the new process like, you know, agile. So they were just trying to provide a fix that how the things can be done in a better way. So in this whole approach, they come up with a solution that they wanted to go with an agile manifesto. So this manifesto was documented with the shared beliefs like, you know, you and me have some different beliefs. So it was all recorded like a discussion, a kind of information which anyone can actually process. So they discussed all the couple of problems which they were forcing because at that time people were using waterfall model and it was not that much efficient.
So they shared their own matter of concerns and a couple of group of people were just trying to come up with a solution so that they can propose this solution to the industry, to the people. And from there, they can go ahead and they can hold up the things. So that was the idea to find out modern best practices, modern software development process, which can be helpful for the teams to handle the things to work it off there. They also endorsed like the collaboration, like how the documentations, the self-management.
So that's the kind of implementations they were trying to do. They were trying to handle it up over there. It was also intended that the whole process needs to be made faster, like a little bit processed over here. So that we don't face any particular issues or any kind of problems as such there. So we are just trying to make sure that the overall development process can be made faster. And that's what we are trying to do. We are trying to handle it up over here in this case.
This is the main approach which we are trying to configure because ultimately we are just trying to see like what exactly is the end result is the main process which we are trying to handle it up over here. So that's the agile process we are trying to talk about here. Also, agile software development methodology is something which was one of the simplest and the additive approach which was there. And it was something which was taking care of like how the things done in a better way.
Now, the ultimate goal of agile development is just to make the delivery faster because at that moment of time, people were taking like three months, four months, that kind of time duration was being taken care. But we wanted to do these things in a less duration of time. And that's where they, you know, try to come up with a solution that how the things can be done in a faster way. And that's the approach. That's the ultimate goal which the teams were handling, which they were discussing up as such there.
So that was the goal and keeping in mind that goal, they wanted to implement, they wanted to proceed further with that particular flexibility. Now, it also focuses on how the business requirements can be met because they really wanted to make sure that all the business requirements can be met and we will be able to fulfill all those things. So keeping in mind that they wanted to share, they wanted to collaborate those couple of things as such there. Also, the whole idea about the agile is to increase the overall quality of the product, whatever the bad practices and the bad processes which was present.
So they were just trying to remove those so that they can get a final product. They can get a particular final high quality product and the overall benefits of the agile should help the developers to do the things in a better way. So before that, the developers were doing the things in a very haphazard manner. But after that, they derived a process and they got a certain processes over there so that we can go over these processes and we can get our desired output. Also, like when we talk about the agile, there are two most widely processes which we define.
One is the scrum and one is the kanban. These are actually the part of the agile there. So some teams, some development teams follow the scrum and some teams follow the kanban. It totally depends on teams to teams that which process they really feel like they wanted to implement so they can go for that particular process here. So that's depending on the different teams to teams over here in this case. Now, what is the scrum here? Now, scrum is one of the agile development method which actually helps us to like have a smaller teams like a smaller workable teams like a members of seven and nine members.
That's a standard which is being promoted by the scrum team. It's not like recommending to have a big teams like a larger teams. So it's just recommending that we should be having a small working teams which is available with the members of seven to nine members. So that's the number of members which we feel like we want to have so that if. If there is any kind of issues, we can handle those things, we can work it off there. Also, Scrum is something which is widely used, like it's something which is being used to manage the complex software development, right? So, it's an iterative approach which is being used over here. Both iterative and the incremental processes or practices is what we are using up in this one.
So, Scrum is a very, very popular development process which is being implemented and people are using it, people are referring to that and they are holding up to that particular value as such. Also, Scrum significantly increases the overall efficiency and makes the release cycles quite shorter. That's a kind of ultimate goal which Agile sets up that once you are done with the Agile, once you are finished with the Agile or the Scrum process implementation, you are going to get an efficient and a shorter release cycles. That's the ultimate thing here. Now, this was the biggest concern with the waterfall model because the waterfall model was following a very lengthy release cycles like a period of, you know, like three months, four months, two months.
That's a very, very lengthy process. The release cycles which was being promoted are being used by the waterfall model. But down the line with the Scrum, it actually got reduced to shorter release cycles and that too also quite efficient release cycles as such here. Now, the next one, the different roles which is available there because earlier we were having the traditional looks like project managers, business analysts, the developers. Now, we have actually got a little bit different roles. For example, we have a Scrum Master. Now, Scrum Master is a kind of a head equivalent to the Project Manager.
Now, he's responsible for setting up the team meetings, the spring meetings, and he's responsible for making sure that there is no obstacles, there is no issues in the development process. If any issues are coming up, like if there is any kind of new infrastructure needed or some new resources are required, all those things will be taken care by the Scrum Master. We also have a Product Owner which is like working on as a Product Knowledge. He perks on the Product Backlog and prioritizes the backlog that how this backlog is needed to work is going to, you know, achieve it up over here.
We also have a Scrum Team which actually manages the overall sprint and the sprint cycle. So, Scrum Team is having like all these developers, Scrum Masters, Product Owners, the QA Professionals, all of them are actually being available like they are part of the Scrum Team as such. So, these are the three different roles which is available which is responsible for implementation of Scrum Process and a smooth implementation of Scrum Process as such. Now, this is a kind of a diagram, like an interactive way. So, as you can see, like the Product Owner actually like process this Product Backlog items over here.
Now, this is something that it performs a proper planning, like a sprint planning is being done. So, it force costs the work to the development team and perform a planning with them that how we wanted to do the development. Now, after the scheduling of the things, after prioritizing the things, they actually come up with a sprint backlog. So, this is something which is quite formatted, something which is quite analyzed and prioritized there. Now, after this sprint backlog is being prepared, the whole iterations will start coming up like, for example, if it's a sprint 1, sprint 2, sprint 3.
So, this is something which is, you know, going to work it off there and, you know, it's going to be a cheat-up over here in this case, in this particular stuff here. So, that's the kind of implementations we will be doing and we will be achieving it up over here. So, that's the kind of implementations which we are going to consider it up over here in this one. Now, after the sprint is done, I mean, we will be definitely having the daily scrums which is available there.
So, this daily scrums, we are just trying to make sure that we have a proper review which is being done. So, that's something which we set it up over here in this case that, yes, this is the kind of implementation we wanted. If there is any kind of issues, we can discuss about that. We can talk about that. But, that's a kind of high level of implementation and setup which we are trying to do here. And, once the sprint is done, we can just simply go ahead with the next sprint and this whole process simply keeps on going again and again, again and again over here.
So, that's our implementation. That's a very high level of implementation which we really perform and we execute it up over here. So, this is kind of a scrum, like an overall architecture of the scrum process which we implement and we get it up over here in this case. Now, the next one is the Kanban process. Now, Kanban process is also one of the ones which is there in the agile development. It's a part of the agile development. Some development teams really focuses on like how the Kanban processes can be implemented.
Now, when we are going for the Kanban process here, so, it's something which is taking care of like the implementations like the setup here. So, when you process, when you work with the Kanban over here, so, it's something which was being designed initially by the Toyota developers. So, it's not, you know, like being launched or being implemented by any development team, but in fact, it was being generated by the manufacturing team, that too also by the engineers of Toyota. Now, their idea about this one is just to make note of the things that how the things can be done in an effective way.
That was the primary goal which they were trying to do. They were trying to implement. So, they were looking forward that how exactly they can go for a better efficiency. That was the idea which they were having into their mind. So, understanding that idea, understanding that requirement, so, they come up with this kind of particular framework over here, so, that they wanted to see like how the overall approach, like how the different achievements they can go and they can implement, so, that they will be able to get the desired output as such.
So, it actually consists of a Kanban board, like, you know, which was being prepared, so that we can get the better efficiency and the proper output here. Now, let's see how exactly it goes. So, if you can see here that we have a particular Kanban board which is available here, like we have a to-do list which is available, and one is like in progress, and the last one is done there. So, you know, if there is any kind of item which you are trying to implement, so, you will be having that particular item into the to-do list.
You are going for that implementation. If that implementation is done, you are going to move those items back into the in progress, and after that particular work is done, so, you will be going for the done or the completed part. That, yes, the things are completed over here. So, that's a way, that's a process which you are following. In general, so, you can actually put some items in the to-do list, like, yes, this is the new list which is available there. Then, some items, you will be moving it up into the in progress that, yes, these are the different items which you want to work it off or which you are working at this moment of time.
And then, there will be some items which is completely, which is done, which is implemented over here in this case. So, that's a kind of a process. That's a kind of implementation which you are trying to do. And, corresponding to that, or depending on that, you will be able to get the desired output here. So, this is the different processes which we are talking about over here in this case. Now, if we talk about the difference between the Scrum and Kanban, so, let's talk about this thing one by one.
The very first one is the roles and responsibility. Now, when we talk about the Scrum, so, what happens is that each team member has a predefined role, like, that's something which is available that what it needs to do, what it needs to perform over here. So, that's a kind of predefined role which is available there, like, Scrum Master, Product Owner, or the Scrum Team. So, those kind of details are already available there. On the other hand, when we talk about Kanban, so, we don't need, or there is no separate roles which is available there.
So, there is no separate different profiles which we are talking about over there in that sense. When we talk about the delivery timeline, so, Scrum is something which is like delivering and the deliveries are planned as a Sprint. So, that's something which is being planned prior and that too also in the Sprints, each and every work should be handled, should be performed. So, we are expected to complete all the activities, all the work in the specific or the defined Sprints as such there. Then, when we talk about the Kanban, so, the products are continuously implemented like delivered.
So, there is no specific time in which you will be delivering it up there. So, what you are trying to do is that you are just trying to implement and you are just trying to deliver the things on a specific time duration. So, that's what you are trying to do. You are trying to handle there. During the Sprint, changing requirements are strongly discouraged because all the planning has already been done. So, it's not going to consider to pick any kind of new requirements. Whereas, in case of the Kanban, the changing requirements can be easily handled up there.
So, that's kind of ad hoc requirements also you can pick it up there and that's the kind of advantage which we can get from the Kanban process. If we talk about from the best implementation, so, Scrum is something which is best for teams whose priorities may not change over the period of time. I mean, they are strict with their priorities. They are having all the processes defined properly there. So, for them, Scrum is quite perfect and for those processes where or for those teams, the priorities are changing depending on the requirements.
So, for them, the Kanban process is something which is quite perfect because they can afford to attend the changing requirements and they can go for that kind of implementations. If we talk about the best implementations, you know, this is the kind of a difference which we have got here. And, you know, it's an ultimate thing because that's a kind of understanding which we wanted to do also, which we wanted to take it up over here. Now, last one is the metrics. So, in case of Scrum, we talk about the metrics as velocity.
In case of Kanban, it's like the cycle time throughput, which is being considered as a metrics over here in this one.