Agile Methodology Scrum Master PDF 2023

Agile Methodology Scrum Master Education and Training Solutions 2023 1 Project Life Cycle 2 The Brief of History of Scrum 3 Understanding the Basics 4 Scrum Overview Objective Understanding Traditional Versus Agile Project Management. Understanding of the Agile Manifesto...

Agile Methodology Scrum Master Education and Training Solutions 2023 1 Project Life Cycle 2 The Brief of History of Scrum 3 Understanding the Basics 4 Scrum Overview Objective Understanding Traditional Versus Agile Project Management. Understanding of the Agile Manifesto. Understand Scrum Overview. Project Life Cycle Project Life Cycle The series of phases that a project passes through from its start till completion. It provides the basic framework for managing g the project. Phases may be sequential, iterative, or overlapping. Predictive Iterative Incremental Agile Predictive Life Cycle Predictive Life Cycle Waterfall/Predictive/Plan-Driven/Traditional. Requires detailed plan at the beginning, changes are carefully managed. Business value is delivered at the end of the project, it’s suitable for construction projects. Analyze Design Build Test Deliver What is the Iron Triangle? The Iron Triangle of Project Management: also known as triple constraint, project management triangle, or flexibility matrix, models the constraints project managers work within on every project they oversee. Iron Triangle Time Quality Cost Scope Iterative Life Cycle Iterative Life Cycle Improve the product through successive Prototypes or Proof of Concepts. Suitable for complex projects with expected frequent changes and different stakeholders’ opinions about the final product. Iterative live cycles may take longer, as they are optimized for learning rather than speed delivery. Iteration 0 Iteration 1 Iteration 2 Iteration 3 Plan Plan Develop Project Develop Develop Test Setup Plan Test Test Release Feedback Feedback Product Incremental Life Cycle Incremental Life Cycle Customer cannot wait for the complete product but is willing to receive completed subsets of it. Optimized for speed delivery, small deliverables, and varying size increments. Analyze Design Build Test Deliver Increment 0 Analyze Design Build Test Deliver Increment 1 Analyze Design Build Test Deliver Increment 2 Scrum Life Cycle Scrum Life Cycle Combines Iterative and Incremental approaches to adapt to the high degree of change and deliver project value more often. Welcome and expect changes, and utilizes feedback loops, Continuous learning through discovery and experiment. Constantly Improve upon the project and the project work. Exercise What are the Differences Between Agile and Waterfall Models? Note: Upload your answer in the learning hub. Exercises The Brief History of Scrum What is the history of scrum? Hirotaka Takeuchi and Ikujiro Nonaka published the article, “New New Product Development Game” (the double “New” is indeed part of the title). The authors described a new approach to commercial product development that would increase speed and flexibility. Understanding the Basics What is a Scrum? Scrum is an agile framework In order to develop, deliver, and sustain complex products. Scrum is a framework, not a process, or a definitive method. A framework in which people can address complex problems, while productively and creatively delivering products with the highest possible value. What is a Scrum? Scrum tells you what needs to be done and lets you figure out how to do it, but does not tell you how to do things, at a high level, Scrum is lightweight and easy to understand, but it is difficult to master. What Scrum continuously improves : 1. The product 2. The team 3. The working environment. What is the characteristic of Scrum? Light Weight Simple to Understand Difficult to Master Scrum Overview Scrum Overview Where to use Scrum? 1. Develop, Release and enhance products. 2. Sustain products and renew. 3. Research and identify viable markets, and product capabilities. Where to use Scrum? 1. Develop, Release and enhance products. 2. Sustain products and renew. 3. Research and identify viable markets, and product capabilities. 1 Scrum Theory 2 Scrum Framework Components 3 Scrum Values 4 Scrum Events Objective Scrum Framework and Theory. Understanding the Three Pillars. Understanding the Scrum Roles. Managing the Release Planning. Understanding effective Users Stories. Scrum Theory Agile Manifesto Individual and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. Scrum Theory Scrum is founded on Empirical Process Control Theory or Empiricism. Knowledge comes from experience, making decisions based on what is known. Scrum employs an iterative and incremental approach to optimize predictability and control risk. Scrum Theory 3 Pillars of Empirical Process Control are: 1. Transparency 2. Inspection 3. Adaption Transparency For there to be transparency, those aspects need to be defined by a common standard, so that observers can understand what is happening. Inspection Detect undesirable deviations within Scrum artifacts and progress toward Sprint Goals frequently. Adaptation To minimize further deviations, it is essential to adjust the deviated process as soon as possible after inspection. Scrum Theory For Inspection and Adaptation, four scrum events are used ( Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective). Exercise Do we need to discuss the Scrum with the customer too, and receive its approval for the use of this method? A. Yes, because it changes our delivery method B. Yes, because it increases our return on investment C. No, because it is our internal way of managing the project D. No, because it is acceptable nowadays to use Scrum Exercise Solution: Correct Answer: A Explanation: In Scrum, we deliver the final product in small increments so that users can give feedback as they receive it, rather than waiting for the project to be finished to receive it all at once. Exercise In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams? Exercise Solution:  Understanding the product, the product vision, and the rules of the Scrum framework, the group divides itself into teams. Scrum Framework component Scrum Framework Components: 1. Team 2. Rules 3. Artifacts 4. Events 5. Roles Scrum Values Scrum Values When the values are embodied and lived by the Scrum Team, the Scrum pillars of Transparency, Inspection, and Adaptation come to life and build trust for everyone. Scrum Values Courage: Scrum team members have the courage to do the right thing and work on tough problems. Focus: Everyone focuses on the work of the Sprint and the goals of the Scrum Team. Scrum Values Commitment: People’s personalities commit to achieving the goals of the scrum team. Respect: Scrum Team members respect each other to be capable, independent people. Scrum Values Openness: the scrum team and its stakeholders agree to be open about all the work. Scrum Roles Scrum Team : 1. Scrum Master 2. Development Team 3. Product owner Scrum Team Characteristics : 1. Self-organized. 2. Cross-Functional. 3. Team Model is designed to optimize Flexibility, Creativity, and Productivity. Scrum Roles Delivers the product iteratively & Incrementally to maximize feedback opportunities. Incremental delivery of the Done product ensures the availability of a potentially releasable version of the product. Product Owner Aims to maximize the value of the product produced by the development team. Rather than a committee, it should be one person. Manages the Product Backlog. Product Owner Aims to maximize the value of the product produced by the development team. Rather than a committee, it should be one person. Manages the Product Backlog. As part of the Product Backlog, the product owner does the following Ordering the items. Optimizing the value of the work. Clearly expressing items. Ensure the Development Team understands the backlog at the needed level. Ensuring that is visible, transparent, clear, and shows what is next. As part of the Product Backlog, the product owner does the following Teams of professionals who work to produce releasable increments at the end of each sprint. The team should consist of 10 or fewer members. Empowered by the organization to organize and manage their own work. No titles (no tester, no graphic designer). Development Team characteristics Self-organized: No one tells him how to work. Cross-Functional with all skills necessary to finish the increment. Scrum Master A scrum master who Removes impediments, shields the team from interruption, Communicates continuously with project vision and will be like whom carries food and water to support the team. Scrum Master Scrum Master is a Servant Leader which is a leadership philosophy in Which a man or woman interacts with others with the purpose of attaining authority instead of power. The responsibility of promoting and supporting Scrum is to assist in understanding the theory, practices, rules, and values of Scrum. Scrum Master Helps everyone change these interactions to maximize the value created by the Scrum Team. Facilitating Scrum events as requested or needed. Management Focus VS. Leadership Focus Management Focus Leadership Focus Tasks People Control Empowerment Efficiency Effectiveness Doing things right Doing the right things Speed Direction Practices Principles Command Communication Scrum Master Services to Product Owner Ensure that goals, scope, and product domain are understood by the scrum team. Find techniques for effective Product Backlog management. Understanding and practicing agility. Helping the Scrum Team understand the need for clear and concise Product Backlog items. Scrum Master Services to Development Team Coaching the development team in self-organization and cross-functionality. Removing Impediments to the team’s progress, helping the team to create high- value products. Exercise We are going to assign Alice, our Sales Manager, to the role of Product Owner; but we are not sure about that, because John has recently joined X-CO and he is not an expert in software development. Should we choose another person instead? A. Yes, we need an expert on our specialist work, capable of communicating with the customer B. Yes, we need an expert on our specialist work, who is part of the Team C. No, he doesn’t need to be an expert on our specialist work, given that he gets expert help when needed D. No, he doesn’t need to be an expert on our specialist work, he just needs to be business oriented Exercise Solution: Correct Answer: D Explanation: Development Team handles all project's technical aspects, while the Product Owner should be mainly business-oriented. Scrum Events The sprint is the container for other events Sprint Planning Daily Scrums. Sprint Review. Sprint Retrospective. Scrum Events All events are time-boxed, once a sprint begins the duration is fixed and can’t be changed, Each event in scrum is an opportunity to inspect and adapt, any failure to include any of these events it’s reduced transparency. The Sprint The Sprint Time-boxed to 1 month or less to produce releasable increment. Each sprint may be considered as a project that has a goal of what is to be built. A new Sprint starts immediately after the conclusion of the previous one. The Sprint Throughout a sprint, progress toward a goal is inspected and adapted to ensure predictability. Sprints risk one calendar month of cost. Only the product owner has the authority to cancel the sprint if the sprint goal is obsolete. Incomplete Product Backlog items are re-estimated and put back on the PBL. Exercise We believe that it’s a good choice to have a day off after the first Sprint, but the company does not accept it. Who should discuss it with the company and try to get their approval? A. Product Owner B. Scrum Master C. Development Team D. All three roles Exercise Solution: Correct Answer: B Explanation: It’s the Scrum Master’s responsibility to resolve these kinds of issues. Exercise The CEO asks the Development Team to add a “very important” item to a Sprint that is in progress. What should the Development Team do? ​ Exercise Solution:  Inform the Product Owner so he/she can work with the CEO. Exercise One week through a four-week sprint, the Development Team realized that they won't be able to deliver half of the Sprint Backlog items. The Product Owner is not happy with this, because the customer is expecting most of those features to a release at the end of the Sprint. What is the best Exercises course of action as the Scrum Master? Exercise Solution:  Recommend the Product Owner to revise the order of Sprint Backlog items and let the developers continue with the best they can 1 Scrum Planning 2 Daily Scrum 3 Scrum Review 4 Scrum Retrospective 5 Scrum Artifacts 6 Scrum of scrum 7 Burn-Down Chart Objective Grooming The Product Backlog. Working on g The Sprint Backlog. Running The Sprint/Iteration. Sprint/Iteration Review. Sprint/Iteration Retrospective. Collecting Artifacts. Sprint Planning What about Sprint Planning? A sprint of one month is time-boxed to 8 hours. During the sprint planning meeting, a sprint goal is created. It is the scrum master's responsibility to ensure that the event is held, that the attendees understand its purpose, and that it stays on time. Sprint Planning? This meeting is based on the PBL items, the latest increment, and the past performance of the development team, During the planning meeting, the team should answer these two questions: In this sprint, what can we accomplish? What are the plans for completing the work? Daily Scrum Meeting Daily Scrum Meeting Developers on the Scrum Team participate in the Daily Scrum for 15 minutes each day. In order to reduce complexity, it is held every working day of the Sprint at the same time and location. In the Sprint Backlog, Product Owners or Scrum Masters can participate as Developers if they are actively working on the items. What are the Daily Scrums Meeting improves communications identify impediments promote quick decision-making consequently, eliminating the need for other meetings. In the Daily Scrum meeting should the team ask these questions What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do to help the development team to meet the Sprint Goal? Do I see any impediment that prevents me or the development team from meeting the Sprint Goal? Sprint Review Sprint Review A sprint of one month is time-boxed to 4 hours. Participants are invited by the product owner, including the Scrum Team and stakeholders. Rather than a status meeting, this is an informal gathering to share the increment and foster collaboration. After each Sprint, this meeting is held to assess the increments and develop the product backlog. What happened in the Sprint Review meeting? 1. The Product Owner explains what Product Backlog items have been done. 2. The Development Team demonstrates the Done work and answers questions about the increment. 3. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved. 4. The group collaborates on what to do next sprint. Sprint Retrospective Sprint Retrospective A one-month sprint is time-boxed to 3 hours. It's a great opportunity to inspect the relationships between people, processes, and tools. Identify improvements the scrum team can make to the way it works. Adapting the definition of done will reflect on product quality, it is an opportunity to enhance product quality. During the Sprint Retrospective, the team discusses 1. What went well in the Sprint? 2. What could be improved? 3. What will we commit to improving in the next Sprint? Sprint Artifacts Sprint Artifacts Product Backlog. Sprint Backlog. Increment. Sprint Artifacts As part of Scrum, artifacts act as indicators of work or value for a project, providing transparency and opportunities for inspection and adaptation. To maximize transparency, artifacts are specifically designed so that everyone has the same understanding of key information. A scrum master can detect incomplete transparency by Inspecting the artifacts Sensing patterns Detecting between expected and real results. Product Backlog Product Backlog Backlogs are ordered lists of all the features and functionalities that will be included in the product. Whenever changes need to be made to the product, this is the source of requirements. Value Description Order Estimate Value Product Backlog Attributes Product Backlog It is the Product Owner's responsibility to maintain the product backlog and to ensure that it contains relevant content, is available, and can be ordered, Is never complete, and is a living artifact. Features Functions Fixes Test Description Requirements Enhancement Product Backlog component Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Sprint Backlog Sprint Backlog It’s a combination of selected Product items backlog and plans to deliver the increment. One or more high-priority improvements identified in the previous meeting are included. The Development Team modifies the sprint backlog throughout the sprint. Sprint Backlog If new work is required, the development team adds it to the sprint backlog. Only the development team can change the sprint backlog during a sprint. The Development Team tracks this total work remaining at least for every daily scrum. Definition of Done Definition of Done Mabey the organization has a fixed structure, or the development team agreed on when the increments are done. When the increment achieves all the requirements and the sprint goal. The Scrum team should define how the project it’s done. Definition of Done This helps the development of how to choose features in each sprint backlog. All the team should agree on the same meaning of DOD. The Increment The Increment It is the summation of all the product backlog items that complete during a sprint and the value of the increments in all previous sprints. At the end of a sprint, the new increment must be “Done” which means it must be in useable condition and meet the scrum team DOD. The Increment 3 Feedback Unit of 2 value Value Feedback Unit of Unit of 1 value value Time Scrum Of Scrum Scrum of Scrum Multiple Scrum Teams work together on the same product. One product backlog, a product backlog attributes that groups items may then be employed. The Development Teams on all the Scrum Teams must mutually define the DOD. Burn-Down Chart Burn Down Chart A graphic representation of how quickly a team is working through a customer’s user stories. The tool captures the description of a feature from an end-user perspective and shows the total effort against the amount of work for each iteration. Burn Down Chart 12 10 8 6 4 2 0 21-Feb 22-Feb 23-Feb 24-Feb 25-Feb 26-Feb 27-Feb 28-Feb 1-Mar 2-Mar 3-Mar 4-Mar 21-Feb 22-Feb 23-Feb 24-Feb 25-Feb 26-Feb 27-Feb 28-Feb 1-Mar 2-Mar 3-Mar 4-Mar Planned 10 9 8 7 6 6 6 5 4 3 2 1 Actual 10 9 9 7 7 6 6 5 3 2 2 1 *Note: If the actual work line is above the ideal, it means more work is left than originally thought. In other words, the project is behind schedule. Ideal Work Remaining Line As its name suggests, the ideal work remaining line indicates the remaining work that a team has at a specific point of the project or sprint under ideal conditions. Managers use past data to estimate this baseline and draft a straight line across the burndown chart. The ideal work remaining line should always have a negative slope. Actual Work Remaining Line The actual work remaining line indicates the remaining work a team has at any point of the project or sprint. Unlike the ideal work remaining line, this is not an estimate, but rather a realistic depiction of the team’s performance. Actual work remaining lines are usually not straight as teams work at different paces as projects are completed. Exercise You are the Scrum Master of a new, to-be-developed product. Development is requiring 42 people. What is a good first question for you to suggest the group thinks about when forming teams? Exercises Exercise Solution:  How will we make sure all teams have the right amount of expertise? Exercise How much work must a Development Team do to a Product Backlog item it selects for a Sprint? Exercises Exercise Solution:  As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done Exercise User documentation is part of your definition of “Done”. Yet, there aren't plenty technical writers for the teams. Your Development Team doesn't have a technical writer. What should you do? Exercises Exercise Solution:  Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it. Exercise You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select conditions you should strive for in this scenario. Exercises Exercise Solution:  The product has one Product Backlog.  There should be only one Product Owner. Exercise If burn-down charts are used to visualize progress, what do they track? Exercises Exercise Solution:  Work remaining across time References 1- Scrum.org. (2019). The Scrum Guide. [online] Available at: https://www.scrum.org/resources/scrum-guide. 2- "Manifesto for Agile Software Development." Manifesto for Agile Software Development: http://www.agilemanifesto.org Overview of Database