← Previous lessonFree lesson 3 of 3 · lesson 3 of 24

Unlock all 24 lessons of DevOps FundamentalsFull course ₹40,000 · paid

Price & syllabus
Free lesson · 24 min · no payment

Agile Values, Principles, Waterfall Comparison and DevOps Careers

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 2”

What will you learn in this free DevOps Fundamentals lesson?

Lists the Agile values and principles, such as customer satisfaction, welcoming change and frequent delivery. Compares agile with the waterfall model on customer interaction and feature prioritization, then covers the DevOps job market and salary trends before summarizing the week.

  • The four Agile values
  • Agile principles like frequent delivery and daily collaboration
  • Agile versus waterfall on change and prioritization
  • DevOps job market and salary trends

What comes after lesson 3?

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 certain Agile values here. Now there are certain values which is available like for the Agile which we are talking about over here so that we can understand that how exactly it goes. For example, the first one is like the individuals and interactions, the working software, the customer collaboration, responding to the change. So these are some couple of values which is available there. Now if we talk about the Agile principles, now there are like a lot of Agile principles which is available which is actually helping us to implement the Agile best practices and the implementation and the setup here. So when we talk about this Agile principles, so the first one is about the customer satisfaction. So customer satisfaction is one of the most important thing which is available there.

Second one is like welcoming the changing requirements. We are expected to handle the changing requirements. So that also like something which is considered that yes, we want to go for the changing requirements as such. That's also like we are taking care of here. Deliver frequently. That's very important because if you are going to or if you wanted to have your deliveries deliver faster, then definitely that's the implementation you wanted to attain. Collaborate daily. So the collaboration is also something which we are expected, which we are trying to do so that we will be able to see like how the things are going to be handled and going to be achieved over here.

Motivate individuals. So motivation is also a good thing because we really wanted the people to perform in a better way. So if we provide the proper motivation to the team, so they will also be able to provide the performance in a better way. So that's an expected thing to be considered. Face-to-face conversation is also required. So if you interact with the customers and have a proper communication or the conversation, so it helps us to understand the requirements in a better way that what exactly we are trying to achieve with this overall requirements.

So that's what we are trying to do. So that's what we are trying to do. We are trying to learn it up over here. The measure of projects, project measurements is what we are trying to do. Promote the stable development. That's also like something which we are promoting that how this implementations can be done. Because continuous attention is also required that we are going to give the continuous attention to the particular teams that how this is going to work it out there. Simplicity is important to understand that the things can be achieved in a very simple way. So we don't want to perform the things in a particular complex manner.

So that's something which we are trying to achieve. We are trying to handle it up over here that yes, the automation or the implementations which we are trying to do so that can be done in such a way that it can be achieved in a very simple, straightforward process altogether. Self-organization team is something which is very important. So you don't have to organize anything. So if you are going to get a self-organizing team, that would be always be a better approach because you don't have to put that many efforts as such in order to achieve this kind of stuff here.

So that's why it's recommended that we have the self-organizing teams which can organize themselves according to the requirements, according to the implementations as such. And continuous improvements is also one of the aspects which we are trying to look upon so that we don't have to stuck with the old things. And whenever the new requirements are there, we can take care of that. We can learn about that particular process. So these are the different processes which we are talking about, which really helps us to consider like how the things can be done in an effective way.

Okay. Now, the next thing which we have over here is about the waterfall and versus the agile. Now, waterfall is something which is considered as one of the legacy architectures for the software development and agile is a new process. That's a very beginning difference which we have over here because people have somehow stopped using the particular waterfall model because it's like something which is causing a lot of troubles, a lot of issues as such. So it was having some fundamental issues with the particular software, with the process itself.

And that's why people have started working on the new automations. And, you know, in that case, they have started working with the agile methodology and the agile automation altogether there. So that's a kind of implementation which they have started, which they have worked it off over here in this case. Now, when we talk about the waterfall model over here, so it's something which is dividing the steps in a very sequential manner, like, you know, you are proceeding or you are performing the kind of tasks in a particular very sequential manner over here in this case, step by step approach.

So if one step is done, then only you will be going up with the next phase, next step here. That's the process. That's the way that how we handle the waterfall model over here in this one. But when we talk about the agile model, it's something which is quite iterative in approach, which means like rather than doing the sequential things, which we are going to go in the iterative approach over here. That's the implementation, which we wanted to handle it up over here in this one.

Now, it's very important because we are not performing the things in a sequential manner, but we are trying to perform the things in a very iterative approach so that we can get the desired output as such here. So that's what we are trying to handle up over here. Waterfall model is quite rigid. It's something which is quite difficult to handle, quite difficult to change also. Whereas when we talk about the agile, it gives in a lot of flexibility, a lot of things we can implement, we can achieve with the help of the agile here.

And it's very easy to extend it to any level also. Like if you feel that you want to extend it to a different level, so that's also like something you can do. You can achieve it with the help of this particular setup here. So depending on the requirements, depending on the situation to situation, you can decide that how these things you can handle and you can perform it up over here in this case. Now, when it comes to the waterfall model, so it actually involves like a large team, large development teams will be available there.

But agile is something which is promoting like teams of like five to seven members only. So that's the maximum which is being supported or which is being implemented or suggested by the agile. So waterfall requires customers only at certain phase because at the end of the whole phase is only the customer interaction is there. But agile is all about having more and more interaction with the customers because that's the reason why we are going for the agile. Because in waterfall model, the customer interaction is very less.

And that's why we are trying to see like how the new things can be done and we can go for the maximum customer interaction over here. So that's why we are going for the agile process, agile mechanism as such over here in this case. There is no prioritization of features which is being done in waterfall model. But in agile, the features are prioritized. There is a proper planning which is done so that only the important features can be implemented first and then the non-important features can be handled up.

So this is a kind of a process or the implementation which we are taking up in case of agile. Waterfall models responds slowly to the changing requirements. That's something which is a process there. But agile is something which can handle the changing requirements quite quickly and quite faster here. Waterfall model feedback takes a lot of time. We are not getting the instant feedback. But when it comes to the agile process, we are almost getting an instant feedback. Because once the things are done, we are getting an immediate feedback which really helps us to get the things done in a better way.

So this instant feedback is very important because then only we will be able to know like how the things are being done and how we are getting the particular things or how we are performing the processes all together in a better way. So this is the primary difference which we have got between the waterfall model and agile model here, which really helps us to understand that how the main difference which we have got over here in this case. Now the next one is what is the difference between the SDLC and the agile DevOps over here.

Now SDLC is actually meant for the software development lifecycle. That's something which we use for the software development lifecycle over here in this one. Now when we talk about the software development lifecycle, so there we are talking about like how the development can be done in a better way. So, you know, let's say like the team composition, that's the first parameter of comparison. So when we talk about the team comparison over here, the team composition over here in this one. So the first one is like agile.

So in agile, the development, the QA and potato owner, these are the different team members which is available there. When we talk about the DevOps, we have the development and the operations teams which is available over here. Second comparison is about the goals. So the goal of the agile is to bring the development, QA and the potato owner teams together closer over here. So that's a kind of a goal which the agile is looking forward. Whereas in DevOps, DevOps is talking about the collaboration of dev and ops, like to have them collaborative together over here.

So that's something which we are promoting when we talk about the DevOps as such here. Secondly, if we talk about the duration. So in case of the agile, we have a duration of two to four weeks. That's the kind of sprints which is being followed. But when we talk about the agile process, so it's a little bit something which takes a little bit more time. And, you know, it's something which is talking about the things in a very continuous manner, like a continuous process is there.

So there's a difference. There is a way or kind of a difference which we get over here in this case when we talk about this process. Now feedback, if we talk about, we compare between Agile and the DevOps over here. So when we talk about the feedback, so in case of Agile, it's something which is provided by the customers and the product owners. So they are basically providing us or, you know, giving us this particular features or this particular requirements here. So the feedback is also being provided by the same customers and they actually share that if the application or the features are working as expected or not. So that's the information or the piece of information which is being provided by the customers.

Then in DevOps, we are talking about like how the internal feedbacks or the processes between the development and operations can be handled up, like how these teams are taking care of that feedback. So that also like something which we can take care of the DevOps here. So in case of Agile, the feedback is only being provided by the external customers. But in case of DevOps, the internal teams can also provide the feedbacks here. If we talk about the tools, so JIT, Jira, Lean, these are the different tools which is there in the Agile.

If we talk about DevOps, if we talk about DevOps, Docker, Jenkins, Kubernetes, Ansible, Puppet, ELK, these all different tools are like available in case of the DevOps. So that's the nature of the software which is available like where we can talk about how the processes is being done and is being handled up here. Now when we talk about the collaboration, now collaboration when we talk about here, so in the collaboration, we are trying to see like how the implementations can be done. Now the whole idea of DevOps is actually that development operations and you know other functions must be done, must be performed closely, like you know a proper collaboration should be done here.

So that's the ultimate goal, that's the ultimate goal, that's the primary goal which we are trying to achieve. Also, it's all about like breaking down the organization silos in order to improve the communication between the teams. Now if we have a bigger teams, it's going to be a problem because you know the communication will be difficult. But if you have a smaller teams, the individual teams and in that particular case, you know the performance or the communication, definitely it's going to be better here. And that's something which is being promoted by the agile also that you know if you want to have a better collaboration, then you have to break down this specific silos and get the proper output defined here.

Also, it helps us to perform a better decision making, like you know considering that we wanted to get the better output, so the decision making should also be done in a better way. It also helps teams to improve their skills by collaborating with each other, so that's also like something which we are trying to implement, so that we can get the desired output. So that collaboration is also what we are trying to do, we are trying to handle up over here. So it helps us to see like how the skills can be improved, so that we don't have to collaborate with each other as such.

Now when we talk about the DevOps implementation, now this is a very high level of implementation which is available there. For example, we talk about the orchestration tool here. Now the orchestration tool can be integrated with the CI, with the CD part here. So from the continuous integration perspective, we are taking care of like how the build pipelines can be designed, can be developed. From the CD perspective, we are talking about like how the continuous development or the release pipelines can be handled up there. That also we are trying to do.

And when we are implementing this overall pipeline, so we have different stages like the source stage, checking out the source code, performing the build, running the test cases, deployment to a development environment or a test environment, running the business test cases, performing the deployment to the production environment, and then the production validation. So these are the different stages which is available there, which is basically giving us the end results like how the things can be done in an effective way, and we can get the end results here.

And of course, on top of that, we have the continuous monitoring, feedback, all those standard practices are also available there, which is basically helping us to go and get the desired output. So this is what we talk about as in standard DevOps implementation, which is taking care of the things like how the automations can be done, and we can take care of the different functionalities and the automations as such here. So this is the standard way of the implementation of DevOps. So certain processes we do involve, like when we talk about that, let's say I wanted to implement DevOps.

So what are the standard practices which is there, the standard processes that every person who wanted to go for the implementation of DevOps, they follows and they implements. The very first one is continuous integration. Now, continuous integration is something in which we are talking about that how continuously we are going to develop, we are going to work on our particular features, the bug fixes, and the code modifications to the source code, to the code base here. So that's the kind of a work which we are trying to do.

We are trying to implement it up in the continuous integration here. Secondly, we have a continuous deployment process. Now, continuous deployment is something where we are talking about that how the things done can be done in a better way, like something in which we are talking about how the different ways in which we can deliver the source code. We also have the continuous delivery which is taking care of the deployment aspect. But there is a difference between the continuous delivery and the deployment here. Now, continuous deployment is something which is an automated process.

I mean, it's a kind of straightforward without any kind of human interaction. The deployment is something which is being done in continuous deployment. Now, if you want to put some manual checks, some manual validation, so in that case, we can go for the continuous delivery. So, continuous delivery is something which is similar to the deployment. But, of course, in case of continuous delivery, the deployment aspect is something which is being taken manually. So, that if there is any kind of scope of validations or some checks, you can do that and then only you can go for the deployment on that particular stuff.

So, that's a kind of difference which we have got over here. And ultimately, otherwise, the end result is same that we are looking forward for the deployment and that too also automatically. But the way of doing the things is a little bit different over here in this one. Then, we have the continuous feedback. Now, continuous feedback is also an important mechanism because usually in the legacy world, the developers were not having the instant feedback. They were depending on the QA professionals and it was almost taking a couple of weeks or months to actually get the feedback.

And then only they can improve or they can fix the code base there. So, this was one of the biggest problems which was there in the legacy architecture. And with the new agile architecture, we are promoting like we have some automations like CICD automations which is available, which can give you an instant feedback. And you don't have to wait for weeks or the month's time duration in order to get the feedback. Immediately, in a couple of hours, we will be able to get the feedback as such there.

So, that's a kind of difference which we have got in the DevOps world from the feedback perspective. Now, what is the automation in DevOps? Now, automation is a very generic terminology. It's not even like that DevOps have introduced automation. It was a natural direction in which the industry, the organizations were going on. Now, automation really helps us to perform the things faster. If we talk about the complete SGLC cycle, we don't want to do the things in a very slow and a manual manner. So, what we wanted to do is that we wanted to perform these things in a faster phase.

So, that's why we are looking forward to how the software development lifecycle, the SDLC cycle, we can use, we can go ahead so that we can keep it faster, keep up with the speed of the DevOps. So, you know, if you wanted to do the things in a faster phase, so that's where the automation is needed. Now, automation can also be anything like maybe a code development, middleware configuration, database networking changes, deployment automations, the performance testing, the test automation. It can be anything around the particular SDLC cycle.

So, whatever you feel like you want to get rid of the manual interactions, you can go for the standard automation and implement the things. And that's what we are trying to do. Now, when we are talking about the automation as such there, so it actually helps us to save the time and efforts of the developers, of the testers and the operations professionals. So, as you don't waste your time and efforts as such on this one. So, that's a real thing which we are trying to do, which we are trying to achieve it up over here so that we don't lose the efforts and time as such here.

Also, automation is something which helps us to remove the manual errors like we don't really want to do any kind of manual interactions. So, for that, we are looking forward at how exactly the automation can actually help us to remove those things and we can get rid of all the manual errors, all the manual issues as such here. So, in order to go for the better efficiency and quality of the delivery, we are going for the automation and implementation of the automations as such there. Now, what are the different DevOps rules and responsibilities which we get over here?

So, you should be a proper system administrator like someone who is having a proper understanding about the system, about the processes there. You should be having a proper technical background like a, you know, background should be available there which is having a proper technical understanding. A scripting guru, having a proper scripting understanding, having a proper hands-on on the tools like Chef, Puppet, Ansible like a configuration management tool so that you can use this tool. Managing the configurations or the deploys. People skills is also equally important so that you can actually define like how the people are going on, like how this implementation is there. So people skill is also important. Customer service is also there like something which you can help or you can get along to see like how the implementations can be achieved, can be considered there. Cloud experience is also required so that if we wanted to do some kind of automation on cloud so that can also come in handy.

Tools like Jenkins, Maven, and Build Automation. These are also like the different standards which we are looking forward, which we are trying to achieve it up over here in this case. So that's also the standards which we are trying to do. We are trying to perform it up here. And then Git, Subversion, CVS, Visual Studio. So the version control system understanding is also must for a proper DevOps understanding and the role over here. And at last we have the monitoring tools like the tools understanding so that if at all we wanted to go for implementation of monitoring tools, we should be able to do that with the help of these different tools as such there.

So these are the different components or the different ways in which we can handle and we can see like how the different automations can be done and we can take care of the stuff as such there. So that's the ultimate way of like how we can handle these roles and responsibilities all together in this one, right? So these are the different roles and responsibilities which we have to take care of or we have to talk about when we, you know, work it off onto as a DevOps engineer or we wanted to work or we wanted to set up it as a DevOps professional.

So let's talk about the DevOps job market here. Now, when we talk about the market trends, now DevOps is something which is very popular to like something which is having a very, very popular trends which is going on there. Now, there are some popular trends which is available. For example, there are very few people which is having the understanding of DevOps. So ultimately, a lot of professionals are trying to go towards the DevOps and there is a huge requirement also from the organization perspective. So almost every organization have now understood the benefits of DevOps and they wanted to set up the DevOps implementation.

So that's why they are hiring the people, the professionals was actually helping them to go ahead and implement these kind of standards. So DevOps professionals are quite in demand right now. And if you talk about the market trends, like if you talk about the packages, the job opportunities, we have a lot of job opportunities which is coming up both in the product and the service-based industry. So there are like some profiles in which you may have to work it on certain tools. There are some DevOps profiles in that you are doing something completely opposite to the, you know, another one there.

So it's a very hybrid job and depending on organization to organization, it could be a possibility that this may change, this may vary and you may not be able to know or like you may not be able to get those particular things there. So it's a very hard and quite hybrid job which is available at this moment of time. Friends are also quite good there. People are getting very good packages in terms of the DevOps engineer because you can understand that there are very few professionals which is going to be there in an organization. So it's not like you are having like 50 to 100 DevOps engineer.

So, you know, as compared to the developers or the other profiles, definitely as a DevOps engineer, you are going to get a good amount of particular packages or the financial aid as such. Now, let's summarize this one. Now, if we're trying to summarize over here. So in this week, we pretty much talked about the DevOps evolution, introduction, benefits, challenges. We have also talked about the DevOps tool chain, the best practices there. We have talked about the agile methodology, principles, values. And of course, towards the end, we talked about the job market, the salary trends and the automation.

So these are the different topics which we have understood over here so that we can see like how these things can be done and we can handle up these particular stuff here. So pretty much this is what we have in this week. I hope you like it. Thank you. See you in next week.

Want the rest of DevOps Fundamentals?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full DevOps Fundamentals course

The remaining 21 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full DevOps Fundamentals course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.