IndexWhat is Scrum?ScrumMasterProduct OwnerTeam Software development organizations are increasingly interested in agile methodologies, the focus of which is customer collaboration, individual value and adaptation to change . Scrum is a framework within which people can tackle complex adaptive problems while productively and creatively delivering products of the highest possible value. Scrum clarifies the relative effectiveness of product development and management practices so you can improve. The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework has a specific purpose and is essential to the success and use of Scrum. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an original essay What is scrum? Scrum is a framework for managing work with a focus on software development. It is designed for teams of three to nine developers who break their work into actions that can be completed within time-bound iterations called sprints (typically two weeks), and track progress and reschedule in 15-minute stand-up meetings called daily scrums. Approaches for coordinating the work of multiple Scrum teams in larger organizations include Large-Scale Scrum, Scaled Agile Framework (SAFe), and Scrum of Scrums, among others. Scrum Values: - Scrum is an empirical feedback-based approach that is, like all empirical process control approaches, underpinned by the three pillars of transparency, inspection and adaptation. All work within the Scrum framework should be visible to those who are responsible for the outcome: the process, the workflow, the progress, etc. To make these things visible, Scrum teams need to frequently inspect the product under development and how well the team is working. working. With frequent inspections, the team can identify when their work deviates from acceptable limits and adapt their process or product under development.[18]These three pillars require trust and openness in the team, which the following five Scrum values enable:[ 14] Commitment: Team members individually commit to achieving their team goals, in each sprint. Courage: Team members know they have the courage to face conflicts and challenges together so they can do the right thing. Focus: Team members focus exclusively on their team goals and sprint backlog; no other work should be done except through their backlog. Openness: Team members and their stakeholders agree to be transparent about their work and the challenges they face. Respect: Team members respect each other for being technically capable and working with good intentions. Scrum Roles: - The three roles defined in Scrum are the ScrumMaster, the Product Owner and the Team (which consists of the Team members). The people in these roles work together closely, on a daily basis, to ensure the smooth flow of information and rapid resolution of issues. ScrumMaster The ScrumMaster (sometimes written “Scrum Master”, although the official term has no space after “Scrum Master”) ) is the custodian of the process. The ScrumMaster is responsible for making the process run smoothly, removing obstacles that impact productivity, and organizing and facilitating critical meetings. ScrumMasters' responsibilities include removing barriers between the development team and the Product Owner so that the Product Owner directly leads development. Signto the Product Owner how to maximize return on investment (ROI) and achieve his goals through Scrum. Improve the lives of the development team by facilitating creativity and empowerment. Improve the productivity of the development team in every way possible. Improve engineering practices and tools so that each increment of functionality is potentially transportable. Keep information on Team progress updated and visible to all parties. In practical terms, the ScrumMaster must understand Scrum well enough to be able to train and guide other roles and educate and assist other stakeholders involved in the process. The ScrumMaster should maintain a constant awareness of the status of the project (its progress to date) relative to expected progress, investigate and facilitate resolution of any obstacles holding back progress, and generally be flexible enough to identify and address any issues that arise, in any way required. The ScrumMaster must protect the Team from disturbances coming from other people by acting as an interface between the two. The ScrumMaster does not assign tasks to Team members, assigning a task is a Team responsibility. The ScrumMaster's general approach towards the Team is to encourage and facilitate their decision-making and problem-solving skills so that they can work with increasing efficiency and reducing the need for supervision. The goal is to have a team that not only has the power to make important decisions, but also makes them well and consistently. Product Owner The Product Owner is the custodian of the requirements. The Product Owner provides the “single source of truth” for the Team regarding the requirements and their planned implementation order. In practice, the Product Owner is the interface between the company, customers and their product-related needs on the one hand, and the Team on the other. The Product Owner protects the team from feature and bug fix requests that come from many sources and is the single point of contact for all questions about product requirements. The Product Owner works closely with the team to define technical and user-facing requirements, to document requirements as needed, and to determine the order of their implementation. The Product Owner maintains the Product Backlog (which is the repository of all this information), keeping it updated and at the level of detail and quality required by the Team. The Product Owner also establishes the schedule for releasing completed work to customers and makes the final decision to verify whether implementations have the features and quality required for release. Team The Team is a self-organizing and cross-functional group of people who take care of manual activities. -on product development and testing work. Since the Team is responsible for producing the product, it must also have the authority to make decisions about how to perform the work. The Team is therefore self-organised: Team members decide how to divide the work into tasks and how to assign tasks to individuals during the Sprint. The team size should be between five and nine people if possible. (A larger number makes communication difficult, while a smaller number leads to low productivity and fragility.) Note: A very similar term, “Scrum Team,” refers to the Team plus the ScrumMaster and Product Owner. Pros Scrum: – Scrum can help teams complete project deliverables quickly and efficiently: Scrum ensures effective use of time and money Large projects are broken down into easily manageable sprints Developments are coded and tested during review of the sprint Works well for development projects in.