This learning series contains different strategies to use when negotiating with internal and external stakeholders for effective product management.

To elevate your team’s mindset to focus on customer delight there are many techniques that a Scrum Team can leverage to explore these kinds of questions. This learning series explores a couple of them.

This learning series describes business problem statements, common pitfalls to consider when creating them, and some examples on how to craft them.

Hypothesis-driven development offers a structured approach to problem-solving and innovation while minimizing risks, enabling evidence-based decisions, and fostering experimentation. This series includes the benefits of a hypothesis-drive approach for Scrum Teams and product delivery as well as templates and examples of different hypothesis formats.

Knowing your competition and the dynamics of your competitive landscape are essential to help your organization thrive. This content includes different models to understand the competitive landscape and tips on how to act on that information to build a competitive advantage. This information is vital for effective product management.

Product metrics help assess the customer and business value a product delivers. They provide insights from the perspective of users and the market.

Understanding a product’s revenue and cost is key to creating and executing on a product’s strategy as well as determining its value.

A product roadmap is a visual aid technique that a Scrum Team can use to share and discuss what is upcoming for the product at a high-level.

Business strategy is informed by the company’s mission and vision, and in turn informs individual product visions. An organization inspects and adapts its business strategy based on feedback gathered from delivering product Increments.

Product Ownership requires a distinct set of capabilities and skills. These skills and capabilities are described here. Please note that we are describing Product Ownership here, meaning it does not tie into any specific person, role, function or accountability. This learning series illustrates what needs to be done from the Product Ownership perspective when developing products. The Scrum framework describes a Product Owner as a set of accountabilities that a person can take up. In which ca...

Scrum Teams deliver value to customers in product Increments. Product stability is vital as each Increment builds on the last.

Scrum Team can use forecasting and release planning as a guide for delivering a product through small incremental and frequent releases rather than big bang product launches.

Discover the learning objectives in the PSM course and explore some supporting learning resources.

The objective of a Scrum Team is to deliver value to customers and stakeholders. Product Value actively drives customer satisfaction, loyalty, brand reputation, and the longevity of a business by providing customers with benefits that satisfy their needs.

There are many reasons why Scrum Teams struggle to deliver value. To be more effective, Scrum Teams should better understand customer needs, improve their cross-functionality, be empowered to make decisions, improve their ability to focus, and increase their feedback cycles.

The Developers are the Scrum Team members that create the product. They have specific accountabilities to the team. Learn about these accountabilities and debunk a few myths about being a Developer on a Scrum Team.

A Product Owner is the member of the Scrum Team that is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Learn more about what that means and a few of the common myths about Product Owners.

Un-done work is work that does not conform to the Definition of Done and is therefore unfinished. It represents time the Scrum Team spent creating something that delivered no value. Learn what un-done work is, what causes it and techniques for eliminating it.

The Scrum Master is accountable for the Scrum Team’s effectiveness and for establishing Scrum as it is defined in the Scrum Guide. Excellent Scrum Masters help their teams deliver value. They can help transform a team that struggles, into a team that delivers value every Sprint.

This learning series discusses the importance of developing and delivering valuable product Increments in order to improve the outcomes that its users and customers experience. Scrum Teams deliver product Increments and measure the results to understand what customers want or need.

This learning series contains a list of interview questions that you may encounter as a Product Owner, and the reason why the question is relevant to the Product Owner accountability.

This learning series highlights 9 ways a Product Owner can boost their effectiveness.

The Scrum Team is a small unit of professionals focused on attaining the Product Goal. Scrum Teams consist of a Product Owner, Scrum Master and Developers. Each has a clear set of accountabilities. Learn more about the Scrum Team, accountabilities, responsibilities and why these aren’t called “roles.”

Discover the learning objectives in the PSPBM course and explore some supporting learning resources.

By understanding its customers and users, a Scrum Team can identify opportunities, be more innovative and create products that people need and use. Here are different techniques ways to do this.

Scrum encourages frequent collaboration with stakeholders, and customers in particular. Understanding how to identify and learn about the challenges that key stakeholders face will help the Scrum Team better deliver the value they are seeking.

The Product Vision describes the purpose of a Product. A good Product Vision expresses the value the Product should deliver and to whom that value is delivered.

Product Backlog Management is the act of adjusting and ordering items on the Product Backlog so that the Scrum Team can deliver the most valuable product possible. This learning series explores Product Backlog Management.

The Sprint Backlog represents what the Developers plan to accomplish during the Sprint. Learn about the Sprint Backlog, Sprint Goal, how to use Sprint Backlogs effectively and investigate common antipatterns with the Sprint Backlog.

Learn about the three Scrum artifacts and their commitments: Product Backlog and Product Goal; Sprint Backlog and Sprint Goal; Increment and Definition of Done. Explore some common antipatterns and myths that surround these artifacts.

The Increment is the latest version of the product that conforms to the Definition of Done. During each Sprint, the Developers work toward the current Product Goal by implementing Product Backlog items (PBIs) and integrating their individual work together. Learn about the Increment and its commitment, the Definition of Done. Investigate some common myths about the Increment.

The Product Backlog represents all of the work the Scrum Team knows it needs to do in order to deliver the product. Teams can use the Product Backlog to make decisions about what they should do next. Learn about the Product Backlog, Product Goal, Product Backlog items and Product Backlog refinement.

Unlike the other Scrum Events, the Sprint isn’t a meeting. Instead, it’s the container for all of the work that’s done by a Scrum Team to achieve a Sprint Goal. The Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective all fall within the Sprint.

The Sprint Retrospective is the last event in the Sprint. Unlike other Scrum Events where the focus is on inspecting and adapting ways to improve the product, the Sprint Retrospective is a place for the Scrum Team to inspect and adapt their working practices.

The Sprint Review is a working meeting where the Scrum Team presents their completed work to stakeholders and asks for feedback. The Scrum Team and stakeholders discuss the progress made toward the Product Goal, emerging changes in the business or technical climate and collaborate on what to do next

To keep work moving smoothly, the Developers get together for 15 minutes every day to focus on the Sprint Goal and to plan the upcoming day’s work. During the Daily Scrum, they identify any issues they need help in resolving, ask for help when they need it and adjust the Sprint Backlog, if necessary.

Every Sprint starts with Sprint Planning where the Scrum Team determines what they plan to accomplish during the course of the Sprint. They make this transparent by creating a Sprint Backlog including the Sprint Goal, the selected Product Backlog Items and the Developers’ plan for delivering the work

To help ensure that the work the Scrum Team delivers is valuable, they need to work together, share ideas and responsibilities and have team ownership while also working closely with their stakeholders, including customers and end users.

The five Scrum Events provide regular opportunities for enacting the Scrum pillars of Inspection, Adaptation and Transparency. In addition, they help teams keep aligned with the Sprint and Product Goals, improve Developer productivity, remove impediments and reduce the need to schedule too many additional meetings.

Scrum Teams need to make decisions all the time. Helping teams reach a decision effectively, and gaining necessary buy-in from all team members can be challenging, especially when team members are unclear on who has the final say in making it. Understanding the decision rule, how a decision is made and whose input is required, is necessary because ambiguity in the decision process causes confusion and frustration.

Guidance for how to prepare to earn the Professional Scrum Facilitation Skills certification.

As a new Scrum Master you’ll want to get to know your team, the people outside of your team that you’ll work with, including stakeholders to help the team improve at delivering value. To help you get started, here are some questions and tips to consider when you join a new team as a Scrum Master and suggestions on building collaborative relationships.

The Definition of Done describes the quality standards for the Increment. Learn why getting to Done is so important, what undone work is, if it’s okay to show work that isn’t done to stakeholders, can you present undone work at the Sprint Review and what’s the difference between the DoD and Definition of Ready or acceptance criteria.

Anyone can act as a teacher, helping your colleagues obtain new knowledge or learn new skills. However, if you want to become a very effective teacher, it’s best if you learn a few of the principles of the teaching profession, the skills and traits of a teacher and when teaching can be helpful for a Scrum Team.

Discover the learning objectives in the PSFS course and explore some supporting learning resources.

In Scrum, empiricism refers to the idea that solving complex problems, or doing complex work, can only be done using an exploratory process rather than relying on predetermined plans. Learn about empiricism and complex work. Explore why trust is important for empiricism to thrive.

If you are just getting started, think of Scrum as a way to get work done as a team in small pieces at a time, with experimentation and feedback loops along the way. This learning series explores the pieces that make up the Scrum Framework.

There is no one direct path to become a great Scrum Master. However, we've assembled a few insights and ideas on topics such as driving toward goals, living the Scrum Values, enabling collaboration, removing obstacles, instilling self-management, promoting psychological safety, and encouraging a continuous improvement mindset.