### Payment ![[Pasted image 20240629222622.png]] ### Course Notes 1. Course - https://www.udemy.com/course/complete-professional-scrum-master-training-exam-simulator/learn/lecture/20828472?start=1#overview 2. Scrum in 3 Minutes 1. 3 Artifacts 1. Product Backlog 2. Sprint Backlog 3. Incriment 2. Breaking items down to simple blocks 1. Product Backlog -> 2. Sprint Planning -> 3. Sprint Backlog -> 4. Sprint -> 5. Incriment 3. 5 Events 1. Sprint 2. Sprint Planning 3. Sprint Review 4. Sprint Retrospective 5. Daily Scrum 4. 3 Accountabilities 1. Product Owner (PO) 1. Manages the product Backlog 2. Maximize Value of Product 2. Developers 1. Turn the backlog into Incriments 3. Scrum Master 1. Who manages the scrum workflow 3. Test 1. 150 usd 2. 60 minutes 3. 80 questions 1. multiple choice, true false, multiple answrs 4. Open Book 5. On Scrum Guide 6. Passing 85% 4. Scrum Flow 1. A) 3 Accountability + 3 Artifacts + 5 Events + Foundations 2. B) Theory + Flow + Scrum Team 3. C) Artifacts & Events + Scaled Scrum + Popular Practices 5. Scrum 1. Scrum is guiding changes 2. a framework to use on complex issues 6. Trad vs Agile 1. Scrum is an agile framework 2. Agility means responding to change 7. Agile x Rapid x Lean 1. To be rapid u need to be agile 2. Agile doesnt have to be rapid 3. Succeeding with agile and scrum requires being rapid and lean 8. Agile Mindset 1. See setbacks as Learning Opportunities 2. Adopt short delivery cycles, collaboration, and change 3. Focus on Delivering value 9. Agile Values 1. individuals & interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer Collaboration over Contract Negotiation 4. Responding to Change over Following a Plan 10. 12 Agile Principles 1. Project 2. Product 3. People 4. Process 11. Scrum Guide Definition 1. #### **Purpose of the Scrum Guide** 2. We developed Scrum in the early 1990s. We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum. We have evolved the Guide since then through small, functional updates. Together, we stand behind it. The Scrum Guide contains the definition of Scrum. Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless. We follow the growing use of Scrum within an ever-growing complex world. We are humbled to see **Scrum being adopted in many domains holding essentially complex work, beyond software product development where Scrum has its roots.** As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. **We use the word “developers” in Scrum not to exclude, but to simplify.** If you get value from Scrum, consider yourself included. As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in this document, may be found, applied and devised. Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses. Such tactics for using within the Scrum framework vary widely and are described elsewhere. **Scrum Definition** **Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems** In a nutshell, Scrum **requires a Scrum Master** to foster an environment where: 1. A **Product Owner orders the work** for a complex problem into a **Product Backlog**. 2. The **Scrum Team turns a selection of the work into an Increment** of value during a Sprint. 3. The **Scrum Team and its stakeholders inspect the results and adjust** for the next Sprint 4. _Repeat_ Scrum is simple. Try it as is and determine if its philosophy, theory, and structure help to achieve goals and create value. **The Scrum framework is purposefully incomplete**, only defining the parts required to implement Scrum theory. Scrum is **built upon by the collective intelligence of the people using it**. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions. Various processes, techniques and methods can be employed within the framework. Scrum wraps around existing practices or renders them unnecessary. **Scrum makes visible the relative efficacy** of current management, environment, and work techniques, **so that improvements can be made.** 1. Test Taking Tips 1. Read entire question before reviewing 2. Eliminate wrong answers 3. Use process of elimination 4. Analyze every option carefully 5. Make an educated guess 1. Correct option generally has more text 2. Core Aspects 1. Scrum Master is Facilitator Coach and Leader 2. Self Managing Team to adapt 3. Five Scrum Values of Commitment, Courage, Focus, Openness, and Respect ### Core Notes 2. Timebox is maximum time 3. Sprint review is not formal 4. Artifacts dont change, they are the set 3 5. Scrum values are: commitment, courage, focus, openness, and respect. 6. Scrum Team pursues one product goal 7. Sprint is one month or less 8. 1. Sprint Planning 1. one month, timeboxed to 8 hrs 2. why valuable 3. what can be done 4. how will it get done 9. Daily scrum 1. 15m 10. Sprint review 1. 4 hours for monthly, shorter for shorter 11. Spring Retro 1. 3 hours or less 12. All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful. 13. The Daily Scrum is for the Developers. It should not be used by external stakeholders to check progress. 14. During Sprint Planning the Scrum Team should be crafting the Sprint Goal based on the set of Product Backlog items selected for the Sprint. The Developers identify the necessary work to meet the Sprint Goal. 15. Scrum Team members do not have titles, and no sub-teams; such as testing, architecture, or operations are recognized. Accountability belongs with the Scrum Team as a whole, regardless of whether team members have specialized skills. 16. Length of a sprint 1. Short enough to keep the business risk acceptable to the Product Owner. 2. Short enough to be able to synchronize the development work with other business events. 3. One month or less 17. Scrum Terms change 1. Without a new vocabulary as a reminder of the change, very little change may actually happen. 2. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. 3. management may feel less anxious. 18. Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other setup makes it difficult for the Developers to determine what they should work on. 19. The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. 1. Developers manage the progress of work during a sprint 20. Asked to add item to current sprint 1. discuss with team 21. ### Agile Software Development Manifesto 1. Manifesto for Agile Software Development 1. We are uncovering better ways of developing 2. software by doing it and helping others do it. 3. Through this work we have come to value: 4. Individuals and interactions over processes and tools 5. Working software over comprehensive documentation 6. Customer collaboration over contract negotiation 7. Responding to change over following a plan 8. That is, while there is value in the items on 9. the right, we value the items on the left more. ### Data - Exam - https://www.scrum.org/assessments/professional-scrum-master-i-certification - [https://www.pmi.org/](https://www.pmi.org/) [https://www.scrum.org/professional-scrum-certifications] - (https://www.scrum.org/professional-scrum-certifications) - Guides - Best - Scrum Glossary https://www.scrum.org/resources/scrum-glossary - PSD Glossary - https://www.scrum.org/resources/professional-scrum-developer-glossary - Old - [https://scrumguides.org/](https://scrumguides.org/) [https://mplaza.training/exam-simulators/psm/](https://mplaza.training/exam-simulators/psm/) [https://www.scrum.org/open-assessments](https://www.scrum.org/open-assessments) [https://www.scrum.org/resources/scrum-glossary](https://www.scrum.org/resources/scrum-glossary) [https://www.udemy.com/course/complete-professional-scrum-master-training-exam-simulator/learn/lecture/20828472?start=0#overview](https://www.udemy.com/course/complete-professional-scrum-master-training-exam-simulator/learn/lecture/20828472?start=0#overview) - Study - 100 Agile Terms for PMP - https://www.youtube.com/watch?v=8Y96hNxP77E - Scrum Guide - https://youtu.be/G8jE3pGfGZE?si=y40Qzjacjaw_AKzc - Scrum in 20m - https://youtu.be/SWDhGSZNF9M?si=JavndbfP1iO2SIyL - 10 PSM 1 Questions - https://www.youtube.com/watch?v=PA2r2LbzZVs&list=PLII6Se70aL1iJS9-5k-fY1wdc0WcfxBaZ - Test - https://www.scrum.org/open-assessments/scrum-open