Scrum.org

MAY 29, 2023

That’s roughly the flow of this blog post. Hence the title of this blog post. They have a Product Owner, a Scrum Master, and a bunch of Developers. They conduct all the Scrum events and use a Product Backlog and even a Sprint Backlog. And during the Sprint Review, none of the stakeholders shows up.

Underperforming Technical Team 242

Underperforming Technical Team SCRUM Planning Estimate 242

Scrum.org

FEBRUARY 19, 2024

My last blog talked about how to show management how scrum helps the organization overall. Among the five Scrum events, the Sprint Retrospective stands out as a pivotal opportunity for showcasing self-management. In the subsequent Sprint Review, the team showcases the improvement in code coverage alongside the sprint goal.

Software Review 195

Software Review SCRUM Initiating Executing 195

Scrum.org

DECEMBER 21, 2023

In the past series of blog posts we covered the three pillars of Empiricism, and we covered the Scrum Values. Let’s take a look at the Product Backlog. The Product Backlog includes the Product Goal. This is a description of a future state of the product. Don't want to miss any of these blog posts?

SCRUM 190

SCRUM Risk Management Defining Risk 190

Scrum.org

MARCH 26, 2023

Overview I’ve studied the goals for some time now and have come up with a checklist that can help you make better Sprint and Product Goals. If you’re unclear on why goals are important, see my blog post on commitments. It’s a killer blog that’ll have you rethinking your approach to Sprint Goals.

SCRUM 249

SCRUM Underperforming Technical Team Software Planning 249

Scrum.org

SEPTEMBER 28, 2023

TL;DR This blog explores the crucial role of a Product Owner (PO) in managing the Product Backlog, a central element in Scrum, which serves as a roadmap for the Scrum Team's potential tasks. It aims to offer a clear and transparent roadmap for everyone involved in the product's journey. The objective?

SCRUM 203

SCRUM Closing Influencer Defining 203

Scrum.org

NOVEMBER 30, 2023

The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint - What’s The Point? The Scrum Guide is incredibly concise (just 315 words in the English version) in communicating the purpose and value of the Sprint.

SCRUM 220

SCRUM Cadence Defining Planning 220

Scrum.org

AUGUST 17, 2023

Let’s take the Product Developers. The Developers are accountable for instilling quality while implementing Product Backlog Items in the next Increment. As such they of course adapt the product itself. In the Definition of Done (DoD) for the product. They reflect this in their Sprint Backlog.

SCRUM 165

SCRUM Initiating Controlling Process 165

Scrum.org

NOVEMBER 24, 2022

They build up all skills needed to create value each and every Sprint, and they can decide what work needs to be done, who does it and how to do it in the most effective way. For your reference, you find below an overview of all blog posts in this series. Sprint Planning. Sprint Review. Sprint Retrospective.

SCRUM 187

SCRUM Planning 187

ProjectManager.com

APRIL 2, 2024

It has tools that allow you to plan sprints, track the completion of tasks, balance your team member’s workload and create product roadmaps. Yes, Jira’s kanban view is one of its most popular features and software developers commonly use it for sprint planning. Does Jira Have a Kanban Board? Here are some of them.

Underperforming Technical Team 323

Underperforming Technical Team Software Review 2024 Software Developers 323

Scrum.org

FEBRUARY 5, 2024

However, in Scrum, this engagement is not just a part of the process; it's an integral component of every step in the development of a product or initiative. In Scrum, however, stakeholders are involved continuously, providing feedback throughout the product development process. Don't want to miss any of these blog posts?

SCRUM 176

SCRUM Consulting Agile Initiating 176

Scrum.org

OCTOBER 13, 2022

It needs a self-managing, and especially a cross-functional team, a team living the Scrum Values, to make it work in a way that it brings the needed transparency with regards to the quality of your solution/product. ?? Being Done = meeting the required quality measures = a new Increment exists = a production release is possible.

SCRUM 200

SCRUM Planning 200

Scrum.org

AUGUST 10, 2023

Let’s take the Product Owner. Being accountable for optimizing the value of the product, the Product Owner is managing the Product Backlog (PBL) and as such adapts it quite frequently. This in order to show to the team and the stakeholders what is needed in the Product to reach the next Product Goal.

SCRUM 148

SCRUM Closing Initiating Controlling 148

ProjectManager.com

AUGUST 20, 2021

There is still a person who prioritizes tasks (usually known as the product owner ), but the agile team themselves determine how to do the project planning and get the work done. Agile work takes place during short periods of time that are called agile sprints. This is the product that an agile team works on. Try it free today!

Agile 371

Agile Planning Software Review Defining 371

ProjectManager.com

FEBRUARY 28, 2023

Product management is a way to organize the development, position and pricing of your product. It helps you manage every step of the process that sees your product go from concept to market. A product requirements document (PRD) lists the features you’ll include in your product release.

Software Review 282

Software Review Development Team Review Budget Agile 282

Scrum.org

JANUARY 18, 2024

Being accountable for creating any aspect of a usable Increment that adheres to the expected quality levels each Sprint, Developers do need to take active part in making decisions together with the Product Owner and Scrum Master. During Sprint Planning, the Developers in collaboration with the Product Owner define a Sprint Goal.

SCRUM 199

SCRUM Defining Planning 199

Scrum.org

MARCH 30, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders inspect based on a common understanding. Let’s take Sprint Planning to start with. The Product Backlog What does the Product Backlog show as most valuable right now? Inspect what? Which is a fair point!

Planning 199

Planning SCRUM Controlling Process 199

Scrum.org

OCTOBER 12, 2020

I got the idea of writing this blog while hosting a webinar on the same topics when multiple people told us to document our discussion. Originally I posted this blog on Agilemania , and you can check our upcoming webinars there. Top 5 Things You Should Do During Sprint Planning . 1st – Craft Sprint Goal .

Planning 254

Planning Technical Review Development Team Review Software Review 254

Scrum.org

FEBRUARY 18, 2024

In this blog post I'll try to answer this question from different perspectives. Scrum however clearly lays out a number of services a Scrum Master provides to the Product Owner, the entire Scrum Team, and the organization. helping the Product Owner finding techniques for effective Product Backlog management.

SCRUM 121

SCRUM Finance Budget Consulting 121

Scrum.org

JANUARY 9, 2024

The DOD is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog Item meets the DOD, an Increment is born. If a Product Backlog item does not meet the DOD, it cannot be released or even presented at the Sprint Review.

Technical Review 187

Technical Review Underperforming Technical Team Software Review 2024 187

Scrum.org

JULY 28, 2022

Let’s have a look at the Product Backlog. . Reminder: the objective of a Product Backlog is to bring transparency on what is needed to improve the product. Even though the Product Owner is accountable for effective Product Backlog management, s/he does not have to do this alone!

SCRUM 194

SCRUM Risk Management Risk Initiating 194

ProjectManager.com

MAY 29, 2020

Thus, successful agile sprints make use of scrum software and scrum artifacts to convey key information, deliver transparency and keep the project rolling on time. Scrum artifacts are ways to describe the work that must be done, and they always add value during a sprint. Product Backlog. Refining the Product Backlog.

SCRUM 253

SCRUM Technical Review Software Review Estimate 253

Scrum.org

AUGUST 13, 2023

In the past 20 years, I’ve been involved in a wide variety of software- and product development efforts. The more complex the product is, the more time everyone wants to think. Once I started with Scrum, we often still created all of this, but turned it into a “Sprint 0”. First think, then build.

Software Review 167

Software Review Underperforming Technical Team Technical Review SCRUM 167

Scrum.org

JUNE 22, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders adapt what they deem necessary in order to minimise any deviations to acceptable limits which they have identified during inspection. Let’s have a look at the Daily Scrum. The Sprint Backlog is adapted. The team learns.

SCRUM 169

SCRUM Controlling Planning Process 169

Scrum.org

MAY 4, 2023

Let’s take the Product Backlog. The Product Backlog is inspected at least during Sprint Planning and Sprint Review to detect variances in what the product might be able to be, and what it might be able to provide as capabilities one day (both shorter term and long term) compared to the Product Goal.

SCRUM 197

SCRUM Innovation Controlling Process 197

Scrum.org

JULY 27, 2023

This also applies for the Sprint Backlog. The Sprint Backlog is typically adapted during Sprint Planning and during the Daily Scrum. etc. Each time new insights are gained about the progress towards the Sprint Goal, the Developers do make the necessary adaptations.

SCRUM 158

SCRUM Closing Controlling Risk 158

Scrum.org

JUNE 16, 2023

I changed my role from Project Manager to Scrum Master, the developers slowly moved from programmers to product developers , and we tried many experiments with the Product Owner role because that proved to be a returning challenge. In the context of Scrum, the Product Owner plays an essential role. Sell Sprints.

Underperforming Technical Team 177

Underperforming Technical Team 2015 SCRUM 2010 177

Scrum.org

MAY 16, 2022

Product Backlog. Sprint Backlog. Insbesondere fragen Product Owner:innen. Wie sehen typische Veränderungen im Produkt Backlog, Sprint Backlog am Beginn, während und am Ende der Sprints aus? . Hier möchte ich die Fragen in einer Reihe von mehreren Blogs mit Videos beantworten.

SCRUM 160

SCRUM Planning 160

Scrum.org

AUGUST 24, 2023

Support your Scrum Team with Product Backlog management. All in order to reach their goals as agreed in the Product Goal, the Sprint Goal, and the Definition of Done (quality goal). Don't want to miss any of these blog posts? Are the adaptations made in this area bringing the team closer to their goals?

SCRUM 161

SCRUM Initiating Controlling Defining 161

Scrum.org

MAY 15, 2022

Product Backlog. Sprint Backlog. Insbesondere fragen Product Owner:innen. Wie sehen typische Veränderungen im Produkt Backlog, Sprint Backlog am Beginn, während und am Ende der Sprints aus? . Hier möchte ich die Fragen in einer Reihe von mehreren Blogs mit Videos beantworten.

SCRUM 156

SCRUM Planning 156

Scrum.org

NOVEMBER 16, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team takes decisions, making it self-managing. Let’s take Sprint Planning to start with. The Scrum Team agrees why they will take on this next Sprint. The Scrum Team agrees why they will take on this next Sprint. What steps do we need to take?

Planning 183

Planning SCRUM 183

Scrum.org

MAY 19, 2022

In the past series of blog posts we covered the three pillars of Empiricism, and we covered the Scrum Values. Let’s take a look at the Sprint Backlog. The Sprint Backlog includes the Sprint Goal. This is the objective for the current Sprint. And so the Sprint Backlog supports deciding on what. .

SCRUM 162

SCRUM Risk Management Risk Planning 162

Scrum.org

FEBRUARY 1, 2024

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team should have all necessary skills in order to reach its objectives. Let’s start with Sprint Planning. Remember the objective of Sprint Planning: to have a plan for the Sprint. Why is the Sprint valuable? What can be Done this Sprint?

Planning 154

Planning SCRUM Risk Management Estimate 154

Scrum.org

JANUARY 6, 2022

Let’s take the Product Developers. . The Developers are accountable for instilling quality while implementing Product Backlog Items in the next Increment. As such they of course adapt the product itself. . In the Definition of Done (DoD) for the product. They reflect this in their Sprint Backlog.

SCRUM 197

SCRUM 2022 Initiating Controlling 197

Scrum.org

DECEMBER 23, 2021

Let’s take the Product Owner. . Being accountable for optimizing the value of the product, the Product Owner is managing the Product Backlog (PBL) and as such adapts it quite frequently. This in order to show to the team and the stakeholders what is needed in the Product to reach the next Product Goal.

SCRUM 191

SCRUM 2022 Closing Initiating 191

Scrum.org

FEBRUARY 2, 2023

Let’s take the Sprint Backlog. Why are we even doing this Sprint? Understanding the goal for a Sprint allows the team to take ownership. What Product Backlog Items are selected for this Sprint? Then here you go, bring more transparency though your Sprint Backlog. Agree on this.

SCRUM 180

SCRUM Initiating Controlling Process 180

Scrum.org

APRIL 18, 2022

Welcome to Scrum Sutra – a blog series where I shall share a 3-min overview of each element of Scrum and how it connects with the other elements in the bead to form Scrum Sutra. the Sprint Goal, make necessary adaptation to their upcoming planned work which reflects in the Sprint Backlog. For more, visit [link]. .

SCRUM 186

SCRUM Risk Management Risk Planning 186

Scrum.org

AUGUST 31, 2023

Let’s take Sprint Planning to start with. Commit to achieve the Sprint Planning’s expected outcome: lay out the work to be performed during the Sprint. Have the Courage to have a Sprint Backlog only for the first coming days in the Sprint and find out the remainder during the Sprint itself.

SCRUM 204

SCRUM Planning 204