 Hello, welcome to the session on agile scrum methodology in continuation with the previous contents. Let us see the learning outcome. At the end of this session, students will be able to apply the scrum methodology for software development. Now pause the video for a while and think about what are the business challenges in software development. Let us say one of the important business challenges is shorter delivery cycles or long term customer commitment. Customers looking at faster delivery cycles within a short period of time, solutions to meet customers ever changing business environment, long term customer commitment in development and maintenance of the project and time to market the final product. The second challenge is customer expects more features to be added in the project and also expects better software quality, priority wise adding the features, maintain the high production quality and improve the usability of the software. So these are the some of the challenges. The next challenge is in a competitive world the software should support or address new market requirements and also to maintain or keep track of old customers. From a present in a new market and segments, deliver the project as promised to client, improve customer satisfaction and ensure the retention, agile methodology is a practice that promotes continuous iteration of the development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the waterfall model. A few of the new methodologies are scrum, crystal methodology, dynamic software development methodology, dsdm, ftd, lean software development, extreme programming. Here I am going to discuss more detail about the scrum methodology. The requirements of the market change invariable faster and only the ones who are flexible and contemporary can react time to market and stay competitive and create themselves a competitive advantage. Scrum allows the incremental development of the features. In time the customer receives the first working versions, he sees the progress and if necessary can add some new ideas. Transparency plays a great deal on various levels of scrum because of transparency all the stakeholders are informed where the project is at. It helps discovering weaknesses and it makes the effective teamwork possible which makes scrum so efficient. Testing is an integrative component of scrum at your sprint only if the software is tested and documented it is ready. Regular releases that establishes the condition to recognize the problems on time and react promptly. There are long term statements about the time factor and the product completion possible because of the factors as a team velocity. The period of a project is usually fixed. The effort and the complexity through are just rough. Scrum allows changes on the specification. It includes the customer in the project creates transparency and therefore it allows a definite cost accounting. Scrum is not afraid of changes. On the contrary changes can be shown to the product owner at any time and can be realized in the following sprint. That way the customer gets the product he or she desires. Scrum involves all the participants of the project communication collaboration respect and the understanding what the customer requires or what the team develops is the basis for successful projects. In opposition to the widespread perspective scrum is very good for the development of complex systems and extends you or as the case may be long projects especially there are the exact planning has got a huge impact and the continuous integration of the new functionalities assures that there won't be a bad awakening in the end. Many production plants work with lean principles and the software development that scrum creates an optimal synergy. Not the assignment of the tasks but collaborative functioning and making decisions as a team is an important part of the screen. Software development is seen as what it is a creative and multi-sided activity that can only work properly when everyone takes the responsibility. Pause the video for a while and think about in which game you can find this type of team activity or the scenario. Yes. It's a rugby union game scrum methodology is related to rugby game scrum is an agile development methods which concentrate specifically on how to manage the task within a team-based development environment basically scrum is derived from activity that occurs during a rugby match scrum believes in empowering the development team and advocates working in a small teams says a seven to nine members figure shows a scrum methodology scrum includes the same type of activities as the waterfall methodology that is the processors but rather than implementing them as a sequential phases they are encapsulated into multiple iterations or sprints to create a working application. In this way scrum builds the application incrementally with each increment adding and improving the features and functionality created by its predecessor. I am going to explain in detail of different types of scrum methodology in the next video. Every member of the team understands their role and is aware of the issues and tasks across the team. Issues are quickly identified and corrected. Another integral component of scrum is the different types of feedback loops used to ensure that and end users and customers sees the teams results quickly and they provide timely feedback end users and customers refine existing requirements and provides a new ones as the project progresses. Sponsors sees the team progress as it takes place to eliminate wasteful activities such as formal and often repetitive status reports that detract from the time spent on actually developing a project. There are three types of roles internal to scrum team and one that's external. External roles are the product owner. The product owner is the primary interface between the team and the business owner and is responsible for the maintaining and prioritizing the backlogs of the tasks to be performed. This is performed transparently and collaboratively with the development team. The product owner is also the arbitrary of questions concerning backlog items and to make sure that the team understands the purpose and the value of the application as the customer. The product owner is also arbitrary of questions concerning backlog items and to make sure that the team understand the purpose and the value the application has to the customer. The product owner is also keeps the backlog current as new requirements and existing requirements are refined. Scrum master the primary goal of scrum master is to keep the development team productive. The scrum master must lead by example and acts as a servant leader for the team coaching them to make sure they understand and follow the scrum process and that they operate in a collaborative and professional manner. From the perspective of the product owner the scrum master represents the development team ensures that their issues concerns and roadblocks are taken into consideration by the product owner. Development team the development team is responsible for delivering the product. The team is typically a cross functional in terms of expertise and experience and the team as a whole is accountable for the delivery and quality of the application. Development teams are also self organizing. This means that the team not the product owner or the scrum master or responsible for defining the rules dictating how they work together. The product owner is also responsible for defining the backlog of what needs to be accomplished but the development team is responsible for defining how it is completed. There are no titles or sub teams within the development team. Members of the team may have different skills specialization and experience but they all have a voice in the operation of the project and all contribute to the creation of the application. The scrum master and the development team are collectively referred to as a scrum team. These are the references I refer. Thank you.