Scrum.org

APRIL 20, 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 the Sprint Retrospective. The Sprint itself in its entirety. If no clear targets are agreed, how can a team do a useful Sprint Retrospective?

SCRUM 123

SCRUM Controlling Process 123

Scrum.org

SEPTEMBER 30, 2022

So how is Done, the Definition of Done important during the Sprint Retrospective? Remember that the purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness. As a Scrum team inspects its last Sprint looking for ways to improve, quality could be one of the topics to discuss.

SCRUM 180

SCRUM Planning 180

ProjectManager.com

FEBRUARY 28, 2019

Retrospection is key to understanding and self-awareness. Scrum, an agile framework for small teams, especially harnesses the benefits of retrospection. A sprint retrospective is just as it sounds, a time of reflection. What Is a Sprint Retrospective? The entire team is present for the sprint retrospective.

SCRUM 226

SCRUM Development Team Review Agile Software Review 226

Scrum.org

NOVEMBER 18, 2021

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 take the Sprint Retrospective. . . Don't want to miss any of these blog posts?

SCRUM 179

SCRUM Controlling Process 179

Scrum.org

APRIL 28, 2022

In the past series of blog posts we covered the three pillars of Empiricism, and we covered the Scrum Values. During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team takes decisions, making it self-managing. Let’s have a look at the Sprint Retrospective. In the next Sprint - action.

SCRUM 157

SCRUM 157

Agilemania

DECEMBER 8, 2020

And you might think what is to struggle there, run a Sprint Retrospective and get your improvements, so easy or is it? Does… The post What is Sprint Retrospective? How to Improve Your Sprint Retrospective? I struggled to create a culture of continuous improvement within the team.

SCRUM 90

SCRUM Planning 90

Scrum.org

FEBRUARY 10, 2022

Let's have a look what living the Scrum Values can bring to the Spint Retrospective. Commitment to achieve the Sprint Retrospective’s expected outcome: having planned ways to increase quality and effectiveness. These are only one example of how each Scrum Value could be lived during the Sprint Retrospective. .

SCRUM 145

SCRUM 2022 Planning 145

Scrum.org

MAY 29, 2023

That’s roughly the flow of this blog post. Hence the title of this blog post. They conduct all the Scrum events and use a Product Backlog and even a Sprint Backlog. For example, during the Daily Scrum, the team doesn’t use a Sprint Goal. And during the Sprint Review, none of the stakeholders shows up. Zombie Scrum?

Underperforming Technical Team 235

Underperforming Technical Team SCRUM Planning Estimate 235

Scrum.org

MARCH 18, 2022

Prior to reading this blog, please read the introduction to this series here. To take an example from Professional Scrum, perhaps you’ve been in a Sprint Retrospective where the Scrum Team said “Why do we need to have the Daily Scrum every day? I re-visit the topics/efficacy of my teaching, perhaps in Sprint Retrospectives.

SCRUM 158

SCRUM Technical Review Defining Consulting 158

Scrum.org

MARCH 26, 2024

Short Feedback Cycles: Scrum's iterative approach, with its short Sprints and regular reviews, ensures that feedback is obtained quickly, and adjustments are made in time. Incorporate Regular Risk Reviews: Integrate risk reviews into your regular Scrum events, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Risk Management 183

Risk Management Risk SCRUM Initiating 183

Wrike

JANUARY 11, 2021

Sprint retrospectives are a foundational element of Scrum project management. When done right, a sprint retrospective can help teams improve their processes for future sprints and see better results in less time. What is a sprint retrospective? What is a sprint retrospective meeting?

Software Review 41

Software Review SCRUM Process Planning 41

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 175

SCRUM Planning 175

Scrum.org

JANUARY 9, 2024

If a Product Backlog item does not meet the DOD, it cannot be released or even presented at the Sprint Review. The statements within a DOD must be achievable with a Sprint. The DOD should be inspected and adapted at the Sprint Retrospective. Instead, it returns to the Product Backlog for future consideration.

Technical Review 174

Technical Review Underperforming Technical Team Software Review 2024 174

Scrum.org

AUGUST 17, 2023

Based on learnings from each Sprint, the team is having their retrospective. Next to that, the Developers also keep their Sprint Backlog up-to-date. As they are evaluating their progress towards the Sprint Goal, they evaluate what the best next thing is they can do. They reflect this in their Sprint Backlog.

SCRUM 157

SCRUM Initiating Controlling Process 157

Scrum.org

APRIL 1, 2024

Implement Scrum Artifacts and Events Effectively: Utilize Scrum events like Sprint Planning, Daily Scrums, Sprint Reviews, and Retrospectives as opportunities to inspect progress and adapt plans. Don't want to miss any of these blog posts? We have some scheduled in the coming period.

SCRUM 144

SCRUM Agile Planning Process 144

Scrum.org

APRIL 27, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders inspect based on a common understanding. So far we have covered Sprint Planning, the Daily Scrum, Sprint Review and Sprint Retrospective. What about the Sprint itself? A delicate balance.

SCRUM 192

SCRUM Process Planning 192

Scrum.org

JUNE 1, 2023

Developers are typically involved in inspecting progress towards the Sprint and the Product goal, and in inspecting the collaboration during the Sprint itself (people, relationships, process, tools), and the Product Backlog. With our current understanding, will we be able to achieve our goals (both for the Sprint and the Product)?

SCRUM 141

SCRUM Initiating Closing Controlling 141

ProjectManager.com

FEBRUARY 14, 2023

It’s used for tracking work in a project schedule or during a sprint in a scrum. This also allows them to estimate the time left in the sprint or project. That’s a simple but effective way to measure progress and estimate how much time is left in the sprint or project. Each sprint should be roughly the same duration.

Agile 346

Agile Estimate SCRUM Software Review 346

Scrum.org

DECEMBER 14, 2023

In the past series of blog posts we covered the three pillars of Empiricism, and we covered the Scrum Values. During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team takes decisions, making it self-managing. So far I have covered the Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Technical Review 160

Technical Review SCRUM Initiating Planning 160

Scrum.org

MAY 15, 2022

Does your team struggle with using Sprint Goals? Sprint Goals help teams understand what is valuable in a Sprint, and thus help them make decisions about what to spend time on (and whatnot). Sprint Goals create focus and clarity in complex work. So what can you do when using Sprint Goals is difficult? Invitation.

Consulting 232

Consulting SCRUM Influencer Closing 232

ProjectManager.com

AUGUST 20, 2021

Agile work takes place during short periods of time that are called agile sprints. A sprint is usually between one and three weeks, and the team uses this time to complete deliverables. The release plan is broken down into sprints, with each sprint dictating a specific set of tasks to be completed. Try it free today!

Agile 376

Agile Planning Software Review Defining 376

Scrum.org

JANUARY 12, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders need transparency so there is a common understanding. Remember from earlier posts: I will repeat the above few lines in the coming blog posts: repeating = learning. ;-). Today, we check the Sprint Retrospective. .

SCRUM 184

SCRUM Controlling Process 184

Scrum.org

FEBRUARY 12, 2024

Utilize Sprint Reviews and Retrospectives to gather insights and refine your approach for better value delivery. If you want to take a deeper dive into the concepts we are covering in this blog series, then surely check out our Professional Scrum MasterY workshop. Don't want to miss any of these blog posts?

SCRUM 166

SCRUM Agile Initiating Controlling 166

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 253

Planning Technical Review Development Team Review Software Review 253

Scrum.org

JANUARY 9, 2023

Is your team becoming less predictable sprint over sprint? If this situation sounds familiar, this blog shows how to self-manage this problem. This Scrum Team has two week sprints and then releases monthly. The team, unsure what to do next, talks about addressing this issue in their retrospective. RETROSPECTIVE.

Software Review 182

Software Review Development Team Review SCRUM Initiating 182

Scrum.org

JANUARY 6, 2022

Based on learnings from each Sprint, the team is having their retrospective. Next to that, the Developers also keep their Sprint Backlog up-to-date. As they are evaluating their progress towards the Sprint Goal, they evaluate what the best next thing is they can do. They reflect this in their Sprint Backlog.

SCRUM 183

SCRUM 2022 Initiating Controlling 183

Scrum.org

OCTOBER 7, 2021

Developers are typically involved in inspecting progress towards the Sprint and the Product goal, and in inspecting the collaboration during the Sprint itself (people, relationships, process, tools), and the Product Backlog. With our current understanding, will we be able to achieve our goals (both for the Sprint and the Product)?

SCRUM 165

SCRUM Initiating Closing Controlling 165

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 208

SCRUM Cadence Defining Planning 208

Scrum.org

JULY 13, 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. So far I have covered the Sprint Planning, Daily Scrum, Sprint Retrospective and Sprint Review.

SCRUM 135

SCRUM Closing Controlling Planning 135

Scrum.org

JANUARY 19, 2023

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders need transparency so there is a common understanding. What about the Sprint itself? This does immediately mean that during the entire Sprint itself there are informal opportunities to do just that. Do not wait.

SCRUM 181

SCRUM Controlling Planning Process 181

Scrum.org

FEBRUARY 23, 2023

I also have developers asking me if they can skip the sprint review and retrospective as they have some work to finish off for the sprint and that is a much better use of their time than sitting in a meeting. This is because important decisions are based on the perceived state of the Sprint's increment.

SCRUM 184

SCRUM Risk Management Agile Risk 184

NimbleWork

FEBRUARY 19, 2024

Many teams lean into retrospectives to help uncover areas where processes could be slicker, where engagement hasn’t been as effective as it could and to look for areas of improvement. The Place for Retrospectives Retros happen regularly during the project management lifecycle for agile and iterative projects. But they don’t have to be.

Cadence 109

Cadence Software Review Energy Lean 109

NimbleWork

MARCH 27, 2024

This may also be a great topic to include in the team’s retrospective to encourage the team to think and reflect on their individual and collective efforts to meet the goals that were set. Velocity in Agile represents the amount of work a team can complete in a sprint. Sprint Planning in Nimble Agile 5.

Technical Review 84

Technical Review SCRUM Estimate Agile 84

Scrum.org

AUGUST 25, 2023

Imagine that you’re part of an Agile or Scrum team and you frequently experience how your team struggles to navigate conflict effectively, or the Sprint Retrospective only results in meaningless improvements, or Sprints never have a predefined Sprint Goal. So what can you do when this happens? Interested in learning more?

SCRUM 151

SCRUM Software Review Agile Closing 151

Scrum.org

JUNE 8, 2021

As such the Scrum Framework has a number of meetings that happen throughout the Sprint. These are the Daily Scrum, Sprint Planning, Sprint Review and the Sprint Retrospective. We talked about improvement above, but the Scrum Master doesn’t wait for a Retrospective to occur to cause adaptation.

SCRUM 182

SCRUM Development Team Review Leadership Agile 182

Scrum.org

APRIL 5, 2022

In this blog post, I share my thoughts on this alternative approach. The Spotify Model is probably the most famous example, but other examples are the SAFe framework (which is essentially a large best practices container), or simply the use of Story Points, Sprint 0, or a Definition of Ready. Why does it matter?

SCRUM 206

SCRUM Underperforming Technical Team Influencer Closing 206

Scrum.org

JULY 25, 2023

Focus is on features being delivered rather than the value being delivered (Feature Factory) No Valuable Usable (Done) increment at the end of each Sprint. Unaware of the true purpose of the Sprint Review and Sprint Retrospective. No validation happens once an increment (product) is released to the market.

SCRUM 157

SCRUM Agile Software Review 2001 157