Contents:

Free course: “Fast Start in Python"
Learn MoreThis document presents the process of working in a project team, including setting goals, planning the product, building communication between developers, and monitoring progress. Scrum rules are regularly updated, which is recommended for all Scrum teams. Currently, the fifth version of the methodology is available, and in this material, we will analyze its key aspects. The updates are aimed at improving communication within the team and streamlining development processes, which contributes to more effective achievement of goals.
About Scrum
Scrum is a popular project management methodology used in software development and other fields. It is based on the principles of agile development and is aimed at maximizing the effectiveness of teamwork. Scrum involves dividing work into short cycles called sprints, which allows for rapid adaptation to change and improvements to the product at each stage.
The key elements of Scrum are roles, artifacts, and events. The primary roles include the product owner, the Scrum Master, and the development team. The product owner is entrusted with managing the backlog, which allows them to prioritize tasks. The Scrum Master is responsible for adhering to Scrum principles and helping the team overcome impediments. The development team works on completing tasks, recording the results at the end of each sprint.
Scrum artifacts include the product backlog, the sprint backlog, and the increment. The product backlog is a list of all tasks and requirements for the product, while the sprint backlog includes the tasks planned for the current sprint. The increment is the result of the team's work, which is presented at the end of the sprint.
Scrum events include sprint planning, daily stand-ups, sprint review, and retrospective. These events help the team stay on the same page, track progress, and make necessary adjustments.
The Scrum methodology improves communication within the team and increases the quality of the final product. This project management system is suitable for various organizations seeking effective collaboration and quick adaptation to market changes. Scrum has become the standard in the field of agile development, facilitating the successful implementation of projects in conditions of uncertainty.
About Scrum
Scrum is a project management methodology used in software development and other fields. It is based on the principles of agile development and enables teams to effectively work on complex projects, ensuring rapid adaptation to change.
The main elements of Scrum include roles, artifacts, and events. Scrum distinguishes three key roles: the product owner, the development team, and the Scrum Master. The product owner is responsible for defining and prioritizing requirements, the development team implements these requirements, and the Scrum Master ensures adherence to the methodology and removes impediments.
The primary Scrum artifacts include the product backlog, sprint backlog, and increment. The product backlog is a list of all desired features and tasks, while the sprint backlog includes the tasks selected for completion in the current sprint. The increment is the team's deliverable for the sprint, which must be ready for demonstration.
Events in Scrum include sprint planning, daily standups, sprint reviews, and retrospectives. These events help teams stay aligned, track progress, and identify opportunities for improvement.
Scrum promotes transparency, improved communication, and higher product quality. The methodology enables teams to quickly respond to change and effectively manage risks, making it popular among organizations seeking innovation and high performance.
What is Scrum and why study it?
Imagine a residential building. Its walls, roof, and foundation form a frame that provides strength and stability to the entire structure. Without a reliable frame, it is impossible to carry out repairs or live comfortably in the apartment. The frame is the foundation upon which not only the physical space but also the comfort of the home is built. The correct selection and high-quality execution of frame elements play a key role in the durability and safety of the home.
A team project can be compared to the construction of a residential building. To achieve a successful result, it is crucial to define the rules by which the team will function in advance. These rules provide the structure and organization necessary for effective communication. Clearly established norms help avoid misunderstandings and promote harmonious project work, which ultimately leads to successful completion.
Scrum is an effective project management method based on a clear set of rules and principles. Adherence to these rules is critical, as deviations from them can lead to management errors and a decrease in overall team productivity. Organizations that decide to implement Scrum should closely monitor current updates to the methodology and guidelines. In this context, we offer a webinar on the basics of implementing the Scrum approach, which will help teams master key aspects and successfully integrate Scrum into their work.
In this overview, we present a complete guide that covers the key aspects and features of the new product. The guide contains detailed information on the functionality, benefits, and capabilities that will help users get the most out of the product. We will cover the main sections, including installation, configuration, and tips for optimal use. This guide will be an indispensable assistant for anyone looking to understand the new tool and get the most out of it. Read on to learn all the intricacies and secrets of working with the product.
- Scrum Guide 2020 in Russian and English.
- Presentation by Ken Schwaber and Jeff Sutherland - the guide's authors hold a two-hour stream and talk about the new guide.
- Articles and comments on the new guide from the scrum.org community.
The team is becoming a single mechanism
The old guide often led to conflicts of interest between the product owner and the development team. The product owner focused on business goals and customer needs, while the developers sought to avoid missed deadlines and minimize their responsibility for possible shortcomings. This contradiction created tension and worsened communication within the team, which negatively affected the quality of the final product. Streamlining the project management process and building transparent communication between all participants can help eliminate these issues and achieve more effective results.
Scrum 2017: Overview and Key Changes in the Methodology
Scrum is a popular project management methodology that is actively used in software development and other industries. In 2017, Scrum underwent significant changes and updates that contributed to improving its effectiveness. This year, attention was paid to adapting the approach to the requirements of modern teams and organizations.
One of the key aspects of Scrum in 2017 was increased interaction between team members. This helped improve communication and increase the speed of decision-making. Emphasis was also placed on regular retrospectives, which allow teams to analyze their work and make adjustments to achieve better results.
Furthermore, in 2017, the role of the Scrum Master was updated; now, they are not only responsible for process adherence but also actively contribute to the team's development. This change increased the level of involvement and responsibility of project participants.
Scrum 2017 also emphasized the importance of flexibility and adaptability in a rapidly changing business environment. Teams became more results-oriented and began to use new tools to improve productivity and work quality.
Thus, Scrum 2017 became an important milestone in the development of this methodology, offering new approaches and ideas for effective project management.
The product owner holds a meeting with the customer, at which they agree to launch a website and mobile applications for the iOS and Android platforms within two months.
Following the meeting, he organizes a team meeting at which he voices the technical requirements of the project, ignoring the developers' objections regarding the unrealistic nature of the goals.
The team begins work, focusing on speed of development instead of quality. As a result, everyone ends up at a disadvantage: the customer does not receive the desired product, the owner loses a client, and the developers are left without work. This approach negatively impacts the company's reputation and can lead to lost business opportunities. It's important to find a balance between quality and speed to satisfy the needs of all parties and ensure a successful outcome.
The new leadership effectively eliminates the conflict between developers and product owners. Owners are responsible for the final results, while developers play a key role in the planning process. They help avoid unrealistic expectations and alert to potential problems, ensuring the product is released without compromising quality. This approach promotes more harmonious interaction within the team and increases the chances of successful project completion.
The product owner has the ability to delegate their responsibilities to team members, but this does not relieve them of responsibility for the final result. If problems arise, they cannot shift the blame to another employee. It is important for the product owner to maintain control over processes and take an active role in project management to minimize risks and ensure the successful completion of tasks. The product owner's responsibilities include not only decision-making but also collaborating with the team to achieve shared goals.
Scrum 2020: The Evolution of Project Management
Scrum 2020 is the latest version of the Scrum methodology, which continues to evolve and adapt to modern business and technology requirements. In the context of constant changes in the world of software and project management, Scrum offers flexible approaches to organizing teams' work. This methodology allows for effective project management, ensuring quick adaptation to changes and regular feedback.
Key aspects of Scrum 2020 include improved communication between team members, an emphasis on self-organization, and continuous process improvement. Modern Scrum practices help teams achieve higher results by implementing Agile principles and focusing on the value they create for customers.
The implementation of Scrum 2020 promotes greater transparency, improved communication, and accelerated development processes. This makes it an ideal choice for companies seeking innovation and efficiency in a rapidly changing market.
The product owner meets with the customer and receives the task: a website, as well as mobile apps for iOS and Android, must be developed and launched within two months.
Following the meeting, a team meeting is held to discuss the technical requirements and take into account the developers' input. The product owner, together with the team, develops an alternative plan aimed at achieving the stated goals. For example, a decision is made to increase the project deadline from two to six months, which allows for a more efficient implementation of the tasks and takes into account all the development nuances.
The product owner organizes a new meeting with the customer to discuss alternative terms, taking into account the capabilities of their team. This leads to a win-win situation for all parties: the customer receives a high-quality product, the product owner strengthens the client's trust, and the team ensures stable employment and continued work on the project.
If an agreement cannot be reached, all parties still benefit. The client saves time, the product owner avoids unnecessary expenses on unprofitable deals, and the team doesn't have to sacrifice quality or produce low-quality work. This approach fosters more effective and productive collaboration.
The guide emphasizes the importance of cross-functionality in Scrum teams. Each team member must be sufficiently qualified to effectively solve assigned tasks. Incompetent employees can significantly slow down the development process and create uncertainty in product planning. Cross-functional teams facilitate faster adaptation to change and increase overall productivity, which is a key factor for successful project implementation.
A Scrum team is formed from highly qualified specialists, and in such a team, it is important that all members respect each other and value the work of their colleagues. Conflicts can seriously hinder collaboration between developers and disrupt team bonds. This can lead to the need for constant adaptation when transitioning to new projects and make it difficult to accurately predict work results. Creating a healthy team environment promotes more effective collaboration and increased productivity.

The team focuses on the product goal
Previously, when planning a sprint, the team asked two main questions: what needed to be done and how to get it done. The answers formed tasks that were distributed among the developers without a clear structure. This approach to planning often did not take into account the overall goal of the product, which could lead to delays in development due to the implementation of unnecessary activities. Effective sprint planning involves a deeper connection with the product goals, which allows the team to focus on truly important tasks and optimize the workflow.
Scrum 2017: The Evolution of the Methodology in Project Management
Scrum continued to evolve in 2017, strengthening its position in the world of project management. This methodology has become an integral part of the Agile approach, enabling teams to effectively adapt to change and quickly achieve their goals. In 2017, many organizations began implementing Scrum, recognizing its benefits in increasing productivity and improving team communication.
Key aspects of Scrum in 2017 included an emphasis on team self-organization, regular meetings, and an iterative development process. This helped improve the quality of the final product and customer satisfaction. The adoption of Scrum also contributed to the growth of Scrum Master and Product Owner certifications, emphasizing the importance of professional training in this area.
The use of Scrum in 2017 continued to prove its effectiveness across various industries, including information technology, manufacturing, and services. Many companies noted that the use of Scrum helps not only with project management but also in creating a culture of openness and collaboration.
In conclusion, Scrum confirmed its relevance and importance in modern business in 2017, remaining one of the most popular project management methodologies.
The task is to develop and launch a website with mobile applications for iOS and Android platforms within six months. This deadline is critical, as after it, the client plans to begin an advertising campaign and sell their services through these applications. To successfully implement the project, it is necessary to ensure high-quality execution of all development stages, including design, programming, and testing, in order to deliver a functional and user-friendly product to the client on time.
The team breaks the task into six sprints and determines the sequence of execution. Each sprint focuses on a specific aspect of the task, which allows for effective process management and achievement of goals. This approach helps the team better organize the workflow and also provides more transparent progress tracking. An optimized sprint structure facilitates higher-quality project implementation and allows for quick changes when necessary.
The first sprint includes the website development process. This stage involves creating the structure, design, and functionality of the resource. The focus is on the user interface, ease of navigation, and adaptability for various devices. SEO optimization is also important to ensure the site is visible in search engines. The first sprint should result in a prototype, which will serve as the basis for further work on the project.
Second sprint: website testing. At this stage, it is important to conduct a comprehensive check of the functionality and performance of the web resource. The focus is on identifying errors, improving the user interface, and ensuring compliance with modern standards. Testing should include both automated and manual methods to ensure high-quality website performance. After testing is complete, the results should be analyzed and the necessary adjustments made to optimize the site.
The third sprint involves developing an iOS app. The focus is on creating a user-friendly interface and improving the user experience. The team is working to optimize the app's performance, ensuring its stable operation across various devices. Integration with external services and the implementation of necessary functionality are also being considered. The result of this work is planned to be a high-quality iOS app that meets modern standards and user needs.
The fourth sprint focused on testing the iOS app. This stage includes checking the functionality, performance, and security of the app on the iOS platform. Testing is carried out with the aim of identifying and eliminating potential errors and shortcomings, thereby ensuring a high-quality product. Various testing methods are used during the testing process, such as unit testing, functional testing, and user interface testing. In addition, it is important to consider the app's responsiveness across various devices and operating system versions. As a result of this sprint, we have a stable and reliable iOS app ready for launch.
The fifth sprint is dedicated to developing the Android app. At this stage, the team will focus on creating functionality, optimizing the user interface, and ensuring the app's stable operation across various devices. It is important to consider all design and performance requirements to ensure the app is user-friendly and engaging. Testing will also be conducted to identify and fix bugs, ensuring the app's reliability and security. Effective Android app development in this sprint will be a crucial step towards a successful product launch.
Sprint 6: Android App Testing
During the sixth sprint, we focused on testing the Android app. The main goal of this stage was to identify and fix potential bugs and improve the user experience. We conducted comprehensive testing, including functional testing, device compatibility, and performance.
Functional testing ensured that all key app features function correctly and meet user requirements. Compatibility was tested on various smartphone and tablet models with different versions of the Android operating system, ensuring stable app operation on the widest possible range of devices.
Additionally, we conducted performance testing to ensure fast loading and a responsive interface. The testing results allowed us to identify weaknesses and make the necessary improvements. As a result, we prepared the application for the next stage – the implementation of new features and updates.
Thus, the sixth sprint was an important step in the process of creating a high-quality Android application that meets modern standards and user expectations.
Problems can arise even if developers initially perform their work well. Delays in the development of a mobile application can result in the client not receiving the expected result. It is important that the development process is efficient and meets the established deadlines, otherwise it can negatively impact the project as a whole. The key factor in successful implementation is meeting deadlines and high-quality work by the development team.
The new guide focuses on the question: "What is the value of a sprint?" Each sprint should be aimed at achieving product goals. Sprints are an important project management tool, allowing teams to effectively plan and implement tasks. They help ensure regular product testing and adaptation, which contributes to its improvement and higher quality. It is important that each sprint delivers tangible value that aligns with the project's strategic goals and meets user needs.
- If the product's goal is clear, the team can move on to planning and thinking about the list of tasks for each sprint.
- If the goal is unclear, the team needs to clarify the task and gather additional information about the product.
- If the sprint goal does not align with the product goal, then such a sprint is unnecessary - it is unnecessary work that can be avoided.
Once the team has defined the goals, it is necessary to take the first step. It is crucial to focus on the tasks that will bring the greatest value to the product. This will allow for the efficient use of resources and ensure the successful development of the project.
Scrum 2020 is an updated version of the project management methodology, which continues to evolve in response to rapidly changing market conditions. The implementation of Scrum allows teams to effectively organize their work and achieve high results. Key aspects of Scrum 2020 include improved adaptability, shorter development cycles, and an emphasis on team collaboration. These changes are aimed at increasing productivity and the quality of the final product. Using Scrum 2020 helps companies respond more quickly to customer needs and optimize development processes, which is an important competitive advantage in modern business.
The project goal is to develop and launch a website with mobile applications for iOS and Android platforms within six months. This deadline is critical, as after this period, the client intends to begin an advertising campaign and offer their services through these applications. The development must include all necessary functionality and ensure ease of use for users. It is important to think through a promotional strategy and interaction with the target audience in advance to ensure a successful launch and further development of the application.
We define goals that can be achieved within one sprint. Setting clear and measurable goals allows the team to focus on key tasks and increase productivity. It is important that the goals are achievable and aligned with the overall project plan. This will not only help to successfully complete the sprint but also ensure the continued development of the project. Properly formulating goals promotes a better understanding of the tasks and increases team motivation.
The first sprint includes website development. At this stage, the team focuses on creating the structure, design, and functionality of the web resource. The main focus is on choosing technologies, developing the user interface, and ensuring the site's responsiveness for various devices. It is also important to conduct initial search engine optimization to ensure good visibility in the future. During the website development stage, it is necessary to consider the needs of the target audience and implement UX/UI best practices. This will create a user-friendly and attractive resource that will effectively fulfill its purposes.
The second sprint is dedicated to website testing. As part of this stage, we will conduct a comprehensive check of functionality and user experience. The main focus will be on identifying and fixing errors, as well as optimizing performance. Testing includes checking all key elements, such as navigation, forms, links, and the responsiveness of the design on different devices. We will also evaluate page loading speed and the correct display of content. The goal of this sprint is to ensure a high level of quality and usability of the website for end users. The testing results will help in further improving the website and increasing its competitiveness.
The third sprint is dedicated to the development of the iOS application. During this stage, we will focus on creating a functional and user-friendly interface, integrating the necessary features, and ensuring the stable operation of the application on various Apple devices. We will also conduct testing to identify and eliminate potential errors to ensure the high quality of the final product. The development of an iOS application involves the use of modern technologies and approaches, which will ensure its competitiveness in the mobile application market.
Sprint Four: iOS Application Testing
The fourth sprint focuses on testing the iOS application. This process verifies functionality, performance, and user experience. Testing includes both automated and manual methods to ensure the high quality of the application. Important aspects of this stage are identifying and eliminating errors, as well as checking compatibility with different iOS versions and devices. Effective testing will help ensure that your app runs smoothly and meets user expectations.
Sprint 5 is dedicated to developing an Android app. In this phase of the project, the team will focus on creating functionality, improving the user interface, and optimizing the app for the Android operating system. During this sprint, requirements will be analyzed, screen layouts will be developed, and key features will be implemented. Testing will also be conducted to identify and eliminate potential errors, ensuring the stability and high quality of the app. The focus will be on usability and performance to ensure the app meets modern standards and the requirements of Android users.
Sprint 6: Creating an Android App. In this phase, we will focus on developing a high-quality mobile app for the Android platform. Key tasks include designing the user interface, implementing functionality, and optimizing performance. We will use modern tools and technologies, such as Kotlin and the Android SDK, to ensure the app is user-friendly and performs efficiently. The app should be responsive, intuitive, and comply with best development practices. Regular checks and testing will be included during this sprint to ensure the app is stable and reliable.
The customer emphasized the importance of mobile apps, which underscores the need to gather more information about the product. Mobile applications are critical to the functioning of a business. Although a website also plays a role, its primary functions are secondary: it serves as an information resource about the company and an additional platform for downloading mobile applications.
We define the product's purpose, set priorities, and form an effective action plan.
Phase One: Creating an iOS Application. This sprint will focus on the design and development of functionality for the iOS platform. The main focus will be on the user interface, performance optimization, and integration of the necessary APIs. The team will focus on the implementation of key features that ensure the usability and security of the application. Upon completion of the first sprint, we will have a working version of the iOS application, ready for testing and collecting user feedback.
Sprint Two: Testing the iOS Application. In this phase, we will focus on evaluating the functionality and performance of our application developed for the iOS platform. The main tasks include checking all key functions, identifying and fixing bugs, and optimizing the user interface. We will use both automated and manual testing methods to ensure the high quality of the product. Completion of the second sprint will allow us to improve the user experience and prepare the application for market release.
Sprint 3: Android application development. During this phase, we will focus on creating a functional and user-friendly application for the Android platform. The main focus will be on the user interface, performance optimization, and ensuring a high level of security. Using modern technologies and development tools, we will strive to create an application that will provide the best user experience. During the development process, we also plan to test functionality and eliminate potential errors to ensure stable operation of the application on various devices running the Android operating system.
Sprint 4: Android application testing involves a comprehensive study of the functionality and performance of the application on the Android platform. During testing, special attention is paid to identifying errors, user interface issues, and ensuring the stability of the application on various devices. Effective testing helps ensure high product quality, improves user experience, and contributes to the successful launch of the application. In this sprint, the team will focus on manual and automated testing, as well as analyzing user feedback to make any necessary improvements.
Sprint 5 includes the website development and testing phases. During this phase, the team will focus on creating functionality, design, and user interface. All website elements will also be thoroughly tested to ensure stable operation and compliance with requirements. Identifying and fixing bugs, as well as optimizing performance, are important aspects of this process. Completion of Sprint 5 will prepare the website for the next launch and ensure the high quality of the final product.
Sprint 6 includes reserve time for refining the mobile apps. This will improve the functionality and performance of the apps, as well as eliminate potential bugs and shortcomings. Reserve time is an important stage in the development process, as it allows the team to focus on optimizing the user experience. During the sprint, specialists will be able to implement updates, conduct testing, and ensure the app meets current requirements. Thus, the sixth sprint will be a key moment for improving the quality of mobile solutions.
Understanding the product's goal helped adjust the sprint objectives. We prioritized the development of mobile applications and allocated time for their refinement, allowing the team to focus on the core task. This is an effective project management approach that improves the quality of the final product and user satisfaction.
We lowered the priority of the secondary task of website development and postponed it for later. Having a website is not critical for a business, while well-developed mobile applications play a key role in its success. Without such applications, the site becomes an ineffective tool and only takes up resources.
Focusing on product goals allows the team to avoid constant overload, when developers spend time writing code while being in the office all day, but do not create value. Scrum principles eliminate unnecessary tasks, promoting more efficient work and increasing team productivity. This allows you to focus on the most important aspects of development, which ultimately leads to a high-quality and in-demand product.
The guide's authors argue that releasing a quality product on the first try is challenging. Instead of wasting effort, they recommend dedicating time to refining key features. The optimal approach is to release and test multiple versions of the app, focusing on five foundational features, rather than waiting for one perfect version with ten features. This method allows you to quickly identify shortcomings and improvements, which ultimately contributes to the creation of a more successful and in-demand product.

The team has the right to self-management and to abandon formal procedures.
The previous Scrum implementation guide wasn't precise enough. If a team tried to apply Scrum without a certified Scrum Master, it could lead to a misunderstanding of key aspects of the methodology. This could result in formal rituals that didn't contribute to effective work, but rather created additional obstacles. That's why it's important to have a qualified specialist who can correctly interpret Scrum principles and ensure the successful implementation of the methodology within the team.
Scrum 2017: Fundamentals and Application of the Agile Methodology
Scrum is one of the most popular Agile methodologies, which has been actively used in project management since 2017. It allows teams to effectively organize their workflow, adapt to changes, and ensure high quality of the final product. The core principles of Scrum include iterative development, regular team collaboration, and continuous process improvement. Implementing Scrum helps accelerate time-to-market and increase customer satisfaction through team flexibility and transparency.
In 2017, Scrum continued to evolve, adapting to new challenges and requirements, making it an even more relevant tool for organizations seeking innovation and effective project management.
Management suggested the team hold daily 15-minute meetings to synchronize and discuss sprint goals. These short meetings will help increase efficiency, improve communication, and ensure tasks are completed within the allotted time. Regular meetings facilitate a clearer understanding of the current project status and allow the team to quickly respond to emerging issues and changes.
During the meeting, each participant answers three key questions: what they completed the day before, what tasks they plan to complete today, and what issues are preventing them from achieving their goals. This format allows for effective progress tracking, identifying obstacles, and adjusting plans to ensure successful completion of tasks.
The team is required to maintain daily communication, adhere to the established schedule, and jointly resolve any issues that arise. This ensures effective collaboration and allows for a timely response to any challenges. Regular communication will help avoid misunderstandings and increase overall productivity.
The team met daily and, instead of discussing work tasks, focused on adhering to the 15-minute time limit set in the manual. This approach became a ritual that facilitated efficient use of time and increased productivity. This time limit allowed the team to be more focused and avoid protracted discussions, which in turn positively impacted task completion and goal achievement.
To conduct the meeting effectively, one participant asked everyone the same questions, receiving concise and mechanical answers. This saved time and allowed the focus to be on the key aspects of the discussion. It is important that the communication format facilitates a clear understanding of each participant's positions, which, in turn, increases the productivity of the meeting.
Tasks 15 and 20 have been completed.
Planned tasks include the completion of tasks 25 and 30.
There are no problems, or current issues are being resolved.
The team was losing valuable time daily and not achieving significant results. Developers faced problems alone, while managers formed the mistaken impression that work on the product was progressing according to plan. This led to a decrease in efficiency and a deterioration in the quality of the final result. It is necessary to improve communication and optimize work processes to ensure real progress and improve collaboration within the team.
The new management abolishes all formal procedures and gives the team the opportunity to use any tools that are useful for their work. Team members can independently choose tools depending on specific tasks, which contributes to increased efficiency and improved work results. This approach allows for flexible adaptation to change and finding optimal solutions to achieve goals.
Scrum 2020 is an updated version of the popular project management methodology used in agile development. Scrum 2020 focuses on flexibility, team collaboration, and continuous process improvement. This version includes new practices and recommendations aimed at increasing team efficiency, adapting to change, and improving the quality of the final product. Scrum 2020 also emphasizes the importance of the Scrum Master and Product Owner in ensuring the successful completion of projects. Using Scrum 2020 enables teams to more effectively address the challenges of modern business and deliver maximum value to customers.
The team meets daily for morning meetings to discuss product-related issues and problems in an open-ended manner. Meeting time is not limited and can vary from five minutes to several hours, depending on need. At each meeting, participants share their observations and problems and jointly seek possible solutions. If no problems arise, the team continues its work. Such regular discussions contribute to product improvement and increased team efficiency.
The team focuses on effective problem solving and uses meetings to streamline the development process. This accelerates decision-making and improves communication within the team, which in turn facilitates faster project delivery.
The Scrum team has complete freedom to organize product development and track progress. A key aspect is adherence to established rules, which must be binding on all process participants. This ensures effective team collaboration and contributes to the achievement of goals. Proper work organization and strict adherence to Scrum rules help improve productivity and the quality of the result.

Hiring a Scrum Master to implement the new Guide makes sense, but it depends on the current work of the team. If a team is struggling with process organization, collaboration, or task completion, a professional Scrum Master can significantly improve the situation. Their experience and knowledge will help implement Scrum principles, optimize workflows, and increase team productivity. A Scrum Master can also train team members in the basics of agile, which will provide a deeper understanding of the methodology and its application in their work. It is important to assess the team's readiness for change and the availability of internal resources for independent mastery of the Guide. If such resources are lacking, engaging a Scrum Master will be a justified step for successful implementation and achieving high results.
- If the team uses a classic Waterfall approach, with members working on the project for 30 years and no one willing to change anything, then independently transitioning to agile project management methods is unlikely. In this case, it is important to promptly invite a Scrum Master capable of changing the system.
- If we are talking about a newly formed team that is ready to try and experiment, then the Scrum Master can be replaced by a team lead or one of the managers.
The Scrum Master is a key role in the Scrum team, and any member can assume this role, but a deep understanding of the methodology is necessary for successful fulfillment of these responsibilities. To effectively perform the functions of a Scrum Master, it is important to study the basics of Scrum, read specialized books, familiarize yourself with the latest version of the Guide, and complete training sessions. Without this knowledge and skills, successful implementation of the role will be difficult.
Establishing a Scrum process from scratch is one of the most difficult tasks. In case of significant changes in the team, it is recommended to consider hiring a Scrum Master. It is important that at the beginning of the Scrum implementation there is a specialist who is well versed in this methodology and knows how to apply it correctly. Such a professional will be able to clearly convey the core principles and ideas of Scrum to each team member, which will improve team efficiency and help everyone better understand their role in the process. An effective Scrum Master will not only ensure an understanding of the methodology but also support the team in adapting to new conditions, which will significantly simplify the implementation of Scrum and increase the likelihood of project success.
If the changes are minor, the team is new, and the manager has experience with Scrum, you can try to manage it yourself. If the implementation of Scrum has simplified project management and increased their efficiency, this can be considered a success. The important result should be not only the creation of a functioning process, but also the delivery of a finished product. It is important to remember that adherence to Scrum rules should not be an end in itself; The main thing is to achieve real results and improve the quality of the team's work.

Victoria Pisarenko is a name that is becoming increasingly well-known in various fields of activity. She demonstrates outstanding abilities and dedication to her work, which inspires many. With each new project, Victoria confirms her professionalism and desire for high results. Her work is marked by creativity and originality, making it unique and memorable. In an increasingly competitive world, Victoria Pisarenko stands out as a talented specialist who is able to achieve goals and make a significant contribution to her field.
Scrum Master and Agile Project Manager in Munich, specializing in projects in the automotive industry. Founder of Victoria's Business Secrets Academy, where she teaches methods of effective project management and the implementation of Agile approaches in business. She has experience in optimizing work processes and increasing team productivity in a rapidly changing market.
Scrum emerged from practical experience, observations, and team experiments. Updating the Scrum Guide is an important step, as even small changes help to better understand and effectively apply this framework. Improvements to the Guide contribute to a clearer understanding of Scrum principles and its values, which, in turn, enables teams to achieve better results.
The new Guide introduced the concept of Product Goal, which was a significant change. This innovation is aimed at improving the team's understanding of the overall project goal. At the same time, three questions that often led to mechanical execution of tasks and a decrease in work efficiency have been removed from the Daily Scrum. Instead, the emphasis has shifted to more conscious interaction between team members, which prevents them from turning into "zombies" performing routine actions without a real understanding of what is happening. These changes contribute to increased productivity and team engagement, which in turn leads to more successful project delivery.
I would like to draw attention to three important changes that are not so obvious at first glance. These changes can significantly impact the perception and effectiveness of the content.
- Scrum has officially moved beyond software development: the Guide has removed specific terminology. It's great that more teams can see the opportunity in trying Scrum.
- The Scrum Master is no longer a servant leader. This term sounds strange in Russian translation due to the subtle differences between "serve" and "maintain." The Scrum Master is now "a true leader who serves the Scrum Team and the entire organization."
- Also, the Scrum Master no longer facilitates Scrum Events, but "ensures that they occur, are positive, productive, and stay within time limits." This is a very important change that corrects the misinterpretation of the Scrum Master's responsibility as "leading" meetings."
The new Guide encourages teams and their leaders to go back to the source and ask themselves: To what extent are we preserving the spirit of the game?
Of course, I'm happy to help you with the text. Please provide the source text you would like to rework for SEO.

Yulia Anikeeva is a professional in her field, with significant experience and knowledge. She successfully works on projects that require a high degree of responsibility and creativity. Yulia demonstrates initiative and actively strives for self-development, making her a valuable team member. Her approach to work is based on thorough analysis and the search for optimal solutions, which contributes to achieving high results. Thanks to her skills and ability to work with people, Yulia Anikeeva is a reliable partner for clients and colleagues.
I am a Scrum Master with experience at companies such as Alfa-Bank, AlfaStrakhovanie, Rostelecom, and Croc. I have a deep knowledge of Scrum methodology and successful experience implementing Agile approaches in large organizations. My work involves coordinating teams, optimizing processes, and improving work efficiency. I strive to create a productive and motivating atmosphere for achieving high results.
Author's opinion: the new guide is a way to monetize the services of Scrum Masters
While preparing this material, I got the feeling that the Scrum Guide 2020 was created for the purpose of a marketing strategy - the document presents several useful updates, but most of the changes are aimed at popularizing Scrum as a methodology. Let's consider several arguments that may cause different opinions.
Scrum for everyone. The new guide is presented in simple and accessible language to attract a wide audience. The authors excluded complex IT terms and proposed Scrum as a universal tool suitable for any company. The methodology allows for breaking down work on a product into stages and effectively distributing tasks between small teams, which contributes to increased productivity and improved work quality. Scrum is becoming an accessible and understandable solution for organizations seeking flexibility and efficiency in project management.
Scrum has become more adaptable, allowing teams to use its principles more freely. Along with simple and clear language, the guide offers flexible interpretations of all aspects of Scrum. For example, in the previous section, we discussed daily meetings, where instead of a strict 15-minute time limit and three fixed questions, the team can discuss all necessary topics in a format convenient for them. This approach promotes a more open exchange of ideas and improved collaboration within the team, which ultimately increases work efficiency.
Scrum can be dependent on the Scrum Master. Simple language and a free interpretation of the rules are acceptable when the team is already experienced with Scrum. In this case, they can adapt the methodology to their needs, replacing outdated rules and continuing to move towards their goals. However, when a team is just beginning to familiarize itself with this methodology, a difficulty arises: members understand the desired result, but do not know how to achieve it. This leads to a dependence on Scrum Masters—specialists who, according to the methodology's authors, are responsible for ensuring the implementation and correct application of Scrum principles within teams. Dependence on the Scrum Master can hinder a team's independent development and prevent it from making its own decisions. To avoid this, it is important to develop an understanding of Scrum principles among all team members, which will allow the team to more effectively adapt the methodology to its tasks and work more autonomously. The Scrum Master performs many key responsibilities that facilitate the team's effective functioning within the Scrum methodology. The Scrum Master's primary responsibilities include organizing and facilitating all Scrum ceremonies, such as sprint planning, daily standups, reviews, and retrospectives. They also ensure adherence to Scrum principles and help the team overcome obstacles that may hinder the achievement of sprint goals. The Scrum Master acts as a mentor to the team, teaching them Agile and Scrum methods, and facilitating the development of communication between team members and other stakeholders. In addition, the Scrum Master actively works to improve processes and increase the team's productivity, using various tools and techniques for analyzing and optimizing the workflow. Thus, the Scrum Master plays a critical role in the success of projects based on the Scrum methodology.
- Responsible for the team's effectiveness: organize coaching, establish self-management, monitor the cross-functionality of developers, eliminate organizational barriers.
- Ensure that project work is not missed, is not scattered on unnecessary tasks, does not lose quality and is consistent with the product's goal.
- Help product owners define the main goal, prepare a list of tasks for each sprint and improve communication with customers.
- Build communication between multiple teams.
- Promote Scrum.
A Scrum Master is a sought-after profession, but there is still a shortage of qualified specialists on the market. For some teams, hiring a Scrum Master may not be cost-effective. As a result, if a company doesn't intend to implement Scrum across all its departments and can't afford the expense of a Scrum Master, it becomes difficult to accurately interpret the principles and practices of the new guide. Without the right approach, Scrum risks becoming a set of ineffective formal rituals, which reduces its real value and effectiveness in project management.
In my opinion, the guide's authors intentionally made it abstract, which could lead to commercial gains from re-certifying existing Scrum Masters and certifying new specialists. This negatively impacts the team leads of many IT teams, who may find themselves without the support of Scrum Masters and unable to implement the methodology, even if they have the desire to do so. A shortage of qualified Scrum Masters can slow down the adoption of Agile approaches and reduce the overall effectiveness of teams. It is important that the methodology is easy to implement and understand, otherwise it can lead to ineffective processes and loss of competitive advantage.


