Agile Scrum Full Course In 4 Hours | Agile Scrum Master Training | Agile Training Video |Simplilearn

Hello everyone, welcome to this complete Agilent Scrum

course

just learn in this session. We will tell you everything you need to know to become familiar with the concepts of Scrum and Agile in less than 4

hours

. Our instructors Chandra Rahul and Ishan will cover the topics. like

scrum

agile

agile

project management agile user stories scale agile framework how agile waterfall

scrum

and kanban differ from each other and many more. We will also guide you on how to become a scrum

master

. We will learn all this in less than 4

hours

, so without further ado, let's get started, but before we start, make sure you are subscribed to our YouTube channel and don't forget to click the bell icon so you never miss a SimplyLearn update.

Welcome to Simply Learn Agile Tutorial I Am. cmr chandra sir certified agile professional consultant and trainer scrub

master

pmp master practitioner itl4 managing cobit 5 professional and devops as part of this

video

tutorial we are going to understand what is agile the basic details that one should know about agile to understand this better let us Look for a moment in late 90s what was happening with software development forms then they used to follow waterfall methodologies so there used to be expressions like we said we have a problem so, What happened? So our client wants a new feature for the software we already have.

Halfway through creating the software, we can't add the feature, so what does it mean? There is a scenario where the change is requested, so why might the change be because certain features are added, certain features are removed, and certain things are changed, given what is wrong with that? Why can't we make the change? The point here is not about making the change itself, it's about the effort, plus it costs money in terms of what the effort is and then the extent that you're going to change at the same time. More efforts also need to be made, which will delay the project.

So is it okay now? In the nineties it was good. Today is fine. A big question mark. So why is it not okay? So that I understand it very clearly. waterfall methodology for development is a problem with waterfall methodology, so the answer is no, if it is the current scenario, the answer would be yes, if it is the 90s, the answer would be no, then, What changed in these 20 or 15 years the dynamics of the market changed, consumer behavior changed, so if you look at someone who is using any product, it can be a software product or a hardware product, like if your phone mobile or a television or any mobile application or application used in your systems, the update of the The new features and functionalities are improved more and more and the consumer wants them more and more and you have less time to respond, that is one thing and the Second is that there is a lot of competition, if you don't respond quickly, the competition will take over, so you should do it. sustain and grow it is very essential that you understand this dynamic and you have to respond quickly, which was a little difficult when it comes to tackling what is called the waterfall model.

Now how do we approach this? So what is the waterfall model all about? Because? It is difficult for us, so the methodology where the waterfall model is used involves teams following a series of steps and only moving forward after completing the previous steps, so there is a waiting time, so until the above steps are completed only then can I move on to the next. so it is somewhat slower, it would take some duration, so it is best used in scenarios where the teams are small and the project is expected to progress in a predictable manner, so predictability is very important when we follow the predictability of the waterfall methodology, the variation should be as little as possible, so what is the predictability we talk about while creating this product?

As a result, it emerges if it takes six months, one year, two years, three years, okay, this is what the product would look like. The predictability of what the product will look like. It would look like that particular outcome would come, so when will it happen? Is it okay if I bring back that result after two years? Alright? So if everything is fine that way, without much less, without any variation as such, very less variations, then it is Okay, because of the following waterfall model, what is that methodology? What is that flow? We need to understand that requirements gathering and documentation is the first thing that used to happen, which is also true in agile methodologies, but the main difference here is requirements gathering. and the documentation is done in detail, it is comprehensive now, once it is approved, only then it is more about the design, now it is based on the requirements that are collected, which is completely comprehensive, then the design will be based on the consideration of the process, products, people. the environment then design happens which again is detailed design now once implementation starts if you find any deviation then correction needs to be made as design is detailed the possibility of deviation is least possible, but the challenge arises when the dynamics in the market, when the customer dynamics change, the customer requests a change, you may have to make the change now, when you want to make the change, you may have to make the change only after understanding What would be the impact of this change on the entire process.

The result you are going to create is very complete so it consumes extra time and effort, so it may be a scenario where the scope of work is also reduced, even after that this exercise has to be done which will delay the project, so it was good, when things were done in this model, measures were taken to make changes, it was good because consumer behavior, as I mentioned, there is also a lot of waiting time for consumers, so there was less competition, but that's how it is today. No, I need to go faster, so what are the disadvantages that have just emerged for the consumers or for the organization who actually follow waterfall methodologies in the current scenario?

What could those be? Making changes would be difficult, as I mentioned above, then. it doesn't focus on value from the end user's customer perspective, so today I think we talk more and more about creating value from the customer's perspective and the time it takes for the consumer to realize the value, how much longer does it take? . realization of values ​​by the consumer is delayed there is a delay in terms of making the impression of your product better in the mind of the consumer so the competition will take over so your existence will be in greater threat so that the testing phase is delayed until most of the project is completed Because you have to follow step by step, wait for things to be completed and then testing is done, then measuring progress within the stages is difficult So why is it difficult to measure progress within the stages because the deliverables or metrics that are defined are defined to measure? at a milestone and at the end of the phase to understand if everything is delivered as part of it, now let's see how agile will help us address these disadvantages mentioned in which fall model, so what is agile, the basic meaning of agile.

It is moving faster, being flexible, responding to change, etc. but to achieve this there are many methodologies, now there is something called agile manifesto about 12 principles of agility that we need to understand, so following this and achieving this can only help us become like children. So in 2001 Agile was introduced, that's where the term agile came into the picture, where people started realizing what agile is and why we should adopt those agile methodologies. While it was introduced, an agile manifesto was also published which is a set of principles used in project management. and software development, so basically there are four points that we must understand very correctly and very clearly so that we can understand what is agile and what is correct, it allows the team to deliver value to its customers with ease, so the agile team delivers work in a short time. but usable increments then evaluation of requirements plans and results is carried out continuously, this allows teams to respond to changes quickly.

Now change was one of the scenarios we were talking about. Now responding to change quickly is one of the disadvantages we talked about and here. is addressed is considered to address that is very important now that we respond to change quickly it is not that I just responded quickly but I did not address that problem or that scenario it is very essential to address that scenario also effectively and efficiently So now agile is a concept, so it has a detailed manifesto based on which all agile methodologies are created. So what is this agile manifesto about? So, it was created.

It was created during February 2001, so it details the values ​​and principles of agile processes that says there are some values ​​that are mentioned on the left and they have more weight compared to the one on the right now when we say this, for For example, let's take individuals and interactions over processes and tools one by one. So are we saying we don't value process and tools? That is not the case. Now let's see what were the typical problems or challenges that anyone would have expressed regarding the processes, so the delay may be bureaucracy and they may not have flexibility to move. faster, so basically there are delays due to approval, which is not happening due to processes now, how do we address this?

Can I kill the process itself? The answer is no because in the absence of tools and processes none of the things that we can easily do can exist, so it should be there, the process and tools should be there in the way it should be defined, it should also ensure that there are individuals and interactions encouraged to have their individuals and interactions while you have the process and the tools, so the next thing is work products or complete documentation for when we say complete documentation, as I mentioned in the waterfall methodology during the collection of requirements during the design, there is a detailed documentation that is made in a way that requires a lot of efforts to create it now while delivering the challenge that everyone faced was the upcoming change. configure and make changes to these documentations, which is an extra effort now, if we have working products, if I have a bigger product in that module, I keep creating each little little module and start integrating it into the base model now.

I only focus on the documentation for that particular piece of model work that I am going to create in the next iterations, so my changes to the documentation are minor and also the way I am doing the documentation is that initially I would have a complete skeleton of all the product I'm going to create the roadmap and on that I'm going to make the detailed documentation for that just for that work piece instead of the

full

product itself, then this documentation of the work piece I'm going to create custom that I create the pieces of work that I'm I also get feedback because I'm interacting with the users, the consumers, the end users, so I get the feedback.

I keep making the changes quickly and then the documentation will consequently become the little pieces of documentation that happen with those small little working models that are created and consolidated over a period of time, when the product is finished you have a complete documentation , the project has complete documentation, so it saves a lot of time, so documentation is important, but the way we achieve documentation is one by one. The next thing that is not done in one go is client collaboration or contract negotiation, so any commitment, relationship or business can happen in the absence of a contract.

The answer is no, there should be a contract now, how should this contract be when we want to follow an agile system. should enable customer collaboration, why are we collaborating to understand what is required to understand what customer needs are being met right now? This requires a lot of flexibility in the contract itself so that the business area is an area that is affected and there should be guidelines for that also in the contract so that during the collaboration during the change during the effort that the client puts in as well be informed what the change is going to occur in commercial and time terms and everything so that it is documented in the contract so that there is no confusion when responding to the change or following a plan.

Now we can't have a rigid plan as we were talking about the waterfall methodology so we need to go like this only as per the changes of scenarios so we may need to change their directions and move forward. faster, so responding to change requires specific flexibility that is required in the plan, so I don't have a plan that is very rigid and that provides some flexibility,This is how I create my plan to be able to move. or respond to specific scenarios that are changing, so this is called an agile manifesto and this agile manifesto has 12 principles associated with it.

Now keeping this agile manifesto in 12 principles, all agile methodologies have created their own approaches and frameworks. Now let's see what Are those 12 principles the agile principles? So agile principles. These are some of the principles that must be followed to streamline processes. The first principle is customer satisfaction, so it is necessary to satisfy the customer by early and fast delivery of the product. Now someone. Who is hungry? If you give them water or food immediately. A piece of bread. At least there is some satisfaction. There is some understanding that I already got what I need. So the energy has returned, so it is very necessary to make sure I see things one way.

The customer perspective and the customer is satisfied, so customer satisfaction is not the result of the survey. What I do, it's about how I deal with the consumer, what's the impact on the perceptions that I'm building with the consumer and what do I know about my customer? Really understand the pulse of my customer How partnered am I How close am I How am I collaborating with the customer Which will help you understand how satisfied your customer is It is very essential to consider customer satisfaction and the second principle would be a welcome change, so that changing needs must be addressed even in the later stages of the development process so that change can occur at any time.

It shouldn't become a challenge, so there should be flexibility in the design itself, which it will bring with it, and that's the reason why I think when you move faster it doesn't mean that you eliminate or just keep introducing the defects and You move faster, no. that is not allowed, so whenever there is a change in feature, whenever there is a change in some specific functionality of the product, that should be easier, whatever methodology I follow, that should help me in terms of adaptation , so you should accept the changes, okay. that change is no longer a challenge for me, so principle three deliver frequently, so make sure the software is delivered frequently, focusing on shorter time scales, as I mentioned while talking about the point of the manifesto, like I keep creating a smaller piece of product modules, so I keep putting in the base model and integrating them and ultimately once all the features are integrated, we have a product with all the features and functionality, for so this should happen more frequently, so the release of those that work should happen more frequently and more repeatedly. for the customer to see the ps that work and experiment and give feedback, such rapid changes in manufacturing workpieces that will be easier than working together, so when I work together it is very essential that developers and people business people work together throughout the

course

of the project, which means involvement of customers, involvement of suppliers, involvement of their own team, everyone must work together, each must understand each other's perspective, if not there is a proper understanding of everyone's perspective, it is quite obvious what was expected, what was delivered. they do not match, so there must be a correct understanding, to have that correct understanding, one must work together, collaborate, so they must speak expressly, which is very important, so consumers must provide feedback regularly, so Similarly, the organization that is doing the project should also continue to provide feedback to the suppliers to make the necessary changes and once they work together in the unizona, I think that would help in terms of getting the results in the necessary way, which would help the customer to get the team motivated by value, so projects should be built around motivated people and they should be trusted to do the job means when will the team be motivated when you recognize the work what they are doing when you see the work what they are doing the results are experienced and then feedback is given there is an opportunity to learn and contribute their contribution is recognized only then the team is motivated when there is a motivated team when the team feels that there is someone they can look up to it is quite It is obvious that the team will also generate certain set of innovations in their mind by giving their feedback and also involving themselves in terms of getting the necessary results, so it is always essential to ensure that the team involved in creating the products is always motivated, so I think when we say team, conflict also arises, there can be a clash between different thoughts and preferences, so one cannot simply avoid being a manager, he or she cannot avoid it, he or she must get involved, situate the team , solve them, put things in the right direction, so proper leadership interpersonal skills are very important in the upcoming face-to-face interactions. which helps in terms of the most efficient means of communication, which helps in terms of providing adequate clarity in terms of what is required, so I send an email, I hope the person does it, that is not the case about which we are discussing.

There are more and more interactions that need to happen face to face for each one to understand what needs to be done and there is quick feedback that can happen when that particular conversation of interactions continues to happen so that one can understand other perspective views and then the running software. It's mainly about the product you're talking about, which has to arrive regularly, so that more and more pieces of work as they arrive, the customer can give feedback based on their experience with this piece of work, rather than just imagine something and then give your opinion so it shouldn't seem like a hypothesis or something that's in dreamland, so I said something to the person who listened, visualize something else, it shouldn't end up that way, instead From that, deliver the work piece, expect the consumer, the user, to give feedback so that it helps in terms of creating that particular product that is ultimately usable and that is going to create value for consumers, so What follows is a steady pace, agile process that promotes sustainable development, so you shouldn't do it.

I did it and slept. I did it and then. I'm expecting something else, no, there should be frequent deliveries, which is happening, so there should be a constant moment from left to right, from start to finish, so that the deliveries that are expected continue to happen so that consumers or users They realize their value. it should be a constant pace the speed that should be adopted then the agility of good design can be improved by focusing on technical excellence and good design so when we say technical excellence and good design it is very essential to understand what the product is.

It provided information about what technology is being used, information about the processes, capabilities, skills, so all of this comes together when people sit together and focus on creating that product or service, so they put in the effort to design it. appropriately to fit the purpose. So since things move step by step in terms of creating a piece of work, the detailed design of that small piece of work would happen, which can also happen faster and since these go and fit into the architecture, which It is basically a type of open architecture scenarios. that you're talking about, then all those modules that you create you keep connecting them to design that little piece that is faster, so instead of designing the whole system in detail, you're just creating the little null pieces and fitting into that architecture that is open and pluggable so that it also provides flexibility and design changes will be easier if it does not work and agility helps achieve that simplicity, the amount of work that is not done should be minimized, that is, when Saying that simplicity does not means less right, so the right number of tasks, the minimum number of tasks that need to be done, and above all, I think all the activities and processes that do not add value would be eliminated.

They must be removed, so the more optimized, the simpler. The terms of managing things are always good so that only what needs to be done is done, so that it is very clearly visible and there is clarity in self-organization, so when we say self-organized teams that are not capable of everything, but when look a team has a whole each one has different skills many skills not one or two skills many skills that complement each other so they come together discuss together they focus on the architecture and design requirements and address it together so that the team Also owning the property is one thing when it comes to the image when we say team, here since the team is actually taking that ownership and organizing to achieve the results, the products that are required, then obviously the results will happen accordingly. the way they are.

It is necessary and they will be responsible as a team, so they cannot have a blame scenario where because of one or two members it is happening, they should collaborate better, they should self-organize, what should happen, the next thing that needs to happen is to reflect and adjust, so when do we go? reflect reflect on what is happening learn understand keep learning having a reflection on what is happening means responding to it so that improvement can happen faster the team can improve effectiveness by regularly reflecting on it so the team also understands the team too having that responsibility to ensure that the necessary adjustments are made, the necessary actions are taken to make those changes and corrections quickly, so these are about 12 principles, what supports, what helps to achieve the points of the manifesto, the four points of the manifesto, what is mentioned, so keep these four points of the manifesto for the values. which is mentioned in the manifesto and then 12 principles, so keeping this in mind, any agile methodology has its own approaches and achieves all this, so let's look further into some of the advantages that there would be by following the agile methodology, So we looked at the downsides. what we have when we follow the waterfall, so do we overcome them? the disadvantages we had in waterfall, did we overcome them using agile?

So what are the advantages of agile? So, agile is useful in terms of handling large amounts of interactions between the client and the project team because you are shedding light on the importance of interactions, the importance of collaboration, what is this about self-organizing teams, it is talked about every again and after improving the transparency of complaints in each phase of the project, how is this transparency because the client is seeing those products, the products with features and functionalities are seen, they are experiencing it and based on that they are giving feedback, there is no nothing hidden, like when I go with the waterfall to the end of the project, the client does not know what is going to come out as a whole, but here, since the workpiece is delivered regularly, the client sees it, the users use it and they give feedback, so interactions increase, so the visibility of what we are creating results is more correct the delivery of the result is predictable and sometimes can be sooner than expected because we know what is being done delivering, users get more and more clarity at the same time the team you are creating is getting the pulse of the customer, the instructions are clear, adapt to changes, what were the challenges, it was a The big challenge in the methodology in Cascading has become easier here, so the cost of the project is predictable and follows a rigid schedule, so it is very easy to manage schedules because you are interacting more and more and there are more iterations in creating small pieces of work. a model of how the product works, so now as you move forward you will understand the environment better, you will understand customers better, customers will get better, expectations will be better and you will move faster so it will be easier for you Now that you've become predictable, you can easily predict what that's going to ultimately happen, so you'll start to get more and more visibility, so getting a handle on things will become easier and then allow changes to refine and get back to you. prioritize product backlog?

So when I say product backlog, we need to understand the different user stories. what is written to be delivered, i.e. a list of deliverables, what is there, since we already know what other things need to be created, so this helps in terms of prioritizing those that change priorities based on the change scenario and then pick up the pace. the speed atConsequently, the client can provide the priority of features that allow the team to guarantee maximum value of the project, so it is visible what the user stories are, what is the vertex written, what is that order of priorities, order of priority, what we maintain now, the scenario of change. obviously it tells us if we really need to change this priority of which feature should be done first to make it easier because the list just changes that order in the list and then moves forward accordingly, the integration is not a problem because we have the base model that can integrate all this seamlessly now, by focusing on the needs of the users, the team can deliver value to customers, so that users engage more often, so that the pulse of the user is understood, it is clearly understood what the user requires and, therefore, that value is delivered. for the client it will be easier and simpler so the project will be divided into smaller units with high quality development testing and collaboration because you have the flexibility so since you have better visibility you can do this and move one by one, iteration after iteration. you make more progress, so those were the advantages of adopting agile, now keeping that agile manifesto in 12 manifesto principles, so what are the types of typical agile methodologies that we would find?

There are some that we will see as part of them. I need to know, so these agile methodologies definitely consider the points of the agile manifesto and then demonstrate it in their own way. Now from the perspective of agile methodologies let's go one by one for some of them to see the first one is xp which is extreme programming so this is the framework that allows teams to create high quality software and improves their quality of life, so it enables software development with proper engineering practices, and when it is applicable, so it is applicable to the scenario where software requirements change to handle risks caused by new technology while working with a small development team extended to use technology that allows for automated unit and functional testing, so this is extreme programming, so next we look at kanban, so kanban is a methodology used to design, manage and improve the system flow.

It is actually called pull system i.e. visual system, so everything that is actually put on a board and visible to everyone, what work needs to be done, what is in progress, who has to do it, is clearly visible so organizations can visualize their flow. of work and limiting your work in progress, so what limits what stops is clearly visible overall if I look every timeI will only take a scenario from a meeting and minutes of the meeting that always discuss about it now, when there are meeting minutes shared with many people who have participated in the meeting, they are given certain actions, for example, now these actions items will have a deadline to complete them and, consequently, they must be closed now, when the next one takes place meeting.

When you look at the action item status, most of them are not addressed. The reason could be that people are not sensitive when it comes to responding or addressing them, more than that, the prioritization changes, so one important thing we need to understand how kanban works here is that it is a visual system compared to minutes. of the meeting that are not always visible to us, the kanban board is visible to us always, so one that is visible to us always makes us make a conscious effort to close it because our name is indicated on the board, the work that must be done be completed is mentioned next to our name, so we need to lift it and then close it to push it.

I'll make a conscious effort because it's visible and I can't build any storage saying why didn't I do it, why didn't I consider this as a priority instead of considering something else as a priority, so this kanban addresses it directly and then also called pull system because people pull work from it and then complete it correctly, so where is it applied? It can be used in situations where work arrives unpredictably, meaning it provides a lot of flexibility in terms of adopting changes that are made. happening in the dynamic environment so it is also used to deploy work immediately without waiting for other work items, so since it is visible I think things can go better and easier for people to take ownership of it instead of just disowning it, so now let's look at lean.

When we say lean, it is very important for us to understand that the value is always in the customer's perspective and the elimination of waste, these are the two things that are mainly talked about, so lean is a set of tools and principles that The speed of process development focuses on maximizing value for the customer, ensuring that waste is minimized, so that when you look at the processes, you visualize the interfaces of the processes and the flow, so that the interface looks a certain way, unless the result of one process or procedure enters another process. so the flow must be smoother as there are many pipes connected together and the water flows, so suppose there is a series of pipes of about a foot in terms of diameter of each of the pipes, the water flows between them if you have a pipe that is half a foot now, what happens to the pipe downstream after that half foot pipe?

All the capacity in the downstream pipeline, even if it has a one foot diameter pipeline, generates waste of underutilized capacity because this has become a bottleneck, now such bottlenecks as the one that contributes waste have to be eliminated. , that is very important, so value must be seen from the consumer's perspective and that value would occur only through serial value streams; then in this value stream, identifying constraints and bottlenecks and eliminating waste, what are they? those that contribute to waste, so timeout more frequently changes things, moves from one place to another, allows defects to flow, which leads to rework, so all this in the same way , many things that actually end up giving shapes, so one has to visualize, understand, realize what they are. those activities that you don't value and eliminating them is very important right now, so when are they applicable?

Lean principles apply to any sector where there is waste of any form, so it can be easily applied, so one should know it, so one should strive for it. should be set with the goal to achieve so that your ability to move faster your ability to create that product that is more efficient so that only you can achieve effective results can only occur when there is less delay or less waste in non-product activities. value that needs to be understood and eliminated, so the next population methodology would be scrum, so scrum is a framework that teams use to establish a hypothesis, test it, reflect on the experience and adjust it, it is used to allow the teams incorporate practices.

From other frameworks, depending on the team requirements, it is a simple framework that talks about a product owner, a scrum master, a self-organizing team, so some of the terminologies it uses are sprint daily scrum product backlog sprint backlog, for which is very essential to understand this framework. simpler and capable of adoption is also very easy when applicable is used when cross-functional teams are working on product development when the work is divided into more than one two- to four-week iteration, so these iterations are called iterations in sprint box, so This will also help in terms of achieving results, it provides flexibility and ability to move faster than Crystal, so Crystal is an approach to software development that focuses on people and their interactions in rather than in tools and processes.

Its objective is to streamline processes and improve optimization. It works on the principle that projects are unique and dynamic, each of which requires its specific methods, so where is applicable. It focuses on strengthening team communication. It also focuses on continuous integration, active user involvement, and configurable processes, so these are the few agile methodologies out there. More popular, more heard, however, we can find many other methodologies, such as Safe Agile, which is a scaled scenario for more complex projects, so we also have many methodologies that organizations adopt and these are few for us to understand as part of this tutorial. to understand the basic requirements of understanding scrum, agile methodology, so let's see the problem scenario, what was there in absence of agile adoption in a given environment, so in the given scenario there is a problem expressed, so We have a problem with our consumer. you don't like our product, we will have to make changes immediately, so now, as usual, any manager will respond, the manager says: make the changes, because it is always the changes or whatever we deliver in the interest of the consumer, for what to take into account the interest of consumers. value that needs to be created for customers, any change that needs to be made in any of our projects involving consumers and customers, we may need to make the change, but what is the problem here to make the change so we can't?

We already have it. I started working on the last batch. The waterfall model we follow does not allow for changes to be made mid-process. So does it mean that the waterfall model never allows changes to occur? That is not true. The 100 percent waterfall model allows us to make changes, but it doesn't allow us to make changes quickly, so every time there is a change it requires a lot of effort, it requires documentation changes, it requests changes in several different implementations, which already has been done, what is already executed and then many efforts are made. This takes a lot of time and also involves more costs.

Now, how do we make the change that is required for the customer and at the same time not have any specific additional efforts that are required, so these efforts, whatever is being done, are acceptable? for both parties, both for the stakeholders, which is the project organization, and for the client, so how can you make this happen quickly? That is very important for us, so we should have used agile methodologies, so agile helps us do this. so one of the agile methodologies that we will see as part of this tutorial is scrum, so let's see how scrum will help the scenario of changes that arise most frequently just before that, let's understand what is the meaning of agile what is the meaning of agile what it means and why we should adopt agile so agile means moving faster being flexible responding to changes now agile is a set of methods and practices that focuses on iterative development why iterative in each iteration Agile methodologies help us create a functional piece of the software product that will help us make quick fixes to those pieces of software.

This is not a complete product, it is part of a larger product, so requirements and solutions are obtained thanks to self-organized cross processes. -Functional teams that collaborate, so when we say cross-functional team, self-organizing team, these are the teams that have seven plus or minus two of the size of the team that I'm talking about and that basically have several different skills, each of the members of the equipment. You will have several different skills and they will complement each other. I think today devops are talking about this cross-functional team that owns everything as one team. Some of the organizations have already demonstrated their devops capabilities by having this approach, such as having self-organization and cross. -Functional team that has responsibility for the entire product, the particular piece of product module that they have created, so this helps improve accountability and also ensures better visibility of the product that is being created and delivered, so let's see more in depth the advantages of using agile, then, what it gives us, how it helps us, now the organization that follows the gel methodologies, so that we can see that the projects follow a predefined schedule and have a predictable cause, so the schedules are seen, but wherever there is a change, wherever there is.

Directions need to be changed in terms of making the necessary changes to adopt the required scenario. The agile change scenario helps us, it provides that flexibility so that clients have visibility of each phase of the project, so it is very essential that whoever adopts the agile methodology has theactive participation of It must be ensured that the client is actively involved in the sense that they know what is happening, what they are getting, they know that they are acknowledging it by giving feedback from time to time so that there are no surprises. them at the end, which used to happen during waterfall approaches, so more interaction between the project team and the project means that there must be agile collaboration, it emphasizes having collaboration, so scrum specifically has something called scrum daily where they meet 15 minutes where all the scrum team must come, sit together, the self-organizing team, as well as all that agile team, must meet, express what they have completed before the last daily scrum meeting and what is pending, why it is pending and what they are going to do before the next meeting so that all this is expressed, this will help the team, as well as the scrum master and the product owner to have visibility of what is complete and what needs to be completed and this will help the project manager or scrum master to better provide the necessary inputs.

Visibility to customers and stakeholders, as well as product production, is predictable and can sometimes occur sooner than expected, so now initially, as we know, the visibility of anything we do will be lower now, as which we discussed more and more as we exchanged more ideas. The greater the visibility of it, the more of what would happen in the future, the ability to predict will also be easier and if this does not only happen with the project team, it will also happen with the clients and all the interested parties involved in the project. High-quality development testing and collaboration are guaranteed from the moment the project is broken down, so now every iteration, every module, every piece of software that is created is tested periodically.

User feedback is obtained and active user participation is ensured for recognition. that's how the customer needs are given, so it's not that I discover something I didn't need, I'm seeing it, I said something, I'm getting something, that scenario is eliminated, then the product backlog can be refined and reprioritized. , so we already move the iteration according to the change scenario, depending on the changes in direction, we can continue to reorder or change the priorities of our product portfolio. What needs to be created first if I have an item one, two, three, four, five, I can make it as three, four, one, two, five, so depending on the change scenario whenever it needs to be run it is a bit flexible and easy to do, then teams can maximize the value of the project as clients can provide priority to the project, so we know visibility also increases for the consumer and all stakeholders.

Expressing what value they have seen from this and this will also help make a decision about whether we should continue with this project or not. Better visibility. Better decision making. Better realization of value. Customer needs can focus on increasing value. delivered so that as the customer gives feedback as the visibility increases, then a customer gets that value and then expresses what the changes are, what additionally they may require here, how it can be improved so that these interactions can happen so that the customer can focus on increasing the delivery of value, so in fact, I think before we used to talk about time to market, today we are talking about time to value, which means how quickly consumers , users or customers realize that value is the benefit obtained, so that is what increasingly The discussion is happening and that requires closer collaboration with consumers and their feedback on their experiences with the products. products or services that they use, it is very essential to understand the different methodologies that we have in Agile, we can talk about scrum kanban extreme programming. i.e xp lean methodologies, crystal so now in this

video

tutorial we are focusing on scrum so let's understand what this scrum is about so before we go and understand what scrum itself is let's see the history of scrum where it started how it started in 1986 the name scrum was first introduced by japanese management experts yukujiro nanaka and hirotakat kuchi so now this terminology was introduced but later in 1995, jeff sutherland and ken schubert created the first version of what would become agile methodologies, so now, in early 1995, the need for agile methodologies was felt and talked about.

I mean, why do we need gel methodologies in the future? what the future organization would look like and what it would trigger in terms of what kind of approaches we might need for beyond 2001, the agile alliance is founded and first you look at scrum, you publish agile software development with scrum, then later on line 2002 weber founds the scrum alliance and certifications are added, then, in 2006, the scrum link is created, scrum certified courses are taught so that people begin to become certified in scrum and, later, in 2009 scrum is created. org, which offers professionals a series of scrum certifications.

Then in 2010, the first scrum guide was published, which was available to everyone, so from then on I think more and more people are starting to adopt scrum methodologies. Now the interesting part is the journey that started from the 1980s to 2010, several changes have happened to this particular methodology but one thing we need to keep in mind is the same thing 20 years ago or 15 20 years ago if we go no The need for a prison was seen, so there was talk but not much about the need for a gel, but today we are talking more and more about it.

The reason is that I believe that the change in market conditions, the increase in competition, the need to respond to the change that consumers demand from market variations, has become increasingly important for organizations and service providers. if they don't respond. Due to the change they may lose in the competition so their survival is at stake so it is very essential for them to understand this dynamic and respond to those scenarios quickly so that is where agile adoption was made, the benefit to adopt a gel and scrum. became popular, so what is scrum, let's see that. Now scrum is a framework that allows teams to work together.

It means collaboration is very important as we become agile. So, with the scrum team one can look, that is, see and experience, so you learn from the experiences. then those are captured self-organized working on problems so that they work together discuss ideas reflect on their victories means that any achievements must be celebrated recognized quick victories recognized and their losses must be improved so where things are not going well the necessary corrections have to be I believe that the scrum approach would help in terms of doing it faster and better than some of the benefits of using scrum.

It would seem that Steam can provide project deliverables and efficiently, so over time we will complete all the features and functionality so that the whole model the methodology, what is there that helps achieve them, then more time and money is used so efficient, so time is very important, giving results in the mentioned schedule is very important, ensuring that the results are obtained effectively, it is important, efficiently, the performance of those products now as we are. creating those small pieces of work in each iteration so that the user experience is also there and quick feedback comes back to save time and money and we are doing it on time, so the projects are divided into smaller units called sprint, so that the iterations What are we talking about the rapid iterations of activities that occur during the adoption of scrum when the organization adopts the scrum methodology, which is why it is called sprint?

They are timebox iterations that will have a set of subsets of product backlogs taken as a sprint backlog and those user stories and epics are delivered as part of that sprint and then reviewed daily as part of the daily standup. of scrum and we also have other meetings that will take place when we look at the methodology of how this happens, I think we will get better visibility that works better for projects that move quickly now when we need to respond quickly when we want to move faster now remember that when We say moving faster means it doesn't mean we can allow defects to happen, we can ignore something we can't.

To do that, we need to make sure everything is taken care of at the same time, all results that are created need to be correctly recognized, confirmed, yes, It's defect-free, so everyone that's supposed to be addressed is taken care of and things move faster and better. and the results are in line with what was actually expressed as a requirement, those scrum meetings are being met which gives the team great visibility as there is a daily scrum meeting that keeps happening, people talk about what they have done in the daily scrum above what is that? have accepted that they will complete and what is complete is that everything is complete or something is pending if it is pending why it is pending and what are you going to do more before the next daily scrum meeting so that these are discussed understood so that There is a quick 15 minute meeting that gives information and also wherever there are dependency deviations that occur further, maybe the scrum master sits down with them separately to understand that in detail, so daily meetings of scrums provide quick information to increase visibility of what is happening.

On the ground it constantly involves feedback from clients and customers as I mentioned above, while discussing active and agile participation of a client is very essential, so the client must give feedback every time that part of the work is delivered. application or a product, so only then if the product or that module that is created has those features and functionalities that help in providing the fulfillment of the necessary requirements, whether it happens or not, making changes based on the feedback is very easy because everyone is informed and aware of what is being changed and what should be changed. changed, then the individual efforts of the team members are focused.

Yes, individual efforts are essential at the same time, the cross skills of each team member we call it a self-organizing team, as I mentioned above, so each team member will have different different skills. Capabilities and also cross-skilling are encouraged within the team so that ownership of individual deliverables and the team as a whole working together to deliver some features can also be achieved at that time the scrum team involves the product owner scrum master and then to the scrum team so that each of These are different roles that have their own objectives to fulfill with specific instructions and each of them cannot be merged, such as the roles and responsibilities of the product owner cannot be assigned to only one person who is a scrum master, so both roles cannot be assigned. a single individual because it conflicts with the objectives of both rules, so thinking about putting this team member as the scrum master product owner thinking about that angle is also something that will not work and will not give the required results, so Now what are they? these roles, what are the responsibilities, where is the focus of each of the roles, so let's look at that now when it comes to the product owner, so that the product owner is primarily responsible for maximizing the return on investment determining the characteristics of the product, prioritizing it in a list.

You need to focus on the next impression and constantly reprioritize and refine it, so the key points we need to look at here are determining the features of the product, maximizing the return on investment (ROI) in the second and then reprioritizing and refine the product portfolio now. Why do you need to do that to maximize ROI in the sense that obviously the product owner needs to work closely with the business and have an idea of ​​what the business needs are? What are the client's needs? How do you help the client achieve that result? justifying that investment, what they are doing with the features and functionality of the products and then talking about reprioritizing and refining them, it depends on what features need to be delivered and in what order, so there is already a defined order, so, depending on the change scenario, you can reorder it and the product owner has that ownership and responsibility, so the entire focus is on ensuring the right product backlog, prioritizing it and also adding those user stories and effects in theproduct backlog depending on what makes sense for the business, so the scrum master takes on the next role. teams learn and apply scrum to realize business value means that the scrum master works closely with the team to help remove impediments something that stops progress something that does not allow things to be delivered in the required way something that stops true, that needs to be removed, that needs to be understood, what are the impediments, so when we say impediments, what are the impediments, we can think about the skills and capabilities of the team, that's one thing, maybe the testing environment can be a process, like that than anything.

It comes as a bottleneck or impediments that prevent things from moving smoothly, so the scrum master must work on it, identify it and support the team or guide them to overcome them, so that it protects them from interfaces that help the team. to adopt agile practices, so they encourage the team to adopt agile practices. practices and ensure that they demonstrate it and provide the required value as you move forward, as scrum master focuses on one side in terms of making the scrum team work, while the product owner looks at the entire product backlog and works more closely with the business, so they need to have a good handshake to ensure things go well, but these two roles cannot be merged because, since they have two different angles and two different dynamics, spending time Achieving both can become very challenging and conflicting, and prioritizing will also be difficult.

The scrum team is a collection of all the people who work together to meet the requirements of the stakeholders, so the self-organizing team, what I was mentioning, what we were discussing earlier, for these teams to come together, each member The team will have several different capabilities so that they can contribute at an individual level and as a team they have a

full

complement or contribute to the end result and value what they need to create and this team must have a clear understanding about the deliverable, what is being done as well It's that deliverable, what features and functionality what they're thinking about is that ultimately that value is going to be created, what needs to be achieved, meeting the requirements, which is what needs to happen to customers, so that they need to have that understanding, the direction needs to be clear to the team, so there are certain artifacts to take into account when it comes to scrum, so let's look at that and now we talk about the artifacts that are the components of this crumb process that they can improve the transparency and understanding of the work, so there are three artifacts mainly which we call as a product backlog, a sprint backlog and then a product increment, so let's see what this is one by one, so when I say product backlog it consists of a list of new features, changes to be made to existing features, bug fixes infrastructure changes and various others. activities that the team needs to deliver to ensure a particular result, so this list shows the product backlogs with the required features and functionality, what needs to be delivered, so the prioritization of this needs to happen in what order, what that needs to be delivered, so that the product backlog is the complete list that needs to be delivered as part of this project and as the project progresses, many new backlog items will be added to the product backlog, as the The dynamics of particular scenarios continue to change, so new priorities continue to be added to the pending work. it is added depending on what those dynamics are, so a sprint backlog is further discussed, so sprint refers to that short period of iterations, so the team aims to get a certain amount of work done to help teams deliver working software frequently so sprint can last between one and four weeks, depending on what the deliverable is, so the sprint backlog is a subset of product backlogs, so that the element that is brought to the sprint is prioritized, which are time-bound iterations, the sprint backlog contains the task that the team intends to complete. to satisfy the sprint goal so what is that sprint goal?

So each of those iterations, time box iterations will have a specific goal to achieve, so the sprint goal is the goal decided for the sprint as a result of negotiation between the product owner and the team. so what can be delivered, how long does it take to deliver, when should it be delivered, the goal may be given by the product owner, but is it possible to complete it, there is some negotiation that happens there, so they decide that they agree, if we can. do it, we can't do it, if we can do it, what it requires in terms of effort, time and cost, everything is decided and discussed so that the objective of those particular iterations is agreed, so once it is okay, I think I should first form a team.

Identify the product backlog tasks that need to be delivered to achieve the goal, so these stars are then added to distribute the backlog, so there must be an agreement between both and once added, once agree as part of that sprint, the deliverable. the output of the sprint would be the one that must be completed as part of it, the objective is the goal, the results, which are a specific work software and then the product increment, so this refers to the combination of all the tasks product backlogs completed in the sprint and value. from the increase of previous sprints now, when we talk about lean, lean talks about eliminating waste, it talks about value streams now in each of these impressions, since we have working software that is delivered now, each of these pieces must follow complementing what is the one that has already been delivered and what will be delivered in the future, taking into account that each deliverable will be implemented or configured in such a way that there are no specific bottlenecks, no specific restrictions arise, so it is necessary to have them consider.

It requires all the visibility of What is the final objective that we are going to achieve? In this product increment, all those combinations of product backlogs being done need to take this into account. The team must be very clear about it, so in the first sprint I delivered something in the In the second sprint I delivered something but I can't integrate them, they can't work together, this will lead to more problems and then complications that shouldn't happen, so when we say agile it's about moving faster, fine, so responding well to change, but that shouldn't lead to more complexity, it should simplify things, so scrum emphasizes that part, so an increment refers to usable work inspectable done at the end of the sprint, represents a step towards the overall goal or vision of the project, as I was mentioning, then the result should be in usable condition even if the product owner doesn't decide to release it, so it should be in usable condition , so we talk about two things, one is the release and the other is the implementation.

Now people usually get confused between release and deployment so I posted about this. Part of what we're talking about is that the product is usable, so it's released. The product is usable, but only after deployment will the user have access to use it, so that's the difference. Version makes a product usable, while implementation makes it available for the user to use. This difference people should know, so release does not mean that it is already available for the user to use, so this understanding of the difference should also be there so that one can understand what release means and what it means deployment so when we talk about devops we still talk about cacd in ci cd we talk about continuous integration, continuous delivery and continuous deployment so in continuous delivery we talk about release basically once it is released it becomes usable so once it is deployed, it is available to the user. use and that's about scrum artifacts now let's look at the scrum framework what that scrum framework looks like in its entirety so what are the components?

We already talked about the scrum approach itself, what it is now, we talked about understanding the artifacts, then I talked about the roles in scrum, the activities for each of the roles, now we understood where we see all this when we look at a scrum framework. scrum, so that image lets us see, when we say scrum framework, we already talk about the product backlog. See it's on the left side at the beginning, we have a sprint planning, so we talk about sprint, the time box iterations, and from the product backlog, the items that are moving into the sprint to a specific sprint , what must be delivered and which becomes the pending work of the sprint. now the items are taken from the backlog and the scrum team works on them and conducts this daily scrum meeting and once the deliverables of that particular sprint are obtained, a review is done, the increment is delivered and at the same time a retrospective of what was planned versus what is delivered is checked if you look from the sprint review to have a retrospective to check what is planned versus what is delivered at the same time, the review points will come and be updated in the product backlog and for the product owner, so The product owner must be aware of what is delivered, what is pending to be delivered and that increment is delivered further, so that these increments, what is delivery to production, what gets deployed to production, they have to have values, that integration that happens with all the increments that come together to provide that. the fulfillment of the requirement, as well as the creation of that value, what is required, so the product backlog is the first step of the scrum framework, it is a set of task lists to have successfully achieved the objectives of the stakeholders, we discussed it while discussing the product portfolio moving forward.

Planning occurs when the team determines the product catalog tasks they will work on and attempt to deliver during the sprint. Now this is negotiated, understood, agreed upon and then the bulk of the sprint to be delivered, then the sprint backlog is the tasks discussed during sprint planning. previous step and also do the planning of the script and then add it to the sprint backlog once it reaches the sprint backlog as part of the time-bound sprint iteration the deliverables should happen now scrum team the scrum team which is actually a self-organizing team as we mentioned maybe five to ten nine team members working on the task in the sprint backlog and they will also have daily scrums where the team will also discuss for 15 minutes about the events in which the team member synchronizes activities and plans what they intend to achieve. in the next 24 hours, which is achieved compared to what was discussed in the previous daily scrum and then, if necessary, further discussions should be held to correct those that can be taken as a separate meeting, not as part of the daily scrum, usually daily.

The cleanup meeting would last 15 minutes, it should not be longer than that, it is an indicative time, so updates are quicker to understand what is happening and then the sprint review is done, once the sprint is completed , the sprint review is carried out involving the team, the scrum master and the product owner. and stakeholders to understand what is being agreed upon and what is being delivered or reviewed is what is fully accomplished what is discussed and then during this meeting the team shows what they accomplished during the sprint gives time to ask questions make observations give feedback and provide suggestions at that time, the product owner also presents the product backlog, talk to the stakeholders to get feedback on the upcoming sprints and on things related to the backlog, now that this sprint is complete for the next print what should be the prioritization so the product owner has to talk to the stakeholders so that there is a good understanding, a good handshake on what needs to be delivered and what is the priority in the given list , then the sprint retrospective will be done, so after this print review, the sprint retrospective will be done, during this meeting what went well, such as past mistakes.

Potential problems, what are the new ways to handle them, what should be done correctly in the next iterations or in the next prints, the data found here needs to be identified and incorporated when planning the new sprint so that it works as a lessonlearned, what went well. what didn't go well what did we do for those what didn't go well then what is the learning that we have in these iterations then how can we make sure that in the next iterations the same mistakes are not repeated so that they can be discussed and documented and then consider that as it happens to next spring, then the increment is a viable outcome that is delivered to the stakeholders, so this is where the user actually sees that viable piece and then provides the necessary feedback as well on the particular application or software piece.

So there is something called a scrum board that is used during this scrum flow from the product reaction to the creation of that increment, so let's see what is a scrum board that is used during scrum practice, so the board Scrum is a physical or physical exercise. virtual tool that helps the team visualize items in the sprint backlog, so it helps keep track of what is being delivered, what is in progress, and what needs to be delivered later, so it shows all action items during the daily scrum and helps keep the team focused on the tasks that need to be completed and the priorities of those The scrum board is usually present in a place that is accessible to all team members It is a visual board and can be a physical whiteboard and stickers or virtual software tools that can be used and displayed on the screen so that the scrum board is divided into different slots, as is done in progress, and when new sprints are started, the existing board is reset and a new scrum board is created, so since it is a visual system, I think it is taking kanban thinking, so the visual system always works effectively because the moment I know I see something put next to my name that I need to complete this, it's pretty obvious to me that I will put in effort to complete it, so it's a conscious effort that I'll put in.

It works in my consciousness so something that is not visible to me is that what is out of sight is what you do not feel, so I will not work on it, so there may be a tendency to forget, so if I see it regularly, if I have that feeling or those vibrations that It's about each individual set, someone is everyone and everyone has visibility of it. There is something pending against me, so I am responsible for consciously bringing that to mind, so when people start working on it and close, this will happen quickly so that everything is visible there.

There is nothing hidden, so look at the scenario, so once it is explained, I think it's okay, although this time we made a mistake, we will incorporate scrum into our products. I'm sure we'll do a good job next time, but keep in mind each time it changes. comes, it doesn't mean that I need to go and practice a little bit, never make that decision, understand what the nature of the change is, what that speed is, how quickly it may be necessary to make the change and what is the impact of the change? often this change can arise, you may know it from the lessons learned with the practices and methodologies adopted and then decide whether the existing model or the existing practice, whatever we are doing, is okay or should we really need to go and have a buying from scrum and we completely organized to have a scrum approach, so it is always advisable to go for a scrum approach whenever there is a dynamic of moving quickly from left to right from product backlog 2 that increases what you need to create to achieve it. that speed and engage consumers regularly if it is feasible so that consumers and stakeholders can say they can't get involved then becoming a gel will not make sense because they are not even giving feedback, such active participation of the team, the scrum master , the product owner, business the interested parties the consumers very very important if they are not involved so that the deliverables cannot happen waiting is required so active participation active collaboration of all interested parties is essential there must be collaboration and communication the effective collaboration and communication that needs to be happening The product team has undertaken a new project called Weather Master.

The team is planning to move to the Scrum methodology. This is a summary of the timing of your first 15-minute Scrum meeting. Rick is the Scrum Master of this meeting where the team members discuss what they did yesterday their plans for today and the impediments they faced All team members are standing including Todd who joined the meeting via video chat rick holds the meeting near a scrum board angela the product owner is absent rick reiterates that all discussions would be put on hold until after the scrum meeting and encourages this team to keep the meeting short, people can intervene to resolve issues obstacles.

Hello team, welcome to the daily meeting for the product team on the Weather Master project. We are in sprint one and today is day two. They are planning the transition to the scrum methodology. I hope you find this daily meeting useful. In this meeting you will provide information about what you did yesterday, what you plan to do today, and the challenges you faced. I think everyone is here, let's get started. I don't see Angela, shouldn't she be here? I added Angela as an optional attendee to this meeting and since she hasn't shown up, we don't have to wait for Susan Scrum to provide a specific yes or no on the Product Owner's participation in the daily scrum.

The PO's main role is to provide direction and clarify requirements and priorities, as we don't always discuss them in detail in this meeting. The PO does not need to be here if the PO wants to attend. Generally, in listen-only mode during the meeting, they can use the information collected during the meeting for separate offline conversations. What's up with Todd? He works from his home office. Todd will be part of the meeting via video chat. It is important that he includes all team members in the meeting Hello Todd, how are you? I'm fine, thanks, I'm audible, yeah Team Todd, let's defend the meeting, why don't you go first, Aaron?

Yesterday I was working on creating mock objects to mask the database calls from the unit tests, the difficulty with this approach is that our server side logic depends so much on metadata that writing a real mock is a gigantic exercise , there are decisions that are made during runtime based on data from some of the stored procedures. Calls are also made based on values ​​returned via inline queries that are also embedded in the code. I was debugging the code until about 9 p.m. m., but for the life of me I couldn't figure this out, Aaron, could we please ask you to be concise when you provide an update if you think some of the details you described might be interesting to others, why don't you write a wiki page on it and Do you share the link to return to your update?

Did you finish your homework yesterday? No, it turned out to be much more complex than I had imagined. I'll continue working on it today and see if I can find an xml structure to mock the schema and encode some return values, but I'm really stuck when it comes to inline queries. I know what you're talking about, there's a reason why inline queries are in the code. This is mainly due to performance reasons when the overhead of making a procedure call based on a metadata value and then processing again, guys, sorry for the interruption. This is a really great conversation.

May I suggest we write this problem in the parking lot? I'm not sure what you mean by that about Rick. Let me explain what Aaron just mentioned. It is a blocking problem. Team members should mention it during the daily scrum. to let everyone know that one of the team members is stuck, however, the daily scrum is not necessarily the meeting where solutions can or should be found to every obstacle, it seems that Mary knows a thing or two about the problem that Erin has posed. Let's write this down as a parking topic, this means the team can have offline conversations after the daily scrum to track it.

I will also make a note that will track the impediment Aaron faced daily until it is removed. You should let me know if I can help in any way, right, Aaron, is there anything else you want to say? No, I'm done, thanks yesterday. I worked on the development of wizards for creating mass orders. I'm almost done today. I need to write code to handle some of the exceptions. scenarios before I can hand them to Susan for her to try, that's it for me. I guess you forgot to mention any impediments that aren't really an impediment right now, but I would like to mention that my computer probably needs to be upgraded with more RAM than it has. slow for the last few weeks, okay, I wrote some scenarios to test the bulk order wizard.

I'm looking to get my hands on the code as soon as Mary finishes today. I also hope to complete the company's order testing that has been placed. pending for a while, I'm fine for the moment, but I have a question: shouldn't we all update the task board as we speak? It could be up to you if you think you want to do this during the meeting. If you ask my opinion, we should update the board as soon as we are ready to move the tasks and not wait for the meeting. This will ensure that the dashboard is always up to date and also that we use the meeting time to focus on the conversations.

Great point Rick, I can't see the board very well from here anyway, so maybe we should find a way to create an electronic version as well at some point. Great point Todd, why don't you continue with your updates? Rick, would you like to know first about my work in the advertising module or the integration server? Whatever the team decides is fine with me. Remember that this is really your meeting and I am only here to facilitate and ensure that we get the most out of this meeting. Alright, so I guess I'll start with the integration server.

I would like to inform everyone that I managed to set up the integration server which we can use as a sandbox to test the code before checking it into source control. I'll send it to everyone. a link with some instructions and credentials. I also started looking at the stories in the advertising module. There seem to be a lot of open statements in the stories that I don't really understand. I guess I should have paid more attention during the process. sprint planning i really need to have a conversation with angela about this, which is my main impediment right now.

I sent him an email but have not received a response yet. I have nothing new to add today. I'm almost done with the configuration. Let's continue our project in the free tool I downloaded yesterday. I'll show you a demo at the meeting I scheduled later today. I'll try to find some of these items from the parking lot. Anything else before closing the meeting is fine. For today, have a great day, do you have a moment to quickly chat about the online queries? The purpose of a scrum meeting is to keep team members updated and resolve any impediments.

It is an ideal way to start the day on a positive note. The scrum master reinforces the sense of the self-managed team facilitates communication between team members returns the team's focus to what is important and supports improvement in this session we will talk about agile project management and several other related things before we begin. Take a look at all the topics we will cover today, first we will see the basics of agile project management, then we will check the relevance and principles of agile project management, then we will see the steps required to implement agile methodology and we will also see the steps necessary to implement the agile methodology.

We will see different frameworks involved in the process and finally we will see some companies using agile project management, so without further ado, let's start with what agile project management is. Agile project management, as the name suggests, is a flexible approach to building a project in an agile manner. project management the project is divided into several stages of sprints agile does not work according to the principle of delivering the final product at the end of the project works on the delivery of sections of a project or mini projects the project management process in the case of Agile It is based on agile, so there will not be any central control of the project manager as there was in the traditional way of working.

Before moving ahead, let's take a look at the agile development cycle. Agile methodologies consist of several small cycles or sprints at the end. At the end of each stage, we get a mini project, there is a backlog of the product thatexplains new features, changes to existing features and various other improvements in the project, then we have a sprint backlog which has a list of tasks that need to be completed during each sprint. sprint consists of planning, designing, executing, testing and implementing the stages and at the end of each sprint a mini project is delivered with each sprint, new features are added to the product which plays an important role in the overall growth of the project after all the sprints and validation early in final product development is less likely to fail.

Let us now look at some of the reasons why industries have started moving towards agile project management. The first reason is the high quality of the product. When we talk about higher product quality, we are referring to the construction of the product. According to the demands of the interested parties, tests are carried out in short time intervals whenever necessary to ensure high quality of the product. Then another reason is customer satisfaction. Whatever is done in the project is known to the client. Deliveries do not take longer than before. Take in case of traditional ways, changes can be provided by the client in the project execution phase.

The third reason is risk reduction, since the project is divided into sprints, so if the risk affects one sprint, it does not mean the entire project. will be at risk the risk analysis process continues to be carried out with all other processes another important reason for agile project management is a better and faster return on investment the project is now developed in several sprints and each sprint has its own version, therefore the project is ready for the market after a few sprints, only because the projects can now be launched easily and in a shorter duration, this helps the organization to stay ahead in the competition with respect to to other organizations that have not yet moved to agile methodology.

Now we will check the principles of Agile Project Management There are 10 principles for successful agile project management. The first principle is customer satisfaction by delivering the project quickly and with the fewest errors. The next principle refers to decreasing the amount of time between the planning and delivery phase. The third principle states that the team of managers and developers work together and increase the productivity of their work. The next principle states that changes requested by stakeholders can be taken into consideration and worked on during the development phase. The fifth principle pays attention to the coordination factor between team members, then the sixth principle refers to the process of monitoring and tracking the progress of the project at the end of each sprint and making modifications when necessary, moving to the next principle states that there must be a feeling of trust. and support the team to complete the project objectives, the next principle emphasizes face-to-face conversations with the development team, face-to-face conversation helps both in solving problems and sharing knowledge easily, then principle nine emphasizes in finding solutions and maximizing the amount of work done with simplicity, this ensures timely completion of tasks by all team members.

The last principle states that scrum tools like monday.com or zoho sprints should be used to simplify complicated codes, which further helps in saving time. see the steps in agile project management the goal of agile methodology is to produce shorter development life cycles and more frequent product releases than traditional waterfall project management, so now we will review six steps in agile methodology of projects the first step of the process is project planning Planning includes the feasibility study, developing the scope, dividing the project into executable tasks or sprints and then estimating the amount of time needed to complete those sprints.

The second step is the roadmap creation step. A roadmap is an action plan that shows how a project will evolve. Over time, you create a list of all the features the final product must have and take steps to achieve those features. The next important step is release planning as we are doing the project keeping in mind the agile methodology of the project in which it will be completed. sprints, that means there will be feature releases at the end of each cycle and unlike the traditional waterfall model, the development cycles will be smaller. The fourth step in agile project management is sprint planning.

Sprints are done taking into account what everything is going to be. achieved in that particular step at the beginning of each sprint the goal of that sprint is decided and steps are taken to achieve that goal the next step in the process emphasizes daily meetings there are short meetings every day to discuss whether the team was able to finish the task for each sprint and check if modifications are required. Each team member talks about what they accomplished in the last print and what they are going to work on in the next print. The last step is the sprint review and retrospective step there are two meetings after each sprint the first meeting is for the sprint review this meeting is with the stakeholders to show them the finished product this helps both parties to build a relationship and discuss if there are any problems in the final product the second meeting is To have a retrospective of the sprint, this meeting involves the stakeholders to discuss what went right and what went wrong during the sprint.

The sprint retrospective takes place after the sprint review and before the next print planning. Now that we know the steps required for agile project methodology, we need to understand them. some agile project management frameworks there are several frameworks available today here we will discuss some of the most popular frameworks the first framework we will discuss is the kanban framework kanban framework is a well-known framework for implementing agile software development in the case of kanban The elements Framework work pieces are represented on the kanban board, helping all team members see the status of each work piece at any time.

The kanban board not only helps to visualize the work but also to optimize the workflow among the team. The next framework we will discuss. today is the scrum framework the scrum framework is a popular framework for managing complex knowledge work such as in the field of research and advanced technologies scrum is a simple framework that helps teamwork and learn through experiences gained while working In a problem the third framework that we will see today is the hybrid framework the hybrid framework is a combination of agile methodology and non-agile methodology in the case of a hybrid framework, planning is done using the traditional way of project management, while the Execution and delivery is carried out using the agile methodology since the hybrid is a combination of the two, it handles changes in requirements and delivers the product in different stages.

The fourth and final framework we will look at is the lean framework. The lean framework works on the principle of providing maximum value to the customer and generating no waste. focuses on optimizing the flow of products along the value stream, this helps eliminate waste throughout the process and create processes that require less human efforts. This also simplifies the information management process and makes it more precise. Finally, let's take a look at some companies. that have opted for agile project management today, around 22 percent of organizations worldwide have all their teams working on the principle of agile project methodology.

Let's take a look at some of the most prominent companies in the world that use agile project management on the list I have ibm cisco atnt microsoft philips and samsung so as part of this tutorial we will see what are the user stories advantages of user stories user invest in user stories how to write user stories three c of user stories life cycle of user stories then user story map and its advantages now let's look at a typical scenario of an organization where the need for user stories would arise , so if we analyze this scenario, an organization would have a scenario where the existing products are selling very well in the market and they can think of introducing a new product or they can think of introducing a new feature or functionality to the existing product, so The scenario we are considering is that it says that our previous products sold very well in the market.

Now let's think about new products, so we'll need to make sure we can understand the requirements and meet them now, how do you do this? So how are you going to understand the consumer requirements, the user requirements and how that will help the user fulfill the requirement and satisfy the need, whatever it is that is required? must be fulfilled, so user story helps whoever understands user stories, will look at the users perspective and these user stories provide information about which user would exist, so as we move forward we will understand in the users perspective users the requirements and how.

User stories help in terms of meeting those requirements. This requires a certain amount of visualization. Let's see what it is. So what are user stories? User stories are an agile software development project management tool that provides users with simple natural language explanations of one or more written features. from the end users perspective, so for a given product we can have many users, so we can develop an application within an organization and use that application for an organization. That's a scenario. The second scenario is that we create a product, we sell it, and the employees of our client organization will become users of those products.

These are the two scenarios, so having these scenarios, what type of product is it, what is the objective of this product that is going to be fulfilled, so let me assume an HR application that is used for submitting claims employees, so what is that requirement? So this application must accept the submission of claims. of the employees of the organization and then that needs to be processed and the complaints need to be cleared now, what will now happen to the user community if you visualize that there is a user as an employee of an organization who submits complaints, so there is a user in the financial perspective who is going to deposit the money similarly, there is a user who is going to approve so many such user interfaces, we will see the existence of user roles, we will see who would use these particular applications, from their perspective there. there should be an interface provided, there should be some privileges provided through which they would perform their transactions and activities when we write user stories we don't write them in detail so a user story doesn't go into details it just mentions how true The type of work will bring value to the end user, so what is this function that the specific end user would do in that particular function in this particular product?

What are the transactions involved? So the end user in this case could mean an external end user or even an internal customer or colleagues within the organization, so looking at these points, if I look at the same application, the HR claims processing application, who Are these internal users, the employees of the organization, so who are these external users, perhaps the people who sold this particular application to our organization, so they installed it? they manage it, there is a management function for this particular product that is a similar function, another set of internal users, maybe someone who is from finance or HR, so in the perspective of each of these functions , this particular product should provide the interface and then there should be a transaction in your perspective which is very important so the user story should explain this very briefly so that it helps in terms of visualizing what kind of interface should be provide and why this particular function would use it.

That's very important, so user stories also form the basis of agile frameworks like epics and initiatives so what is this epic? What is this initiative? Let's see it now. Epics refers to the group of user stories where the large amount of work is divided into user stories, so many user stories together. form epics that will provide some information about how these user stories are connected to each other, similarly initiative refers to the combination of multiple epics that form those initiatives which is very essential for thegroup, so managing the perspective will be easy and also observing the target.

It is that particular set of user stories that the epics group is going to achieve, so user stories can also help ensure that teamwork achieves organizational goals across epics and initiatives. how does this combination of user stories come together, so as an employee I am presenting my complaints, so what is required from that user's perspective? There should be a story, so as a finance person, I'm going to clarify these claims, I'm going to pay the money deposits the money, so that particular role needs certain interfaces and that visualization requires how these interactions happen, so the user story should help in terms of understanding, so the requirements for making the user story a reality are added later, after discussing it with the team. we create a user story, we create a user story, it doesn't end there, so there needs to be a discussion that continues to decide that yes, it is a valid user story, so this will also help in terms of prioritization, which needs to be addressed first.

So user stories are recorded on post-it notes or on an index card or in project management software and this would help in terms of prioritization or tracking as well. So what are the advantages of user stories? quality content because what needs to be achieved from the user perspective will be very clear, facilitates collaboration with team members because finalization of user stories and understanding of user requirements would come after discussion with the members of the team, each one would give their own points of view. and prioritizing a particular user story or maintaining a specific user story or not considering that the user story would be based on the feedback the team provides.

This can't happen in terms of having the team members together and talking about it helps to understand the users better so that the user roles are discussed. The user requirements are analyzed and what they are going to achieve through this user interface which is also analyzed so that the user's role is understood. The user requirements are clearly understood when writing a user story, this will also help improve transparency because since the collaboration takes place from the user story it is not taken just like that, the discussion happens and that will have an interaction and collaboration, so it definitely improves transparency, so now it reduces the risks, so when I say risk, it is obviously uncertainty, so it reduces the risk because the clarity that one would have about the requirement of the users, so that consequently the features, the functionality of the product are defined so that they can meet those user requirements, then it supports iterative developments, as I mentioned earlier, collaboration, transparency, everyone working together and, in the agile perspective, the User stories, epics and initiatives fall into the specifics. iterations only after this discussion with the team members and after prioritizing it so that the user story is present in the product backlogs which will be prioritized based on that particular requirement scenario in an agile scenario, so when we say giant it is quite obvious that we need to be flexible to the changing scenarios as we are working together and when we opt for an iterative mode of approach it is quite obvious that we are going to adopt the changing scenario so that we can select that particular feature functionality pulling that story epic or user story as a priority in the given list to make prioritization also easier focuses on local communications, which means that a lot of interactions happen while discussing user stories, so since people They make it locally, a personal touch is also established.

Could collaboration be established so that the user story also provides that visibility because people working together collaboratively invest in user stories? So what is investing in user stories? So what does that mean? So, it is a concept that helps create meaningful users. stories, so it means independent, negotiable, valuable, estimable, appropriately sized, testable, so when I say independent, whenever we write the user story, it should be independent, if possible, to avoid dependencies on other user stories. user, so they must be independent of each other. that each of them can be developed and delivered separately, so it is negotiable, so when we say that negotiable user stories can always be changed or rewritten, at any given time, we should be able to make the necessary modifications so that that supports the flexibility associated with agile methodologies, since requirements often evolve, change and these changes occur for a number of different reasons, so how do we change these user stories or modify this so that it can fit the requirement so that can be adapted to changing requirements, so history must be debatable? and it should be open to negotiation for any change scenario, so next it is valuable, when I say valuable, it is quite obvious that we are talking about the value that is being created for the users or consumers, so a user story would represent the goal or objective of an end user that they are going to look for means that the value is always in the consumer's perspective, so now I created certain features, the functionality is fine, but that really created the value for the consumers, so that value realization plays an important role, so stories must ensure that value is added. for consumers and clients or users always, otherwise the user story has no meaning as estimable, so when we say estimable, you should always be able to estimate the size of the user story, so sometimes the Developers may not have the experience necessary to size the particular user story. the situations are necessary for a user story, the reasons can be anything, it may be that you don't have a specific vision about it or don't know how to estimate it, there may be someone specific who needs to understand those scenarios and then come and discuss the reasons, it can be anything, so stories If they can't estimate, it will be difficult to handle it better, so it should provide some visualization, so it should be estimable and able to be divided into tasks, so now small means having the appropriate size, so the user story should not be too big or should not be too big. too small and then how do we decide this size?

Now, when we say any user story that a developer can complete in individual iterations, can we call it too big? Obviously, that is again indicative, so the user story should be subdivided into two or more small stories in several parts several small stories small stories so that they can be handled better, so the story should not be too large and should be completed within 40 hours or three to four days. These numbers are indicative, so you don't necessarily have to fix them. with this number it is just an indicative to show you what would be the approach when I say user story, what is the effort that would be required to make that now testable, so when we say that the user story is testable, one must make sure that the development is complete. and it's been done right so it means once a user story is created so it needs to be articulated in such a way that it becomes measurable when I say testable obviously there needs to be metrics and target metrics that can be created and that Please help me Please indicate yes, this particular requirement is met, so they must have an acceptance criterion that can be tested to see if they meet the customer's needs.

So how to write user story, this is a very important point to consider, so how to write user story. User stories present a specific template with simple language, so what is it? Now as a role I want you to continue filling it. Typically, role means what would be the specific user role that would use that particular product and its requirements. that are being fulfilled, then that is the role, the name of the role, we are going to put it here, then the role refers to an individual who would be interacting with the system, now one two when we say one two, the desire or action that represents the behavior of systems, so what is it supposed to do?

This action would be unique to each user story now, so this refers to benefits or outcomes that as a result are non-functional and external to the system, what would happen? what we're trying to achieve from this, so let's look at an example, what does it look like as a CEO? I want to track the progress of my subordinates to ensure that the organization's objectives are met in a similar manner if we take reference to those examples we discussed above. As we take the example of a graph portal, then the claim processing requirement can now be the same user story as an employee of an organization, what can I write?

As an employee of this organization, I want to submit my claims online so that claims processing becomes smoother, easier, faster, error-free, so it can also be a user story, so it provides some visualization of what type of users there are and what they need, so when you write user stories, you should visualize that rule. It is very important so there are three c of user stories we call them card then conversation and then confirmation so when we say card the card provides a written description of the user story so what do I mean by written description of the user story?

So, the same as the user story. I just saw it as an example so that it can be written on a card, which will help plan and estimate what and that will also give that visualization of the users and their requirements so that it can be further articulated and also estimated so that it can be seen. in the perspective of investing what is investing what we discussed then it is independent it is tradable it is valuable it is estimable it has the appropriate size means it should not be too big too small the examples we saw were appropriate and verifiable so now when you see this user story In particular, does it meet all those points that we discussed in investing?

That's very important now, this card, whatever description is given, should explain it very clearly and then continue the conversation after the user story is written on a card and given and shared with all the people who participate in that conversation, so there will be discussion, so the conversation represents the discussion between the product owners of the user team, so this helps in terms of any user story written, if it makes sense, if it is in line with user expectations and at the same time whatever understanding we have, maybe as a product owner or a team member, a developer, my understanding is correct, then the user perspective, so any user story that is written is that the user story talks about the requirement that must be met. must be fulfilled as required, so this helps to build a shared understanding between all those individuals so that there is no more confusion, so that once the people converse together, once the interested parties converse together, you will confirm the confirmation, so this represents the condition that needs to be met to make sure the story meets all the requirements, so you are confirming that all the interested parties agree to it, so first of all, to summarize these three C's, refers to the conversation with the card, the confirmation card provides the user stories that really represent, as we take an example, which will capture that so that it also fulfills the idea of ​​investing, then a conversation is required to Understanding what this user story is talking about is a real requirement, so it needs to be further confirmed in terms of confirmation from users and all stakeholders before developing or executing it.

So what is the user story lifecycle? So when we say life cycle. So we may need to understand that a life cycle starts when you conceptualize, when you visualize, when you say this is what we may need to achieve, they should consume or someone should consume that idea, so it may be related to a problem, it may be related. to a specific product for an opportunity what is seen, whatever the reason,There is a stage in which something is conceived. The trigger may be a problem. The trigger may be some problems. What you are facing. The trigger may be an opportunity.

What is seen, then the initiative. the trigger that actually drove towards the creation of the requirements and the user stories, so the user story lifecycle starts from there, so how does it go? It involves from to do point to to do point, then discussion, then development, conformance and then I'm done, so when I say to do, I'm basically saying user stories in their most basic forms, where they are created after communicating with the user and the project team, this acts as a reminder for further discussion, so it is the first level of understanding user stories in the basic form, so it helps in terms of further discussion and response to a call about it, then there will be a chance for these user stories to be modified as we go.

The answer is yes and no, so it can be modified, but the discussion goes deeper and continues from this basic point. understanding of that particular user story, so the further discussion is to dig deeper into what makes sense and confirm, after discussion with stakeholders, the user stories that need to be addressed are decided and put into sprints, so that enters the point at which we said slope. To do this, among this there is a lot of discussion, so when a decision is made here, it is decided and put into sprints, which means that prioritization is also happening, so now the discussion at this stage the user confirms the requirements and the acceptance criteria, so Acceptance Criteria helps in terms that once you test that particular user story after running it, you will check it against these acceptance criteria so that you can conclude that the requirement.

End users are shown a preview of the upcoming features so that they understand that yes, this is what we were hoping that they could provide any feedback, feedback or necessary knowledge, whatever is necessary so that once the discussion is completed , the team can design and implement features to meet the user's requirements, so that once the user concludes that yes, this is what we expected. and there is an approval during the discussion, then features are developed and implemented so that it can go to that product that can be used and then after development it is adjusted so that the end user confirms that there is a story, the features are confirmed in test environments, alpha versions, and Acceptance criteria are analyzed before saying yes, the user is confirmed to be accepting, so this will happen as part of confirming that the features or functionality that were written in the user story so that specific users are using it and conclude that we recognize that yes, this meets our requirement. and this is according to the acceptance criteria what we discuss and agree, so it is very important, so we write a user story well, but the users do not agree, it is not a good scenario to be with the user, you need to accept and confirm, then finished, so the user store is completed at this stage for new requirements or new features, a new user story needs to be created.

Any new feature or new functionality that you need to add to this particular product, then you would write another user story and the same life cycle starts and continues. This is not an end all, so I keep tweaking features as I add new features, I add as I look to improve performance, so I keep writing the user stories. Now a question keeps coming to me, so we write a user story while meeting the requirements well, as a specific user, I want it to be easy to narrate, so how are we going to see a scenario where there is an improvement of something?

So whenever we are going to discuss the improvement of something, it is quite obvious that we need to look at what is that improvement that the user is seeing now when I send a particular request or access something? It is taking some time, it means there is some delay. Now the user experience can be improved by reducing that particular time which is an improvement as a user. The user story. The basic user story does not change, but in performance perspective you may need to visualize it, so the problem statement should be included accordingly. The user story needs to be articulated and then once the user store is written, user story mapping needs to be included.

User story mapping represents and organizes user stories that help understand system functionalities, system backlog planning releases, and provides value to customers, so typically this involves organizing or organizing user stories based on priority along the horizontal axis, so that it does so horizontally when moving. so I'll say what is the priority, which user stories are priority, the first thing I need to focus on, so that the vertical arrays represent how, in the given specific user story, how the activities perspective, the activity perspective task, the perspective of the subtask, below, how it is elaborated to improve. the levels how it progresses, so now let's look at mapping a user story with an example of, let me say, net banking services provided by a bank for account holders.

When I say net banking service, it is quite obvious that it must also be provided. by having a product that the banking app would use, but here we need to visualize the user's journey while accessing the net banking portal, view account details, pay bills like utility bills, perform many transactions within that portal particularly in banking access at the time they do so. like generating account statements or transferring money to one of the benefit recipients etc., all these transactions, what is being done in this user story map, let's see how it looks, so few activities are considered here, like starting account session means net.

The banking portal will come in, then one will enter their credentials and then log in. Now that users journey in a specific activity, what they do is displayed now they log into the account in the sense that obviously one has to go to that portal, so go to log in. then enter the credentials, login id and password, so once the login id and password are entered, there is obviously a process engine running behind to provide the necessary access now if those credentials don't work or if I don't remember, resetting the password is an option immediately now as you go through this subtask in all the particular columns that I have given you as you go through this, as I go deeper into it, it continues until that the person gets access to the account and then starts by making the transactions it goes up to that level so I can keep writing the subtask so manage the account so it goes to the account page once it accesses and then select the specific account because you can have many different types of accounts, which are there. with bank you can have one or many so in the scenario if you have more than one you will obviously select that account and you will be shown the account details so this user won't but the user will get that, so we are displaying it and Also, after the account details are displayed, what the user would do, then he would continue to display that, so part of the transaction, like generating an account statement, transferring money, even for That, the steps are written, so you need to go to the statement page and then select the account for which you need a statement. then select the period from when to when the statement is required and then click on it and download that particular statement or choose an option that mentions that I need an email or I need a printout of it, so similarly transfer money so you can go to that specific salary where you need to transfer the money so you can have the beneficiary there in the list already added if you have added before or recently you are adding a beneficiary so you have the different types of transfers like the international transfer The local national transfer will have within a bank account within the same bank a bank and two consumers, so, for my part, if I am a consumer transferring money to another consumer of the same bank and vice versa, that is a of the options.

The second is a banking consumer. have and transfer your money to another person's bank account, that is another scenario or transfer money to my own account in another bank, so you run into several different scenarios, then there is limitation or depending on what type of beneficiaries they are, what are the limitations? and how are you going to authenticate them so that by the time you view a specific transaction and user stories activities, what are the things that a user can do, you can keep typing mapping this to each of those flows and see how the flow happens so this flow helps me to incorporate all those features and functionalities and also prioritize them, so can I say that the beneficiary option would be the basic thing that the consumer would give?

I think initially, if I go back, when actually the bank provided the banking features, the basic thing was just seeing the account which was the given statement download, otherwise there was no opportunity to transfer money, there was no opportunity to do something beyond that, so now, as we see today, a lot of flexibility is provided with a lot of new features. in web banking or mobile banking options to evolve, as they evolve it is quite obvious that we may need to keep adding those features by writing user stories, that is how improvement happens, so in Generally, if you look at user story mapping, it helps in terms of understanding not only the user story of a transaction associated with the transaction in the user story, what happens throughout the journey, that will help, so this will also help understand and visualize what needs to be created to ultimately provide that access to the user for the end. -The end to end flow should be visualized and should also be prioritized and it should be analyzed now what are the advantages of user story mapping so that the advantages help to prioritize the work as explained in an example.

Similarly, the focus is on the user. rate the moment I click on the website www.abcbank.com now the bank page will appear. I will have a login interface. I'll go and click sign in now from the point where I open a browser and enter that URL and then click sign in. and the login page tells how long it takes, so there are a lot of things involved: the browser is involved, the system the person logs in from is involved, so you eliminate that part and think that both work fine and which one? should be the answer. from the server where this particular website is hosted, you need to analyze that experience, this is how you analyze the value of the user in that transaction now, once I put the credentials, how quickly the authentication happens, what are the checks What does the bank portal do to ensure that the person logging in is a genuine user, is it just a password?

Is there any captcha code? Was any OTP sent or is there any secret code that the person needs to enter? In the same way, there are many things involved in providing that experience to the user. So, and today's user, if they just put in several different checkpoints, they understand it because they are well educated, so all those things like captcha or otp scenario plots, they are included because more and more informing people has become become your ability to The hack also improves so more and more levels are added to ensure that only that genuine user enters the user account similarly when viewing any product and user journey in user interest which Are the things that will create value that need to be understood? only that experience will help the user to get the benefit, then the obstacles are highlighted, as we visualize this journey, this will tell me what would prevent me from moving forward, if there are any concerns, if there are any limitations, such as if you want to activate a beneficiary but for a limited period you can only send the limited amount of money, why is that done by chance if the beneficiary is added by that person who is not a genuine user, so actually we will keep it correct for when does it freeze? time given, by the time the message reaches the real consumer telling them that there is a user activated in this way and, in any case, if it is not a genuine user, obviously, theperson can call the bank saying that this is not the beneficiary. what I have added, there is something that is not correct, so they are giving that space, so how did they visualize that this should be done?

Looking at the process of adding a beneficiary, it is quite obvious when a beneficiary is added, if by chance someone who is unauthorized adds it, so who is going to get this benefit, obviously the user will not benefit, so blocks and constraints are displayed similarly when creating or creating that features functionality, what should be the basic features or in the product, they should be ready only then I can add this. even that will be visible so that obstacles are highlighted and made visible so that it is easier for you to move forward, prioritize and ensure that you follow the flow necessary to achieve that value and then ensure team unity because everyone will have a visualization of user stories and maps reads a lot of discussion and makes people have a common understanding, so obviously that unity, collaboration would focus on constant improvement, so improvement is the key, whatever you do, you just adopted a methodology waterfall, you just adopted an agile methodology, you write user stories, you raise their peaks, you write, you incorporate several different methods to do something, whatever it does, whether it is a product, a service, a process or a specific transaction task , inform everything we do, so all of that should help in terms of identifying opportunities for improvement and making those improvements, which is very important today as all of us do.

We know that Agile has become a well-known development methodology and the approach of choice for many development teams, especially those trying to create a continuous delivery environment. When we think of Agile, we often think of high levels of collaboration and flexibility, as well as an iterative environment. What requirements evolve alongside changing needs, so we also tend to conceptualize agile as an approach that helps development teams across industries deliver new features faster, but how do we get there? What does the full agile history mean and how can you know the history of Agile Helpers better understand the methodology and its positive impact on today's development world.

Let's look at it historically. If you see that the waterfall approach was fine, it was delivering the required value, but it required the teams to meet the requirements and the stated scope of work. from the beginning of the project and not making any changes or additions along the way as the project progresses and following that fixed plan can be problematic at times compared to the scenarios we had previously, which is today the problem is more challenges , more reason. Being a waterfall methodology, bringing a complete product to market was prioritized, meaning that it could take years before teams finished the project in question.

The change delay scenarios to respond to problem solving, meet changing market requirements, were challenging, which led to the introduction of agile methodologies, thus the various development methods. like scrum, rapid application development, extreme programming, dsdm, feature-driven development and pragmatic programs, were introduced, so it all started early, I think in 2001, it was introduced; However, it all began in the spring of 2000, when a group of 17 software developers in Oregon discussed how they could accelerate development to bring new software to market faster, so they recognized two key opportunities that would allow them to achieve this goal, reducing the time to obtain benefits for those users in order to solve the problems of development and product-market fit, secondly, obtain feedback. of users quickly to confirm the usefulness of the new software and continue to improve it accordingly, so this group of 17 developers met again at a ski resort in Snowbird, Utah, USA, and created the popularly known as manifesto agile, which establishes four key values. which says that the people, interactions, processes and tools that work with the software, rather than comprehensive documentation, customer collaboration or contract negotiation, responding to change or following the plan, are valued more now From the time it was introduced until today, agile methodology has become popular and its adoption has increased.

The reason is the flexibility that agile brought to the system, so several organizations around the world started using it, but what happened after, agile gave the result, but there was a challenge, so there were some problems that agile faces to handle the age of widespread use, which is mainly when there are scalability requirements, so what are the scalability challenges? It's pretty obvious how a brittle deployment can be implemented for larger and more complex projects and how difficult the scaling process is, so it wasn't clear the very reason, the challenge you ran into. What the professionals really faced was the lack of experience with agile methodologies, little understanding of the frameworks methods and how to implement them in the next large scale coordination, so when I say specific project, a small project, it was easy implementation agile and then move forward with all these frameworks.

I mentioned earlier that it was easy but the moment you want to scale to a larger organization, the complex environment, coordination, collaboration, dependency management between generally distributed teams, geographically distributed teams was a challenge and thirdly First, have a clear understanding of what needs to be completed in the sprints. and what is the bigger picture. Fourth, align the entire organization and manage engagement. The organization definitely required alignment. The products or services being produced through the project need alignment, so the need for alignment was basically to ensure that the organization gets the value. Whatever they invested. The fifth unrealistic expectation regarding delivery speed.

It is about time to market, but nowadays it has been replaced by time to benefit how quickly users get the value of that particular product or service introduced in the market. That is very important, so agile scaling framework there are several different frameworks, so some One of the most effective ways to scale agile would be large scale scrum, which is called sls scaled agile framework, scaled disciplined agile scrum. , nexus scrum, the spotify model, so when I say less scrum at scale, it's a way to scale agile and scale. scrum for large product development groups has been used since 2005 on different software and hardware products in industries such as banking and telecommunications, so when it comes to a scaled agile framework, it is a set of organizations and flow patterns. of work intended to guide the company in scaling agile and lean practices to be freely available through a scaled agile link that retains copyright and registered trademarks, so disciplined agile delivery, which is also called daddy, is a software development part of the disciplined agile toolset, so dad allows teams to simplify Process decisions around the delivery of incremental and iterative solutions, so that it builds on many practices of software development advocates. agile software, including scrum hill modeling, development levies and others, so scrum at scale, so scrum originally, if you look at the outline in the scrum guide, is a framework for development. deliver and sustain complex products through a single theme, so from its beginnings its use extended to the creation of products, processes, services and systems that require the efforts of multiple teams, while scrum at scale was created to efficiently coordinate this new equipment ecosystem.

The goal is to establish a minimum viable bureaucracy through a scale-free architecture. Now comes the next one, the Nexus Scrum, so it consists of multiple cross-functional Scrum teams working together to deliver an integrated potentially releasable increment at least at the end of each print based on dependencies. Teams can self-organize and select the most appropriate members to perform a specific job. Lastly, the Spotify model, which is basically a self-contained, people-driven framework to scale agilely while emphasizing the importance of culture and network, this methodology uses squads, tribes, chapters, guilds, the foundation that is . called acting as a scrum team, so let's look at our focus area of ​​this particular video, which is basically what a scaled agile framework is, so the scaled agile framework, as I mentioned earlier, consists of a collection of principles, best practices and processes that would enable large organizations to adopt agile methodologies to help them deliver the highest quality products and services faster, making Safe best suited for complex projects involving multiple large teams at the program and project portfolio levels.

The current version of Safe is version 5, which has seven. core competencies based on which you can help organizations, large organization is specific so it is safe, it has certain core values ​​which are basically alignment, built in quality transparency and program execution so when I say alignment I was mentioning alignment with business requirements business strategies, so it is necessary to keep pace with rapidly changing disruptive competitive forces and geographically distributed teams, while agile and empowered teams are good, even great, but responsibility Strategy and alignment cannot rest on the combined opinions of teams, no matter how good they are, but rather alignment must depend on the companies' business objective, so it must also require keeping up with change, competencies and then the dynamics in the environment in which the organization conducts its business, so the next thing is built-in quality, so built-in quality is basically ensuring that every element and every increment of the solutions reflects the quality standards throughout the development lifecycle, so quality is not added later.

Building quality is a prerequisite for efficiency and flow. Without it, the organization will likely operate with large batches of unverified and unvalidated work leading to the desired product or service. is not right and would also lead to excessive rework, which is not good, and slower speeds, which does not allow the organization to respond quickly to market dynamics, so the third is transparency, which basically should allow that the teams trust each other. There must be trust that must be built, on the basis of which high performance can be achieved, wherever trust exists, so that business and development can trust each other to act with integrity, especially in times of rapid response or to find a solution. to solve something that doesn't actually allow things to move forward, so without trust no one can create high-performing teams and programs, so the trust needed to make reasonable commitments is very, very essential, so fourth There is program execution, so security focuses on work systems and business results. which primarily, for example, for teams to continually execute and deliver value, places an intense focus on work systems and business outcomes, this is because while many companies begin transformation with individual agile teams, they often They are frustrated as even those teams struggle to deliver more substantial results.

The quantity of solution values ​​reliability and efficiency, so offering solutions with better value, reliability and efficiency, is very essential and here we are talking about ensuring scalability to the largest organization, so program management plays a very important role, which requires a lot of collaboration in communication. so without better execution of that, without managing it better, things cannot go as required, so several competencies are recommended safely, so safe competencies involve technical and team agility, agile product delivery , solution delivery, efficient portfolio management, organizational agility, continuous learning culture and then lean agile. leadership, so when I say t1 technical agility, agile teams are high-performing and cross-functional business solutions are created by business and technical teams that delight customers with high-quality results, so this requires a capable team that understands the agile frameworks that follow it andthat they fulfill it. and also a technically sound and agile product delivery which actually refers to the scenario where the customer is at the center of the organization's product strategy, so development is based on cadence and on-demand releases , exploring integrity, continuously implementing and innovating, then, delivering enterprise solutions, building a great system with the help of Lean to coordinate and align the entire supply chain, the continuous evolution of the live system requires ensuring the visibility of entire companies and provide solutions accordingly.

Lean portfolio management that basically focuses on aligning the financing and execution strategy, optimizing operations across the portfolio. Driven decentralized decision making. Through lean governance, organizational agility is created. An agile and agile mindset is created throughout the company. It is very essential, for example, I am working on a project. I have burnout if HR does not understand the dynamics of my project and if they are not agile, I as a project organization. becoming agile will not help in a similar way as procurement, similarly processes are very essential for all units of the organization to become agile so that business operations can complement each other, contribute that speed or change that is required so that opportunities and threats are addressed quickly so that risks are identified and addressed quickly so that they are worked on so that risk management can become easier with the involvement of appropriate stakeholders culture of continuous learning so that in this scenario everyone learn and grow together exploration creativity is a very important part of the organization where there should be innovation creation execution, maybe I think I come across certain terms like intelligent risk taking, so learning through the Failures should lead to investigation, not blame, so these are all things that are increasingly discussed when we want to make an organization a learning, continuous improvement organization. of solutions, services and processes is everyone's responsibility, so agile leadership, by modeling desired behaviors, inspiring others, aligning words, actions and mindset with agile principles and values, leading change and guiding others, so this requires a lot of responsibility and ensuring correct information, well-informed people.

Moving forward now, how does safe work work? Considering those competencies. What we saw in the seven competitions. Let's see what happens in each of the competitions. How does safe work work using these competencies? First, let's look at technical and team agility. Basically, it involves an agile team of 5-11 members that helps define build testing and product deployment, so this is done by breaking the task into small iterations with deadlines that are easier to manage in Chrome. scrum master and supported by the product owner's plan and then deliver the product in increments so that after delivery they have a retrospective to determine how the iterations went and how it can be improved.

This is incorporated into the next phase of iteration planning so that the method is used. Here either scrum or kanban is used, which is why both are popular. The combination of this can be used, so scrum basically helps ensure that things move in iterations and that everything is visible and delivered, while kanban supports it in terms of making it more visible and able to be managed. better agile product delivery, so a large organization usually consists of several agile teams, each led by their respective housekeeping masters, so these teams together represent a range of agile release, also called art, so usually They involve 50 to 125 people, so ART is cross-functional and involves everyone who understands the customer's needs and can help build and deliver the required solution, so ART uses agile delivery practices like those used by teams to deliver value to customers, so it uses timebox iterations called program increments or pis, which typically involve four to five iterations, all teams come together to plan their work during pi planning events, for so the three main components that are required when we do agile product delivery are the release drain engineer and then the project management. and then the system architect, so the release train engineer represents the art coach, facilitated the pa planning process, project management provides the project vision and task backlog, the system architect system provides architectural guidance for the process and then the teams make plans for what they could accomplish, so the program board is also built to determine the dependencies between the teams, which also goes through the program iterations, the pi, as I mentioned earlier, then after each iteration, the art shows the integrated output to all the teams through a demo of the system, so once the pi is completed, the entire team meets for retrospective of the event called events of inspection and adaptation, thereby also establishing a continuous delivery channel based on artistic Devops practices that are also used to ensure that values ​​are available on demand.

I think the term devops is becoming more common. and more popular today, which actually provides that visibility, need for collaboration, need for cultural transformation, which helps in terms of bringing that agility to the entire organization as well as the learning organization, so one of The principles of Devops itself says that continuous learning should be continuous experimentation and learning to take risks in intelligence to take risks and we also find ourselves talking about concepts like the semian army concept, like introducing flaws into existing systems and learning what can fail and what is the solution for it and what can help in terms of becoming a more resilient and reliable system so Devops has become popular and the adoption of that discussion about it has become more common in all organizations, for What the next delivery of enterprise solutions, let's look at scenarios where a single craft may not be able to deliver an adequate solution in a solution train. which coordinates multiple arts and suppliers could provide solutions in large and complex scenarios, so the enterprise consideration has complete visibility of the organization from end to end, so basically what are we trying to achieve, so alignment we discuss what the purpose of the organization requires because the organization is investing so everything we do at different levels should complement each other rather than contradict each other so complementing thinking or complementing visibility can only happen when someone has greater visibility in the business world while looking at the three main components. that are required in delivering enterprise solutions would be the solution architect solution management and solution train engineer solution management has the authority of content or what needs to be built the solutions architect handles the architecture in all arts the solutions train engineer enables

training

and facilitation of solution flow events so that Next is efficient portfolio management, so efficient portfolio management provides ways to create and combine strategic themes and a portfolio view.

This allows the development of solutions to be aligned with the business strategy, so when I say first we must keep in mind that it is about creating value for stakeholders. that's the first thing, the second thing is the elimination of waste now, when I link this to the strategy when a link to the directions of the organization, what it says and as I go in the directions, I have to make sure that no defect moves down. or removed when it goes downstream so customers need to see the value which is very important and all waste contributions need to be identified and removed so this ensures there is value in the value stream of organizations, which also ensures that these value streams remain funded, so funding plays a very important role.

An important role, so next is organizational agility. When I say organizational agility, you have to ensure that the different business units of the organizations are with that dynamic of agility, what organization is going through, what organization is going through, as I mentioned earlier, if you have a project. where you have adopted agile methodologies it is quite obvious by your pace by your flexibility by your speed other business units that are working with you to support you must also complement that they cannot become slower they cannot have their own pace to do things like in your project , you have an acquisition, you have a hiring, you have some claims that need to be removed from human resources, maybe you depend on certain tools and environments now, if these are not agile, if they do not respond with the same flexibility or the same speed as the agile project team requires then obviously things won't flow anymore now when I say agile obviously we introduce products or services quickly into the environment now someone needs to manage we have operations now can operations manage the products or services that neither do you even know at this moment?

There agility is required as I continue to introduce new products or services into the environment, operations must also be well informed and educated about it so that they can monitor and manage them effectively and efficiently if they fail. I think users will not have a good experience. Your product or services may have great features but yet if there is always a query about the features or functionality of that product, whenever there is a problem, the incident that the user actually calls, the first point of contact for any user would be the operations at the time of the operations.

If you don't respond quickly with correct clarifications or rights resolution, then obviously the user experience will not turn out in a good way. I think customer satisfaction or delight will be at stake. Say when the operation should become a job, so the rest of the supporting business units are similar. The financing we talk about financing is not done in an agile way, obviously things can't move more fluidly or easier, so everything across the organization needs to become agile. Organizational agility must be ensured, so that the portfolio is enabled with strategic agility, changes in direction are made depending on the scenario and then encouraged. the growth of people with lean thinking and agile teams, so people must work to ensure value creation, always every task, every transaction is what they do, it must be enabled through it, so they must also know what Whatever we're doing, how this particular task or work or results are performed, what I'm creating results in added value or value creation for the organization, does it really align with the requirements of the organization?

Is it perhaps meeting the client as a stakeholder or my own organization? the business unit that is actually investing in this project in that context or In that perspective, everyone needs to be aware of that alignment, the directions of the vision, then focus on the value and help organize and reorganize building an environment to the flow of value throughout the organization, so that everyone must realize the value, so that value is what can be defined in the perspective of each individual's background and the requirements of each individual because it is perceived, for so there may be something real in what we have created, but the perception is different, so what is perceived versus what is actually created should be as close as possible, so zero deviation is an expectation, but difficult, but However, it should have a tendency towards that, actually it should be very close to that perceived reality, but there are two things involved: one is that I create features and functionalities for my product or service that meet the requirements of the customer, the customer such Maybe you don't know, you're not well informed, you're not up to date. and I don't know how to realize that value, how to know how these features and functionalities can be used, so now if you educate that customer, the user, how to use it, what are the values ​​that you can create and do some exercise in terms of education .

training

, coaching, the client can visualize it and simply understand that this is a possibility.

The second thing is that the client is very mature and our product does not have therequired features and functionalities, so these are the two scenarios that require a lot of interactions and engagement to increase in terms of the use of products and services and the realization of those values, so this should be encouraged more and more to promote a culture of continuous learning. So when we say learning, it is quite obvious that the organization must continue to mature. Individuals in the organization must continue to mature in terms of capabilities in terms of ability to do new things innovate knowledge ability skills competencies so that can only be possible through learning, so learning must be continuous, so so that this guarantees an atmosphere of innovation and constant improvement until organizations become a learning organization, that is, at all levels, every individual, every professional, every engineer.

Each executive invests his time in learning, learns through what he is doing, receives formal training, incorporates that formal training, learns the actions here, learns more, so he continually experiments creating a hypothesis that works on those hypotheses and aligns with the organizations' requirements. and see how it complements the requirements of the organization, so seeing this is very essential so that the organization that has the culture of continuous learning can sustain and grow continuously. It is a matter of looking back if the organization has a scenario where it will not learn. fade away, they may cease to exist, so it is very necessary to understand the dynamics of the market. continuous learning of their capabilities and improvement of skills.

Continuous learning of your innovations and how to improve things. continuous learning, so continuous learning helps the organization to be present in the industry and continue with the competition, so next is agile and agile leadership, so it is quite obvious that leadership plays a role very important, it's about leading, it's about owning, it's about showing directions, it's about ensuring that everyone gets the job done, everyone is motivated, so leaders must embody, teach and exhibit agile and agile principles and values. . So first of all, you have to understand what it is, you have to be aware of it, you have to be exposed to it, you have to be fully aware of it, as I was learning about continuous learning culture in the previous point, so the Leaders should do that first and only then.

I think followers will really embrace learning and things will move more fluidly and better and this should happen throughout the organization, so by doing this it is quite obvious that the organization can become better and the agile organization complement each other to achieve the objectives and goals they wanted to achieve. and there are secure configurations that one must ensure that involve a secure portfolio of secure and completely secure essential secure raj solutions, so when I say essential security it acts as a foundation for all secure configurations and is the easiest starting point for the implementation of such a great solution for sure.

It is used to create large and complex solutions, while the secure portfolio provides principles and strategies that can enable business agility in an enterprise, so when I say portfolio it should be understood as the portfolio of an organization as a whole, the portfolio of services , the product portfolio, the business portfolio. Therefore, understanding this and complementing it is very essential, so total security is a comprehensive setup that includes all competencies and ensures business agility, so advantages and disadvantages of security, so advantages entail allow decentralized decision making, facilitate collaboration between multifunctional teams, guarantee decisions. They are developed with strategic objectives in mind, so the disadvantages include additional layers of supervision that make it similar to the waterfall approach.

The top-down approach can limit understanding of the software lifecycle and cause poor planning, so visibility, as long as that visibility is very essential, then broader planning cycles and roles that look at the development cycles in this session we will learn about the two most popular software development life cycle models, we will understand the contrast between the agile model and the waterfall model of software development, so without further ado, let's start now before. Looking at the differences between the two models, it is important to understand the basics of the software development life cycle and its need, as the name suggests.

The software development life cycle is a process that is used in any software industry to design, develop and test a software the objective of the life cycle is to meet the quality standards of a software a software is always manufactured keeping in mind Account for customer expectations, timelines, and cost estimates. The framework is a collection of steps in which different tasks are defined and performed at each step. Take a look at all the steps involved in the software development process. The software development life cycle has six different stages. The first stage is planning and requirements analysis.

It is the most important and fundamental stage. In this step, contributions are taken from everyone involved in the process. This information is then used to plan the basic process. approach of the project and conduct a feasibility study of the product, this helps the project to excel in the operational and technical economic areas, then comes the second step which is the definition phase or the requirements definition phase, once the performs the analysis of the requirements, this step involves defining them and obtaining them approved by the client, this is possible through a document called srs or software requirements specification document, which consists of all the product requirements that will be designed and will be developed during the life cycle of the project, after the definition phase comes the design phase, the srs that was made in the last step is now used as a reference to build the project based on the srs.

A design document specification or dds is documented, which helps decide the design approach of the project. The next step is construction or development, as the name suggests. The real development begins in this step. The code for the software is generated according to the dds documented in the previous stage. For code, the programming language is chosen with respect to the type of software being developed. After development comes the step of testing the product. The image of this stage refers to the stage where product defects are reported, traced, repaired and retested. This is done until the product reaches the quality standards defined in the SRS.

The last phase is the implementation phase after the testing is done and the product is ready to be implemented, it will be formally launched in the market, the product can be launched first in a limited segment and tested in the real business environment, then, Based on feedback, the product may be released as is or with some updates to the market now that we know. the steps of the software development life cycle let's take a look at the sdlc models. There are several defined and designed software development life cycle models that are followed during the software development process.

These models can be called software development process models. Each model has its own set. of single steps to achieve success there are several sdlc models in the market here we will discuss the two most popular models the waterfall model and the agile model so let's start with what is the waterfall methodology. The waterfall model or waterfall methodology was the first process. The model to be introduced is a linear sequential life cycle model that is easy to understand and operate in the waterfall model. Each phase must be completed before the next begins. The next phase depends entirely on the outcome or deliverables of the previous phase.

The entire software development process is divided into a sequence of several phases. All phases can be seen as a waterfall that constantly flows downwards. Neither phase overlaps the other phase and begins once the previous phase is completed. The steps involved start with requirements gathering and work their way up. To the maintenance phase, let's take a look at all the phases in detail. The first phase is the requirements gathering phase, as the name indicates, all possible requirements of the project to be developed are collected in this phase and documented in a requirements specification document. comes the system design phase, in this phase the requirements collected in the previous phase are studied and the system design is prepared, the design helps to specify all the requirements and also helps to define the overall architecture of the system after the of design, the implementation phase comes after the inputs in the system design phase the system is developed in small programs called units these units are integrated in the next phase here in this phase each unit is developed and tested to determine its functionality , what is known as unit testing now comes the integration and testing phase All the units developed in the previous phase are now integrated into a system after integration the entire system is tested for faults or faults after the testing phase testing, comes the implementation phase, once all the testing, functional testing and non-functional testing are completed.

The product is implemented in the customer's environment or launched on the market. Now comes the last phase, which is the maintenance phase. Issues that arise in the client environment are fixed in this phase and then to improve the project some better versions are released. Maintenance is performed. deliver these changes in the client environment, all these steps or phases are strictly followed one after another like a waterfall moving forward, we know the waterfall model and its phases, so let us now see what is the agile methodology. The agile methodology believes that every project is different and should be handled differently and existing methods should be adapted to better fit the project requirements.

The agile methodology promotes continuous iteration of development and testing throughout the entire life cycle. of software development the process expects rapid delivery of all functional components involved in the project in agile tasks are divided into small periods of time to deliver specific features for a release these divisions are known as prints and these sprints have their own set of deliverables that are decided at the beginning of each sprint work can be reviewed by the project team and the client with the help of daily builds and sprint demos, demo work software is considered the best means of communication with clients to understand the requirements and not just rely on documentation, one of the main focuses of the agile methodology.

It depends on the client, so the process involves the client throughout the project as the requirements cannot be fully collected at the beginning of the project due to various factors. Continuous interaction with the customer is very important to get the right product requirements. Then, there are several phases involved in the agile process. The software development lifecycle begins with concept construction and continues through the retirement process. The life cycle consists of five different phases. Let's take a look at all these phases in detail. The first stage of the agile life cycle is the initiation phase. The initiation phase o The initial phase deals with the completion of the project scope and the return on investment.

This step identifies the team members that will be needed for the project, then also takes into account time constraints and other resources needed to complete the project. The second stage in the life cycle is the planning phase in this phase the team meets and identifies exactly what they are looking for they make a firm plan of how to make the project a success in this phase the risks are estimated and developed milestones with an initial phase Release plan After the planning phase comes the development phase, once the requirements have been defined based on feedback from product owners and stakeholders, the real work of development.

Agile product development delivers high-quality work products in incremental phases or sprints, then comes the release phase. The product after being developed is now deployed and starts being used by the end users. The stages are now closely monitored for any bugs, defects or bugs that may have been left in the test part. This phase continues until the project is fixed with all the bugs and is ready to be retired. The last in the final stage is the retirement phase. This last phase marks the implementation of a newer version of the product in which all the bugs are fixed. errors, there may be some minor software changes in thenewer version and in the older version is no longer supported, the product may also be retired if it is not profitable in the current business scenario.

Now that we know the basic concepts of the two SDLC models and their life cycle phases, we will differentiate between the waterfall model and the agile model depending on different aspects in software development. The first aspect we will see here is the life cycle in In the case of agile methodology, the model life cycle is in a continuous iterative format, this helps to develop and test a project in several iterations, while in the case of waterfall methodology, the life cycle has a sequential format linear where development steps are followed in the form of a top-down approach.

The second difference we will see is based on rigidity, as we know, the agile model is a very flexible way of building a Software in which the feedback of changes can be accepted even after the development has started, while the model in Cascade is less flexible and the model structure is rigidly followed while developing a software. The second difference that we will see is based on rigidity, as we see. Know that the agile model is a very flexible way of building software in which feedback or changes can be accepted even after development has turned around, while the waterfall model is less flexible and the structure of the model is followed rigidly while developing one software and then the next.

The aspect we will discuss is collaboration. If we talk about the collaborative nature of the model, then the agile model is very collaborative in nature, which allows you to deliver a better result and complete the project in a more productive manner, while the waterfall model is not open to collaborations. It does not allow the team to collaborate and strictly follows the sequence of steps. The next important aspect is the process. In the case of the agile method, the process is divided into sprints that have their own deadlines and deliverables at the end. The waterfall model has a development process. of software that is divided into several phases that go as a top-down approach giving a result at the end now after the process the aspect that we will consider is accepting changes in the case of agile methodology the changes can be accepted after the initial phase the planning is complete, while in the case of the waterfall model the development requirements cannot be changed once the project development has started.

The next important aspect on our list is software development. If we consider the agile model, the software development process is a collection of many different projects. As the agile approach completes the project in several sprints, while in the case of the waterfall model, the software development is completed as a single project or deliverable, the next aspect we will discuss is testing, in the case of agile methodology , testing is done in the same step in which programming or building the software is done, while in waterfall model there is a separate testing phase in which the system is tested and this phase comes after the development phase. construction, we often encounter the question of which development model to choose for software development. especially these last three will help you understand which model will best suit your work.

The next aspect we will see is the focus, that is, what exactly the agile or waterfall model focuses on, so the agile model focuses on customer satisfaction and performs the steps with its respective inputs make the entire process is customer-centered, while the waterfall model focuses strictly on the process steps and rigidly follows the sequence; It only focuses on completing the project at the end of the sequential process, while the waterfall model focuses strictly on the steps. in the process and rigidly follows the sequence, it only focuses on completing the project or software at the end of the sequential process now the next important factor is the projects which establish which of the two models best suits which type of projects if If we talk about the agile process, it is very suitable for projects in which the requirements can change, while if we consider the waterfall process, it is very suitable for well-defined projects in which all the requirements are well established and no changes are expected.

The last crucial contrast factor is customer satisfaction, as we know, the agile model is customer-centric and therefore involves the customer in every step of the process, takes their inputs and implements them, while the model in Cascade is an internal process that does not involve clients and simply strictly follows the sequence. of steps let's talk about what agile is, it is a very popular principle used in software or project management. The approach involves creating products incrementally from the beginning of the project rather than delivering them all at once at the end of the project. Agile project processes focus on frequent inspection and adoption, fostering teamwork, self-organization, accountability, and delivering high-quality software.

The business approach is to align development with the needs of the client and those of the organization. Now, as I mentioned earlier, the agile process delivers work in small usable increments so that organizations leverage the agile principles they need to adhere to the values ​​mentioned in the agile manifesto agility puts people and interactions before processes and tools work products are more important than comprehensive documentation client collaboration is much more important than the contract Negotiation and response to changes are more important than following a plan with agility. Clients on the project team can have a great deal of interaction.

This helps them understand each other better. Clients have greater transparency in each phase of the project. The result is delivered predictably. easily and sometimes it can happen sooner than expected. It provides high-quality development testing and collaboration because the project is divided into smaller units and, thanks to continuous evaluation of requirements plans and results, teams can respond to changes very quickly. Now let's talk about some agile methodologies. First, let's take a look at each of them. XP Extreme Programming or XP is a framework with which teams can create high-quality software. It can also greatly help improve your quality of life.

It also involves proper engineering practices to enable software development is now applicable for teams managing changing requirements while working with smaller teams managing risks due to new technologies and much more. Next we have kanban kanban is a visual system that can help organizations visualize their workflow to design, manage and to improve the flow of systems now applicable in scenarios where work is unpredictable. It is also used to deploy work quickly without having to wait for the other components below us. Lean provides a set of tools and services that focus on identifying and eliminating waste so that the speed of process development can be improved with lean, waste is minimized and customer value is maximized.

Lean principles can be applied to any industry. that is susceptible to producing waste, then we have scrum, so we'll take a look at scrum in a moment, but basically scrum is a framework that involves teams establishing a hypothesis, then testing it, reflecting on their experience, and making adjustments accordingly. and finally we have crystal crystal is a software development approach that puts people and interactions tools and processes with Crystal Processes are streamlined and optimization is improved. Crystal is applicable in scenarios where the focus is on strengthening team communication. Now let's take a look at what scrum is.

Scrum is a framework through which teams can work together with the help of. of sprints sprints are events that have a time limit and generally last two to four weeks scrum allows teams to learn from their experiences self-organize and work on their problems reflect on their successes and losses to improve the team's progress is measured by The help of a 15-minute long daily meeting called daily scrum during this meeting, the team members talk about what they plan to do that day, what they did the previous day and the obstacles they faced so that the scrum teams can deliver their projects efficiently in time and money is used effectively thanks to strumming meetings, visibility improves and improvements can be made thanks to constant customer feedback and much more.

Now let's take a look at how scrum works, so here's the whole process, let's take a look at each component first. first we have the product backlog, a list of all the tasks that need to be completed is created now this list is called the product backlog now the completion of all these tasks represents the successful completion of the project, then we have the sprint planning here , the team decides the different tasks they are going to work on and focus on delivering them during the next sprint, then we have the sprint backlog. Now the tasks that were discussed in the product backlog are added to this print backlog, which is basically another smaller list consisting of selected items. product backlog items, next we have the scrum team, the scrum team is a set of five to nine people who are working on the tasks mentioned in the sprint backlog, then we have the daily scrum, now this is a session 15-minute session during which team members can synchronize their activities and determine what they did the previous day, what they plan to do that day, and what obstacles they will face next. sprint review now, after completing a sprint, a meeting involving the scrum team, scrum master product owner and stakeholders takes place during this meeting the team shows what they accomplished during the sprint questions are asked observations are made they make comments and suggestions now it is returned to the product backlog now the product backlog is presented to the stakeholders so that the product owner can get some feedback for the next sprints, then there is also the sprint retrospective, now during this meeting, previous errors are identified and new ways to handle them are determined.

The data that is obtained from this meeting is also used in planning the news trend and finally we have an increase now in this. stage a viable outcome is provided to the stakeholders and after this another sprint starts and the whole process is repeated again now let's talk about strumming vs agile first let's take a look at the methodologies now agile is a set of principles which are iterative and incremental agile You have there are a number of different methodologies that you can choose from, there is xp crystal kanban, even scrum, in fact let's talk about scrum now it is an implementation of the concepts of agile, so basically most of the important components of agile are can apply to scrum and also provides the client with incremental builds that are delivered to the client in the span of two to four weeks an organization can be agile but not practice multitude however an organization cannot practice crumbs without being agile look at projects agile is more suitable for projects that have a small development team made up of experts, while on the scrum side it is generally more suitable for projects that are subject to a large amount of change and will quickly have leadership, now For agile, a project manager takes care of all the tasks and has a very important role to play in the process of a job.

A project manager represents the entire team and is responsible for solving problems by assigning them to the appropriate team members. In scrum there is no leader, there is a scrum master who can generally guide the sprint process, but the team addresses the problems themselves, usually involving cross-functional and self-organizing teams. Next we have flexibility, agility is relatively more rigid than scrum and cannot handle changes with scrum, it also requires a lot of initial development process. and changes within the organization with scrum can enable agile delivery of the team requires frequent deliverables so they can receive feedback from the end user.

This in turn will help improve the product, the product is delivered and updated periodically with scrum afterwards. the team is provided with customer sprint feedback for a build scrum involves daily scrum meetings to review and get feedback to determine the next steps of the project the next print is only planned by the team after the current sprint is completed. Collaboration with agile collaboration involves face-to-face interactions with team members.team of other cross-functional teams for scrum. Daily meetings are held with specific roles like product owner scrum master and scrum team and finally we have design with agile design.

In addition to its execution, it is relatively simple with scrum, the design and its execution can be innovative and experimental, so you may be wondering which one you should choose now between the two options. There is one thing that will remain common in Agile now, what you can decide is which agile methodology you will choose: is it lean, is it canvan or is it scrum, let's jump to scrum versus kanban, so before we delve into the differences between scrum and kanban, let's take a look at a look at what exactly scrum is. Scrum is agile and simple project management. framework that organizations use to help teams collaborate, handle unpredictable and complex projects or products, while ensuring that the products delivered are of the highest value.

Describes a set of meeting tools and roles that enable teams to work in sync and help them structure and manage themselves. Your scrum work is one of those things that is really easy to understand but very difficult to master and although scrum is generally considered to be used by software development teams, its principles and themes are quite universal and can be used with almost anything. type of teamwork. Scrum teams can learn from their experiences what worked, what didn't work, and so on. They can also organize themselves to handle their problems effectively and basically improve themselves by reflecting on them.

So how does scrum work? Here we have the first component, the product backlog, the product backlog consists of a list of tasks that need to be completed so that the stakeholders' goals are achieved, then the team decides which tasks in the product backlog they want to take on. and deliver within a two to four week period called sprint, hence the name sprint planning, then the tasks that were discussed in the previous phase are added to the sprint backlog, this is a set of tasks which will focus on the current sprint, after this the scrum team which usually consists of 5 to 9 members will work on these tasks.

They now also have regular scrum meetings where they talk about their wins, the problems they are facing and what they plan to do in the next 24 hours and then they have the sprint review. The sprint review is a meeting during which the team shows what they achieved during the sprint now during this time questions are asked observations comments and suggestions the product owner also receives feedback from the stakeholders for the next sprints they also have a retrospective of the sprint now during this session past mistakes potential and new problems Ways to handle them are identified. The data from here is incorporated into the new sprint plan.

The final step is to increase. Here a viable and usable result is provided to interested parties. Now that we know how Scrum works, let's take a look at kanban. Kanban comes from the Japanese word kanbam which literally means sign like scrum. Kanban is a popular agile framework that is a visual system by which work can be easily managed as it progresses. Kanban uses something known as a kanban board to make these things possible. With this you can easily identify bottlenecks and then solve them cost-effectively at optimal speeds. The main goal of kanban is transparency, since everything related to tasks is on the board.

Everyone can stay up to date. It also ensures that teams focus on their current tasks until they are finished. These limits. the amount of work that is in progress, so on the kanban board the work is divided into smaller, more manageable pieces the work to be done is written on a note or card and placed on a board the columns on the board They help represent where each item is. Regarding the workflow, now let's look at what they are in detail, let's find out how kanban works now. The board consists of three main components: The to-do list, which represents the items that need to be completed.

The in progress column, which represents items that are currently being worked on, and the completed or finished now column represent tasks or items that have already been completed now, although this is a physical representation of the board, several organizations use software versions of the board that They replace sticky notes with cards that can be moved from column to column as the work progresses. At this point, you guys must have noticed how similar these two frameworks sound, so let's go over some of their similarities, find out what they are like. They seem first, both have principles of lean and agile which means waste reduction and both are iterative and time-bound approaches that allow product to be delivered incrementally.

Both frameworks aim to reduce the amount of work in progress, forcing teams to ensure they focus on a smaller set of tasks. this also makes blockages and bottlenecks a little more visible in both cases work is broken down into smaller, more manageable units both frameworks use pull scheduling now this means products are only created based on demand in Instead of forecasting, transparency plays an important role in both these frameworks help them drive process improvement and in both cases the release plan is continuously optimized and finally both methods aim to deliver releasable software frequently and sooner. than expected.

Now let's take a look at how these two frameworks differ from each other in the first place. take a look at cadence Cadence refers to the amount of time in a sprint or before a release, so when it comes to scrum, the entire project is divided into time-bound iterations, that is, into manageable units smaller, but when it comes to kanban, it even drives the The next criteria we will look at is the release methodology in scrum. Releases take place after each sprint, which typically takes two to four weeks to complete. Kanban releases are carried out in a continuous delivery manner.

They occur in such a way that changes. such as new features, configuration changes, bug fixes and experiments that reach users in a safe, fast and sustainable way. Next, let's take a look at how changes to both frameworks are addressed in scrum. No changes can be made while this print is in progress once it is completed. Changes can be considered in the sprint plan and then added to the sprint backlog. Kanban changes can be made at any time and incorporated into the workflow. Now let's consider the metric that is measured in scrum for process planning and speed of improvement, which is the measure of The work that a team can complete in a sprint is the key metric in kanban.

Delivery time is the key metric. This represents the period of time between the appearance of a new task in your workflow and its final exit from the system. Next, let's take a look. To see how teams work in these frameworks in scrum, you need a cross-functional team to achieve their goals in a sprint in kanban. Cross-functional teams are optional, but specialized topics that focus on particular aspects of the workflow are required. Now let's talk about new additions. In scrum, just like in change management, you can't add any elements between a sprint or nitration. In kanban, new items can be added to the board as long as there is capacity available for it.

Now let's take a look at the job roles within these frameworks that scrum has. three main job roles product owner scrum master and team scrum with kanban you don't have any specific job roles now let's talk about representation or furthermore let's talk about how data can be represented with scrum the board needs to be reset once a sprint is started in Complete with kanban, the board remains persistent throughout the project. And finally let's take a look at linking the project with scrum. It is more suitable for longer projects and with kanban projects that can be completed in a shorter period of time they are better, so which one should you choose now?

The selection of these two methods is mainly based on the team requirements. Do you expect your project to be shorter? you want to make changes at any time you don't want to set specific roles for work then kanban is the framework for you or you want a long duration project with different work roles and involve cross-functional teams scrum is the answer for you based on the differences we discussed in the last topic, you can make an informed decision. Now let's take a look at some of the popular companies around the world that employ both frameworks. companies that have successfully implemented scrum are facebook general electronics and adobe companies that have implemented kanban are siemens bbc and sap today we will learn how to become a certified scrum master so without further ado let's get started so here we have two people let's call them jim and pam here we see jim introducing himself to pam and the team as their new scrum master pam is now expressing interest in becoming a scrum master herself and is asking jen for guidance, happy to help jim get started first, let's talk about scrum, what it is exactly.

Scrum is an extremely popular agile framework that allows teams to work together while working on a complex project or product. Scrum helps teams self-organize to learn from their experiences and reflect on their wins and losses to improve, although it is commonly used in software development the concept of scrum can be applied to any type of team, it is basically a collection of tools and meeting roles that help the team structure and manage their work. Let's talk about some advantages of scrum, first of all, it improves the quality of product development with scrum you can develop complex products in less complicated processes.

Teams can make constant improvements to their product thanks to the input and feedback of their customers. Additionally, it provides faster delivery of projects. Now this can be an extension of the previous point thanks to real-time updates from stakeholders or end users, the team can immediately address changes, allowing the project to be delivered at a faster pace, then scrum gives you A high written investment or return on investment scrum allows you to deliver projects but reduce time. to the market thanks to the results being delivered early, it gives the interested parties to reinvest more. It also demonstrates the value of the project to interested stakeholders.

The following scrum allows for self-sufficiency and creativity. It allows team members to be creative in problem-solving and decision-making. a hands-on approach to the project and since decisions are made by each team member, it ensures its own self-sufficiency and ultimately improves client satisfaction thanks to constant involvement in each phase of the project with feedback and interactions. The final product is more likely to be in a shape they appreciate. Next, let's talk about the role of a scrum master. A scrum master is an individual who promotes and supports the use of scrum practices in the team and in the organization.

Scrum masters have a high-level view of the project and help team members perform their tasks better without having to deal with obstacles and distractions. A scrum master helps the team understand the theoretical rules and values ​​of scrum considering that there are many moving parts in a project. The scrum master enables the business, the product owner, the scrum team and other people to work together in harmony. Now let's talk about the responsibilities of a scrum master. A scrum master ensures that the product owner and development team follow the principles and practices of scrum values. This can help team work effectively and provide high-quality results.

The scrum master also ensures that the team's productivity is not affected by any blockages if the problem can be resolved by the team members alone. The scrum master. Helps the scrum master access different blockages and prioritizes the resolution of each of them. The scrum master also protects the team from any external distractions and interference to ensure that they can deliver value at the end of each and every sprint. A scrum master ensures that the team does not engage in irrelevant discussions and focuses on the sprint goals. Requirements The scrum master also has different roles to play with specific components of the scrum process such as the product owner, the scrum team, and the organization.

Now let's take a look at the responsibilities of the scrum master towards the product owner. The scrum master ensures that objectives are achieved and all team members understand the product domain. The scrum master needs to find a way to effectively manage the product backlog. This helps the teamscrum to understand why your product backlog must be clear and concise. The scrum master needs to ensure that the product backlog is organized. appropriately and to facilitate scrum events such as sprint retrospectives sprint planning sessions daily scrum events now let's take a look at how a scrum masters is accountable to the scrum team for developing the team to be self-organizing and enabling cross-functionality with teams to help The team creates high-value products to eliminate obstacles the team may encounter.

The scrum team needs to facilitate scrum events as required. Now moving forward. The Scrum Master helps the organization lead and coach its adoption of Scrum. The Scrum Master helps plan the process. scrum implementation the scrum master needs to help the employees as well as the stakeholders the scrum master helps to understand how scrum helps to increase the value produced and finally the scrum master helps to make changes that increase the productivity of the scrum team and more now Let's talk about How can you become a scrum master? You must first have a solid understanding of the concepts of scrum and agile.

As a scrum master you must ensure that your team follows the principles of agile and scrum. You must have a clear understanding of the different topics and phases. within scrum to ensure you can understand and teach the use of the framework to the organization correctly. In short, having a detailed understanding of the systems and terminologies is mandatory. A scrum certification can also be of great help with this. More on that in a moment you'll need more information. Sharp organizational skills. You need to be able to structure the team and plan your actions to ensure everything stays organized and to make sure everything stays on schedule.

You need the ability to plan things. Must be able to ensure equipment is maintained as intended. and all tasks are completed successfully, you can also use online project management systems like monday.com nutcase and sam 9000 to keep things organized. You need to be familiar with the technology the equipment uses. you need to make sure the team can complete their tasks. project in a timely manner, this can be done by understanding the different technical terms and processes that the team is involved in, therefore some technical familiarity and training is really important. You must also have the ability to coach and teach the team to follow. scrum appropriately for teams that are new to the scrum methodology your ability to teach them the different concepts, terms and principles play a very important role in the future success of the team, you need to be able to tell the team not only what needs to be done, but also how and why you also need to be able to increase the number of team members to work together and improve themselves.

You may also need to work with individual team members to maximize their potential. You need to have the ability to handle conflicts and resolve them quickly. Considering that teams are full of people with different personalities, ideas and working styles, they are likely to come into conflict from time to time, if disagreements cannot be handled between them, it is necessary to be able to resolve things, if not are resolved, this could inhibit the progress of the entire team so you must be able to negotiate and resolve the conflict in a way that satisfies everyone and finally you must be a servant leader a servant leader puts the needs of the team before the needs of the team. own and help each member perform to the best of their abilities, you need to be both a leader and a team member, you need to be part of your team while ensuring that they can successfully meet your requirements.

Now let's talk about the certifications to become a certified scrum master in that one. The most important thing you can do is pass the certified scrum master test. This quiz tests your understanding of the different principles and processes that are part of the scrum process. Additionally, to take this test you must have completed an in-person or online test. course taught by a certified scrum coach or certified agile coach you will also need to have at least 14 hours of face to face interaction with the aforementioned coach or a coach let's go to the exam the exam is 1 hour and has It has 50 questions and you must obtain at least 37 to pass the exam.

The exam costs between 29 and 30 dollars and you have two attempts to pass it after 90 days or two attempts, you will have to pay 25 to retake the exam once. If you are certified, you will need to recertify by taking an exam again after two years. Now let's talk about the salary of a scrum master according to glassdoor, in the United States of America, a scrum master earns approximately 97,000 US dollars per year, meanwhile in India. A scrum master can earn up to Rs 14 lakh per year. I'm excited about becoming a scrum master, but let me now tell you how Simply Learn can help.

Simply Learn offers the Certified Scrum Master Certification Training Course, so we simply learn the Certified Scrum Master Certification. will provide you with agile and scrum methodologies importance of agile scrum lifecycle scrum terminologies roles involved in scrum and much more, so take the first step towards becoming certified and advancing your career by clicking on the top right corner and signing up in Simply Learn and With this we have reached the end of this video of the complete course on Agile and Scrum. I hope it was informative and interesting. If you have any questions related to the topics covered in this video, please ask in the comments section below, our team will help you. please resolve your queries as soon as possible thanks for watching, stay safe and keep learning Hello, if you like this video, please subscribe to Simply Learn YouTube channel and click here to watch similar videos.

Turn up the volume and get certified. Click here.