Introduction to Scrum3 things we want to be true:Say no to plagiarism. Get a Tailored Essay on “Why Violent Video Games Should Not Be Banned”?Get an original essayThe customer knows what they wantThe developers know how to build itNothing will change along the way3 things we have to live with:The customer discovers what he wants Developers discovers how to build it Most things change along the way. Given the above reality, this led to the founding of Agile which is “The Manifesto for Agile Software Development” which was officially made public in February 2001. Through this work, we managed to value:Individuals and interactions on processes and toolsWorking software on comprehensive documentationCollaboration with clients on contract negotiationResponding to change by following a planKen Schwaber and Jeff Sutherland worked on Scrum until 1995, when they co-presented Scrum at the OOPSLA conference in 1995. This presentation essentially documented the learner that Ken and Jeff acquired over the previous years and made public the first formal definition of Scrum. The history of Scrum is described elsewhere. To honor the first places it was tested and perfected, we recognize Individual, Inc., Newspaper, Fidelity Investments and IDX (now GE Medical). The Scrum Guide documents Scrum as it was developed, evolved, and supported over 20 years by Jeff Sutherland and Ken Schwaber. Other sources provide you with templates, processes, and information that complement the Scrum framework. These can increase productivity, value, creativity and satisfaction with results. Purpose of Scrum: Scrum is a framework for developing, delivering and maintaining complex products. Scrum consists of the roles, events, artifacts, and the rules that bind them together. Scrum is a framework in which people can solve complex adaptation problems, while productively and creatively delivering products of the highest possible value. Scrum is: LightweightSimple to understandDifficult to understand masterScrum is a process framework used to manage work on complex products since the early 1990s. Scrum is not a definitive process, technique, or method. Instead, you can use various processes and techniques within a framework. Scrum clearly shows the relative effectiveness of your product management and work techniques so that you can continually improve the product, the team, and the work environment. The Scrum framework consists of Scrum teams and their associated roles, events, artifacts, and rules. Each component of the framework serves a specific purpose and is essential to the success and use of Scrum. Scrum rules link roles, events and artifacts, governing the relationships and interactions between them. Topic Analysis Scrum was originally developed to manage and develop products. Since the early 1990s, Scrum has been widely used around the world to: Research and identify viable markets, technologies, and product capabilities; Develop products and improvements; Publish products and improvements, as often as several times per day; Develop and maintain the Cloud. (online, secure, on-demand) and other operational. Product use environments; and, Maintain and renew products. Scrum has been used to develop software, hardware, embedded software, networks of interactive functions, autonomous vehicles, schools, government, marketing, management of the operation oforganizations and almost everything we use in our daily lives, as individuals and companies. As technological, commercial and environmental complexities and their interactions have rapidly increased; The usefulness of Scrum for managing complexity is proven daily. Scrum has proven to be particularly effective in iterative and incremental knowledge transfer. Scrum is now widely used for products, services, and management of the parent organization. The essence of Scrum is a small team of people. The individual team is very flexible and adaptive. These enduring assets operate in one, many, many, and networks of teams that develop, disseminate, leverage, and support the work and work products of thousands of people. They collaborate, interact via sophisticated development architectures and target release environments. Scrum is based on empirical process control theory or empiricism. Empiricism states that knowledge comes from experience and making decisions based on what is known. Scrum uses an iterative and incremental approach to optimize predictability and control risk. Three pillars support any implementation of empirical process control: transparency, inspection and adaptation. Scrum prescribes four formal events for inspection and adaptation, as described in the Scrum Events section of this document: Sprint Planning Daily Scrum Sprint Review Sprint Retrospective When the values ​​of commitment, courage, focus, Openness and respect are embodied and experienced by the Scrum team, the Scrum team the pillars of transparency, inspection and adaptation come to life and strengthen everyone's trust. Scrum team members learn and explore these values ​​by working with Scrum roles, events, and artifacts. Successful use of Scrum depends on people's ability to better live these five values. People are personally committed to achieving the Scrum Team's goals. Scrum team members have the courage to do the right thing and work on difficult problems. Everyone focuses on the Sprint work and the Scrum Team goals. The Scrum Team and its stakeholders agree to be open about all work and challenges related to performing the work. Scrum team members respect each other for being competent and independent people. The Scrum team consists of a Product Owner, the development team and a Scrum Master. Scrum teams are self-organizing and cross-functional. Self-organizing teams choose the best way to accomplish their work, rather than being led by people outside the team. Cross-functional teams have all the skills needed to get the job done without depending on others not on the team. The team model in Scrum is designed to optimize flexibility, creativity and productivity. The Scrum team is proving more and more effective for all the uses mentioned above and any complex work. Scrum teams deliver products in an iterative and incremental manner, maximizing opportunities for feedback. Incremental deliveries of the “Done” product ensure that a potentially useful version of a working product is always available. Scrum artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everyone has the same understanding of the artifact. Scaling Scrum: Keep.