Agile Principles form the foundation of Agile methodologies, emphasizing flexibility, collaboration, and customer-centric development. Key principles include prioritizing customer satisfaction through early and continuous delivery of valuable software, welcoming changing requirements even late in development, and delivering working software frequently. Agile encourages close, daily cooperation between business stakeholders and developers, building projects around motivated individuals, and promoting sustainable development. The principles also highlight the importance of simplicity, self-organizing teams, and regular reflection on how to become more effective, fostering an environment of continuous improvement and responsiveness to change.

Scrum principles are the foundation on which the Scrum framework is based. The principles of Scrum can be applied to any type of project or organization, and they must be adhered to in order to ensure appropriate application of Scrum.

The aspects and processes of Scrum can be modified to meet the requirements of the project, or the organization using it, but Scrum principles are non-negotiable and must be applied as described in the framework presented in A Guide to the Scrum Body of Knowledge (SBOK® Guide). Keeping the principles intact and using them appropriately instills confidence to the user of the Scrum framework with regard to attaining the objectives of the project.

• Empirical Process Control—This principle emphasizes the core philosophy of Scrum based on the three main ideas of transparency, inspection, and adaptation. Empirical process control aids learning through experimentation, especially when the problem is not well defined or when there are no clear solutions.
• Self-organization—This principle focuses on today’s workers, who deliver significantly greater value when self-organized, and this results in better team buy-in and shared ownership; and an innovative and creative environment which is more conducive for growth.
• Collaboration—This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project delivery as a shared value-creation process with teams working and interacting together, as well as with the customer and other business stakeholders, to deliver the greatest value.
• Value-based Prioritization—This principle highlights the focus of Scrum to deliver maximum business value, from early in the project and continuing throughout.
• Time-boxing—This principle describes how time is considered a limiting constraint in Scrum and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, Sprint Review Meetings, and Retrospect Sprint Meetings.
• Iterative Development—This principle defines iterative development and emphasizes how to better manage changes and build products that satisfy customer needs. It also delineates the Product Owner’s and organization’s responsibilities related to iterative development.

Scrum principles are the core guidelines for applying the Scrum framework and should mandatorily be used in all Scrum projects. The Scrum aspects and processes, however, can be modified to meet the requirements of the project or the organization on a project to project basis by the Scrum Core Team.

The Scrum Master Certification serves as a vital credential for professionals aiming to master Agile principles and practices. This certification validates a Scrum Master's expertise in guiding teams through Agile frameworks, facilitating collaboration, and ensuring the seamless implementation of Scrum processes. By achieving this certification, individuals demonstrate their ability to effectively manage and support Scrum teams, promote continuous improvement, and deliver high-value products in iterative cycles. The SBOK™ Guide provides a comprehensive understanding of Scrum methodologies, preparing candidates to tackle real-world challenges and lead their organizations towards Agile transformation with confidence and proficiency.

As with all other additional certifications which ensure success in a Project according to the business needs, Scrum also provides assurance that the end result of a product or service will always be better than the initial stages of its development. This is due to the fact that quality is emphasized as top priority in Scrum to meet the Acceptance Criteria and satisfy the business needs of the Customer.

In order to ascertain that a project will meet the requirements of quality as defined, in Scrum, the process adopted is that of continuous improvement in which the teams have the benefit of learning from experience. There will also be regular interaction with business stakeholders for keeping the Prioritized Product Backlog constantly updated with any changes in requirements. This Product Backlog will be never complete until the project is closed or terminated. Unless the requirements are changed according to the customer, then internal and external changes will have to be brought about for allowing the team to continue working and adapt according to the new developments.

As the work has to be completed as increments in the duration of Sprints as per the Scrum rule, the advantage is that errors, faults or defects can be located in the early phases by continuous tests of quality while the final result of the product/ service are on the stages of completion. Another advantage is that other valuable tasks related to quality such as testing, development and documentation will be completed in the same phase, that is, same Sprint also by same staff members. By following this method, a project can be ensured of specific quality in any release product or service as per part of a particular Sprint. The end product or deliverables from these kind of Scrum projects which can be worked on, are usually described as “Done.”

By following the principles of Scrum, continuous improvement with consistent testing of quality can increase the chances of attaining the anticipated levels ofquality in a Scrum project. Regular interaction between the business stakeholders which includes users and customers and Scrum Core team can decrease the gap regarding the expectations and actual deliverables of the product by valuable suggestions at the end of each Sprint.

Valuable suggestions and guidelines can also be obtained from Scrum Guidance Body regarding the quality which might prove useful for all the Scrumprojects in the organization. The Scrum Guidance Body usually consists of a group of experts typically involved in defining objectives that are related to government regulations, security and various organizational parameters.

Scrum Master certification training encompasses a deep understanding of Agile principles, which are fundamental to successful project management in today's dynamic business environment. Agile principles focus on customer satisfaction through early and continuous delivery of valuable software, embracing change for competitive advantage, delivering working software frequently, collaborating closely with customers, and fostering a culture of self-organizing teams. Scrum Master certification training not only equips professionals with the technical knowledge of Scrum framework but also instills the core Agile values of communication, collaboration, flexibility, and responsiveness, empowering them to lead teams effectively and drive successful project outcomes.

Why Choose SCRUMstudy for Scrum Certifications?

Comprehensive Certification Programs

SCRUMstudy provides a range of certification levels catering to beginners to advanced practitioners in Agile and Scrum. These include Scrum Fundamentals Certified (SFC), Agile Master Certified (SAMC), and Scrum Product Owner Certified (SPOC) among others.

Global Recognition and Credibility

With a presence in over 150 countries, SCRUMstudy certifications are respected worldwide, enhancing career opportunities and credibility in Agile project management.

Benefits of SCRUMstudy Certifications

Career Advancement

Achieving a SCRUMstudy certification demonstrates mastery of Agile principles, making professionals more competitive in the job market.

Practical and Applicable Skills

Certification exams from SCRUMstudy emphasize practical knowledge and application of Agile frameworks, ensuring candidates can implement Agile methodologies effectively in real-world scenarios.

Choosing SCRUMstudy for Scrum certifications ensures not only validation of skills but also opens doors to global career opportunities in Agile project management. Whether you are new to Agile or a seasoned professional, SCRUMstudy offers a structured path to enhance your expertise and career prospects in Agile methodologies.

The Scrum training community embodies a dynamic ecosystem where knowledge meets practice in the realm of Agile project management. It serves as a hub where aspiring Scrum practitioners, seasoned Agile coaches, and certified Scrum Masters converge to exchange insights, refine methodologies, and cultivate expertise. This community thrives on collaborative learning, with certified trainers imparting core Scrum principles and practices through interactive workshops and certification programs. By fostering a culture of continuous improvement and adaptation, the Scrum training community not only equips individuals with technical skills but also instills a mindset of agility and innovation crucial for navigating today's complex business landscapes.

When an organisation is trying to adopt Scrum, this is the biggest question that comes in their mind. Since traditionally the Scrum suggests that the Scrum Teams should ideally be 6-8 Member team, how will this work for humongous projects which have huge team some time in 100’s. This leads to a misconception that Scrum is for small organisations and can only be used for small projects.

But Scrum is a very adaptable process and your larger team can be split into multiple small teams with an average size of 6-8 team members and convene scrum of scrums process to communicate between the scrum teams, enabling larger organisations to adopt scrum and reap the benefits of scrum. Even if teams are geographically divided, you can conduct the scrum meetings with the help of internet technology.

And the scrum of scrum meetings will help in communicating with the scrum teams and update progress, discuss challenges and coordinate the activities. These scrums of scrum meetings are comparable to the daily stand up meetings.

Whereas the daily stand up meeting, facilitated by Scrum Master is a short daily meeting time-boxed to 15 minutes, the scrum of scrum meetings are usually not time-boxed to facilitate more sharing of information between the teams.

The three daily questions in the daily stand-up meeting are:

1. What did I complete yesterday?

2. What will I do today?

3. What impediments or obstacles (if any) am I currently facing?

However Scrum of scrum meetings, facilitated by Chief Scrum Master, is not time boxed to fifteen minutes, also unlike daily stand up meetings there is no frequency. And in the scrum of scrum meeting here there are four questions to be answered by the designated team member representing each team:

1. What has my team been working on since the last meeting?

2. What will my team do until the next meeting?

3. What were our teams counting on our team to finish that remains undone?

4. What is our team planning on doing that might affect other teams?

This allows each team to clearly understand the work status of all other teams. The scrum of scrum meetings could be set at predefined intervals or could be ad-hoc when required. This way larger organisation with large project teams can quickly embrace scrum effectively.

(Abstracts from – Source: A Guide to the Scrum Body of Knowledge – SBOK Guide)

Professional Agile Leadership guidelines provide a structured framework for leaders to effectively navigate the complexities of Agile environments. These guidelines emphasize servant leadership principles, encouraging leaders to prioritize the needs of their teams and stakeholders above their own.

Scaled Scrum Master Guidelines provide a framework for effectively scaling Agile practices across multiple teams or large projects. These guidelines emphasize the importance of alignment, collaboration, and transparency to ensure the success of Agile transformations. Scaled Scrum Masters should focus on facilitating communication, removing impediments, and promoting a culture of continuous improvement. They play a crucial role in guiding teams to embrace Agile principles while adapting practices to fit the specific needs and complexities of the organization.

SCRUMstudy presents a thorough Scrum Certification Classroom Training program crafted to offer a profound grasp of Scrum principles and methodologies. Guided by seasoned instructors, these engaging sessions guarantee participants acquire practical insights and hands-on practice. The curriculum encompasses crucial Scrum fundamentals such as roles, events, and artifacts, equipping attendees for certification assessments. Through active participation, both individuals and teams can elevate their Agile competencies, refine project execution, and bolster their contributions to organizational success.

The Scaled Scrum Master Certification (SSMC™) Online, is designed for Scrum professionals who aim to extend their expertise in scaling Scrum across multiple teams and complex projects. This certification equips practitioners with advanced skills to coordinate, manage, and implement Scrum processes effectively at an enterprise level. The SSMC™ curriculum covers essential topics such as managing distributed teams, synchronizing multiple Scrum teams, and handling intricate project dynamics, ensuring that participants can drive agile transformation and deliver substantial business value in large-scale environments.

The Scaled Scrum Master is a premier certification for Scrum Masters operating within large-scale Agile environments. This program equips professionals with the knowledge and skills necessary to manage multiple Scrum teams, coordinate large projects, and ensure alignment with enterprise goals.

The importance of Scaled Scrum Master Certification cannot be overstated in today's complex, large-scale project environments. This certification equips Scrum Masters with advanced skills and knowledge to effectively coordinate multiple Scrum teams working towards a unified goal. Organizations benefit from reduced project risks, improved efficiency, and higher agility, making Scaled Scrum Master Certification a crucial asset for driving successful outcomes in expansive, multifaceted projects.

Scrum Agile principles are foundational guidelines that drive the successful implementation of Scrum in software development and other project management contexts. These principles emphasize iterative progress, collaboration, and flexibility. Key elements include delivering small, incremental improvements frequently, fostering close cooperation among cross-functional team members, and maintaining a constant focus on customer feedback and value. Transparency, inspection, and adaptation are central to Scrum, ensuring that processes and outcomes are regularly reviewed and adjusted as needed.

Many organizations all over the world are finding it hard to keep up with the fast-changing business scenarios, using the traditional project management methods. These scenarios may include periodic customer demands, fast-changing project requirements, and issues relating to support activities and so on. Increasingly, project managers and software developers have started to prefer Agile software development methods. Even the US Department of Defense, in a recent update to its procurement rules has made known its non-preference for ‘Waterfall model’-based project management solutions. Some of the most popular methods include Rational Unified Process, Scrum, Extreme Programming and Dynamic Systems Development Method.

An overview of the Agile methodology

The year 2001 saw the ‘Agile Manifesto’ being formulated by seventeen software programmers at Snowbird Resort in Utah, USA. The Agile Manifesto gives us twelve important principles, which include customer satisfaction, communication, co-operation, the importance of working software, and welcoming change.

Agile methods break-up complex tasks into small increments with nominal planning. Iterations are short time frames that may last between one to four weeks. The iteration involves a team with cross-functional skills. Planning, requirements analysis, designing, coding, unit testing, and acceptance testing are all taken care of by the same team. At the end of the iteration, a working product is presented to business stakeholders. This reduces overall risk and allows the project to adapt to changes swiftly.

An overview of the Scrum Framework

Scrum is one of the most popular Agile methodologies. As per the Scrum Book of Knowledge, Scrum is an adaptive, iterative, fast and flexible framework designed to quickly deliver significant value during a project. It ensures transparency in communication and creates an environment of collective accountability and continuous progress.

The typical Scrum project will include the below-mentioned steps:

• The Project Vision is created during Business Stakeholder Meeting, following which the Product Owner develops a Prioritized Product Backlog. This includes a ranked list of business requirements written in the form of User Stories).
• The Product Owner consents about the Deliverables only if they meet the previously agreed Acceptance Criteria.The Sprint comes to an end with a Retrospect Sprint Meeting where the Scrum team deliberates ways to develop processes as they move ahead into succeeding Sprints.
• A Sprint Planning Meeting is the first activity within a Sprint, during which high priority User Stories in the Prioritized Product Backlog are considered to be included within the Sprint.
  • A Sprint usually lasts between one and six weeks, where the Scrum Team works to create theoretically shippable Deliverables or product increments.
  • During the Sprint, short yet extremely focused Daily Standup Meetings are coordinated by the Scrum Master where the Scrum Team discusses progress.
  • Toward the end of the Sprint, a Sprint Review Meeting is held during which the Product Owner and relevant business stakeholder(s) are provided a demonstration of the Deliverables.

The center of an Agile project management course revolves around equipping participants with the knowledge and skills to navigate the complexities of Agile methodologies effectively. It serves as a hub for learning Agile principles, understanding various frameworks like Scrum and Kanban, and mastering the techniques for iterative planning, continuous delivery, and adaptive project management. The course emphasizes practical application through hands-on exercises, case studies, and interactive discussions, ensuring participants can confidently apply Agile practices to enhance project outcomes and meet evolving business needs. The center of the course is not only about learning theory but also about cultivating a mindset that values collaboration, transparency, and continuous improvement in Agile project environments.

Agile Scrum project management is an iterative and collaborative approach focused on delivering value to customers efficiently and effectively. It emphasizes adaptability, transparency, and continuous improvement throughout the development process. In Agile Scrum, projects are broken down into small, manageable increments called sprints, typically lasting two to four weeks. Each sprint delivers a potentially shippable product increment, allowing for frequent feedback and course corrections.

A role such as that of a project manager doesn’t exist in Scrum. But, in the organization there are project managers. Then, what is the role of the project manager in the event of the team migrating to Scrum. Well this question has been asked so many times, however the answers are different and are conflicting.

Let’s take up an example to understand this. Mike is a Project Manager and his project is about to migrate to Scrum. For a very long time, Mike is working as a manager in his career. Mike has respected his team mates and trusted them to be responsible about their jobs. His ideology about the finest approach to obtain the outcomes is to develop a team of exceedingly driven professionals, set goals, take initiatives and ensure all needed resources towards their work are there without obstacles. The team looks up to Mike if they have any problems or concerns, as they feel quite at ease intimating project estimates to him because of no “Boss pressure”. He is always careful of their requirements with high importance. It has always been Mike’s goal to enable and support effective communication, prevent and resolve clashes, eliminate obstacles, and make certain maximum prominence into the project for all the involved business stakeholders.

Would Mike be a good Scrum Master for his team? Yes, he will be a good Scrum Master.

The product owner is equally vital as the Scrum Master. In the absence of an effective and efficient product owner, the project is unlikely to succeed. Preferably the role of product owner should be undertaken by the client, who isn’t always plausible or the client is very engrossed with something that, though formally it is the product owner but whom always finds availability at all times to the team a major inability.

In this situation, there is a necessity for a product owner, or substitution product owner, indigenous to the team. A likely candidate can be the project manager. Interacting and working with numerous business stakeholders to convert an incessant flow of change requests into a prioritized list is something the project manager can fare well as he would have prior experience on that.

Agile Respected Institution stands as a beacon of innovation and excellence in the realm of project management methodologies. With a steadfast commitment to fostering adaptive workflows and collaborative environments, it has earned the admiration and trust of professionals worldwide. Its holistic approach prioritizes flexibility, customer satisfaction, and continuous improvement, serving as a catalyst for organizational success in today's dynamic business landscape. Through rigorous training, insightful consulting, and a culture of empowerment, Agile Respected Institution equips individuals and teams with the skills and mindset needed to thrive in an ever-evolving world.

Becoming a certified Scrum Master is a pivotal step for professionals seeking to excel in agile project management. With the increasing demand for agile methodologies, selecting the right training provider is paramount. The SBOK® Guide, a comprehensive resource for Scrum practitioners, serves as a beacon for aspiring Scrum Masters. Distinguished training providers offer an immersive learning experience, equipping candidates with the knowledge and skills needed to navigate the complexities of Scrum frameworks effectively. Through interactive sessions, real-world case studies, and expert guidance, these providers ensure a deep understanding of Scrum principles and practices. With certification from a reputable provider endorsed by the SBOK® Guide, Scrum Masters are equipped to lead teams, foster collaboration, and drive successful project outcomes in today's dynamic business landscape.

The Scaled Scrum Master Certification (SSMC™) Online, is designed for Scrum professionals who aim to extend their expertise in scaling Scrum across multiple teams and complex projects. This certification equips practitioners with advanced skills to coordinate, manage, and implement Scrum processes effectively at an enterprise level. The SSMC™ curriculum covers essential topics such as managing distributed teams, synchronizing multiple Scrum teams, and handling intricate project dynamics, ensuring that participants can drive agile transformation and deliver substantial business value in large-scale environments.

Scrum Certification Professional Development focuses on enhancing skills and knowledge in Scrum, a popular Agile framework for managing complex projects. It involves earning certifications most popular being Scrum Master Certified (SMC) and Scrum Product Owner Certified (SPOC). These certifications validate one's expertise in Scrum principles, practices, and methodologies. Professional development in this field includes attending workshops, participating in training courses, engaging in practical Scrum projects, and continuous learning through reading and community involvement. It aims to improve one's ability to facilitate, implement, and optimize Scrum processes, leading to more efficient project delivery and higher quality outcomes.

It is often seen that Agile has been implemented successfully in different projects. But when it comes to Product Management or NPD (New Product Development), many people get sceptical regarding implementation of Agile. Now it has to be understood that Agile is not a methodology which can be used in a cookie cutter way across any organization. A lot of tweaking and customization is required to make it work. So, in product management, a proper assessment is required to see if Agile implementation will improve performance or not.

Here also, we need to see if the following two criteria are being fulfilled or not:

1. Requirement Volatility : It is important to identify the volatility of requirements and whether working in Sprint will actually improve customer satisfaction, reduce uncertainty and help PM teams become more productive or not. If requirements are fixed in sand and are not dynamic in nature, it will not make any marked improvement even if the teams work in sprint. Also, Agile Product Life Cycle Management involves a lot of new learning, so it needs to be checked if the team will be comfortable in this transition or not.
2. Frequent customer Interaction: External customers are big stakeholders in any Agile effort. In many product management scenarios, we have seen that customers just give their specifications and just go away for months and months. And finally when they come back for the product, it is completely different from what they expected, because market dynamics change and the expectations change as well. So the biggest benefit is actually to the customers themselves, and this is what the PM team should explain in details to the customers so as to get their buy in. Without their pro-active support, it will not be possible to implement Agile in any way.

If we are talking about New Product Development, then Agile actually becomes even more crucial and important.  That is because neither the customers nor the PM team has any benchmark to follow. So, frequent discussions and brain storming sessions followed by change in requirements or prototypes will be mandatory for successful NPD. So, it is important to realize that Agile can be implemented successfully in Product Management as well, provided it is understood properly and used in the proper context. Also, management buy-in and customer buy-in are important components in this scenario, and a good AGILE coach will also be very beneficial.

Scrum Agile principles are foundational guidelines that drive the successful implementation of Scrum in software development and other project management contexts. These principles emphasize iterative progress, collaboration, and flexibility. Key elements include delivering small, incremental improvements frequently, fostering close cooperation among cross-functional team members, and maintaining a constant focus on customer feedback and value. Transparency, inspection, and adaptation are central to Scrum, ensuring that processes and outcomes are regularly reviewed and adjusted as needed.

Many organizations all over the world are finding it hard to keep up with the fast-changing business scenarios, using the traditional project management methods. These scenarios may include periodic customer demands, fast-changing project requirements, and issues relating to support activities and so on. Increasingly, project managers and software developers have started to prefer Agile software development methods. Even the US Department of Defense, in a recent update to its procurement rules has made known its non-preference for ‘Waterfall model’-based project management solutions. Some of the most popular methods include Rational Unified Process, Scrum, Extreme Programming and Dynamic Systems Development Method.

An overview of the Agile methodology

The year 2001 saw the ‘Agile Manifesto’ being formulated by seventeen software programmers at Snowbird Resort in Utah, USA. The Agile Manifesto gives us twelve important principles, which include customer satisfaction, communication, co-operation, the importance of working software, and welcoming change.

Agile methods break-up complex tasks into small increments with nominal planning. Iterations are short time frames that may last between one to four weeks. The iteration involves a team with cross-functional skills. Planning, requirements analysis, designing, coding, unit testing, and acceptance testing are all taken care of by the same team. At the end of the iteration, a working product is presented to business stakeholders. This reduces overall risk and allows the project to adapt to changes swiftly.

An overview of the Scrum Framework

Scrum is one of the most popular Agile methodologies. As per the Scrum Book of Knowledge, Scrum is an adaptive, iterative, fast and flexible framework designed to quickly deliver significant value during a project. It ensures transparency in communication and creates an environment of collective accountability and continuous progress.

The typical Scrum project will include the below-mentioned steps:

• The Project Vision is created during Business Stakeholder Meeting, following which the Product Owner develops a Prioritized Product Backlog. This includes a ranked list of business requirements written in the form of User Stories).
• The Product Owner consents about the Deliverables only if they meet the previously agreed Acceptance Criteria.The Sprint comes to an end with a Retrospect Sprint Meeting where the Scrum team deliberates ways to develop processes as they move ahead into succeeding Sprints.
• A Sprint Planning Meeting is the first activity within a Sprint, during which high priority User Stories in the Prioritized Product Backlog are considered to be included within the Sprint.
  • A Sprint usually lasts between one and six weeks, where the Scrum Team works to create theoretically shippable Deliverables or product increments.
  • During the Sprint, short yet extremely focused Daily Standup Meetings are coordinated by the Scrum Master where the Scrum Team discusses progress.
  • Toward the end of the Sprint, a Sprint Review Meeting is held during which the Product Owner and relevant business stakeholder(s) are provided a demonstration of the Deliverables.

Adopting Scrum for enterprise projects requires a strategic and phased approach to ensure seamless integration and optimal results. Key strategies include obtaining executive buy-in to foster a supportive culture, starting with a pilot project to demonstrate value, and gradually scaling up. Training and certifying team members, particularly Scrum Masters and Product Owners, is essential to build expertise. Implementing robust tools for tracking progress and facilitating communication can enhance collaboration. Additionally, it's crucial to align Scrum practices with existing enterprise processes, allowing flexibility for continuous improvement while maintaining compliance with organizational standards. Regular reviews and feedback loops help refine the approach and drive sustained success in large-scale environments.

Scaling Scrum for the Enterprise is usually applicable to the following:

• Portfolios, programs, and/or projects in any industry
• Products, services, or any other results to be delivered to business stakeholders

The term “product” may refer to a product, service, or other deliverable. Scrum can be applied effectively to any project in any industry—from small projects or teams with as few as six team members to large, complex projects with up to several hundred team members.

For Scaling Scrum for Enterprise, the following processes need to be followed:

Create Program or Portfolio Components—In this process, the Program or Portfolio Product Owner and key business stakeholders identify common components and resources required for the program or portfolio. The Minimum Done Criteria are defined and all business stakeholders are identified.

Review and Update Scrum Guidance Body—In this process, the Scrum Guidance Body recommendations are regularly reviewed by the members of the Scrum Guidance Body and are updated when and if necessary. In this process, changes in the membership of the Scrum Guidance Body are also handled.

Create and Refine Program or Portfolio Backlog—In this process, the Program or Portfolio Backlog is created, updated, and maintained. Recommendations for improvements of the Scrum Guidance Body Recommendations may be made and implementation deadlines may be adjusted based on changed requirements and/or progress of the projects in the program or portfolio.

Coordinate Program or Portfolio Components—In this process, components of the program or portfolio are coordinated. Dependencies between projects are addressed, common impediments are discussed, and best practices are shared. Sometimes, recommendations for improvements of the Scrum Guidance Body are made.

Retrospect Program or Portfolio Releases—In this process, the Program or Portfolio Product Owner and key business stakeholders get together to retrospect a program or portfolio Release and internalize the lessons learned. Often, these lessons learned to lead to agreed actionable improvements to be implemented in future releases. Sometimes, improvements to the Scrum Guidance Body may be recommended.