Agile Scrum Model

In the last topic we studied the Iterative Model. Now, let’s see about Agile software. The different software development methods are there, these have formed a group and from that Agile methodology has come out. In this the work happens with the Iterative approach. After every Iteration the software is delivered and in every new build there is an additional feature. Come, let’s see it in the form of a diagram and understand it very easily. In Agile First of all we will gather the requirements. Based on those requirements we will create the stories. In Agile stories it means test case. It is not a new thing; test cases are called stories in Agile. Right? In every story what will happen? We will write its criteria. We will write the criteria of a particular functionality. Like how this functionality should work. Right? If there is a button, a login button. How will it have different, different behavior? After entering the username, password the login button should be activated. If the user has not entered username, password, the login button should be disabled. And many other things that are there, we will write them in the stories. As soon as the stories are getting over, they will go to the developers and according to that the development will happen. The stories are written, they are developed, tested and they are delivered. This entire process will be in continuation. Like in this first of all they have mentioned start, initiate project, in which we will collect the requirement. After that, whichever development comes, there will be a development of it. As soon as the development happens, development one, they will integrate and test it. That is complete, development 2, development 3, like this there will be End number of developments. After that what will happen? It will have its release, feedback. From whom will we get the feedback, from the clients? Whichever small functionality that we have added. Is it particularly working as per your requirement or not? If it is accepted, we will release it in the market. If it is not accepted, what will happen? If not, what are the changes that they have given? The changes that the client has given us, we will record it. Like in the login page first we had to mention, Username, Password and Login. Client is seeing and saying that I want change. What change does he want? I also want to use Captcha code. Username, password and after that Captcha code will be there. So a change has come. So, what will we do? Record in corporate change. We will record and implement the change. We will track the change, when that change is going to get over. When that change will be developed. And next Iteration we will do in development. Again, we went into development, again we will take its feedback. Accept, yes and release to market. It is very simple to understand the Agile Model. This also has its advantages and disadvantages. We will see, what is it? This is a very realistic approach for software development. Why is it a realistic approach? The small requirements that we develop, we are telling about it to our clients. If the client is happy, we can release the product. Right? The disadvantage of it is that somewhere the complex dependencies are difficult to handle. In this there will be teamwork because the entire process that is there in which the developers are there, project manager, everyone will be included, so the team work will increase. In this the risk is there of maintainability and extensibility. It is possible that few functionalities cannot be implemented going ahead in a particular project. It is not necessary that every functionality that is not coming can be implemented. We can give the customers the development and easy demos, quickly. Somewhere its disadvantage is that we have to follow the practices of Agile. We have to follow Agile project management practices, otherwise this will not work. This Agile development, it is suitable to whom, where there are changing requirements or little bit of fixed requirements. But where is its disadvantage? In the delivery management. Now, in the next topic we will see Forms of Testing.