Scrum.org

MARCH 11, 2020

When I started out in a Scrum Team we never really had a Sprint Goal, our focus tended to be looking at the items in the backlog then saying "Get that done and that one, if not all of them!" . One purpose of the Sprint Goal is to provide focus to the Development Team during the Sprint. Not a great place to be in!

Development Team Review 246

Development Team Review Underperforming Technical Team SCRUM Closing 246

MPUG

FEBRUARY 5, 2025

One might conclude that agile approaches to project management, such as Scrum, mean there is no need for gate reviews. We say the same thing if one adopts gate reviews for every product development project. Let’s explore a typical product development project’s phases, goals, and metrics reviewed at each gate.

Development Team Review 111

Development Team Review Technical Review Manufacturing 2008 111

Scrum.org

NOVEMBER 12, 2019

TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?

Development Team Review 172

Development Team Review Underperforming Technical Team SCRUM 2017 172

Planio

FEBRUARY 17, 2025

The Stage Gate process is a project management methodology that breaks projects down into a series of defined stages and gates, each used to manage, validate, and control a project as it develops. The gate at the end of each stage is used as a review point to check if the project is still on track before proceeding to the next stage.

Software Review 88

Software Review Process Development Team Review Technical Review 88

Scrum.org

SEPTEMBER 10, 2020

As Scrum is framework, your teams may be doing additional things in the events - which is fine,as long as they're getting value from doing the actions. Optimise the value of the work the Development Team perform Talk with customers. Ensure the Development Team understands items in the Product Backlog to the level needed.

Development Team Review 169

Development Team Review 2017 SCRUM Estimate 169

Scrum.org

JANUARY 17, 2020

The use of the terms Showcase, Show & Tell or Sprint Review. So which event is best to use? There is nothing wrong with a Show & Tell, Showcase or Sprint Review when used correctly to achieve the desired outcome. However, usage does not make them equal to each other as events that are interchangeable and the same.

Technical Review 200

Technical Review Development Team Review SCRUM Consulting 200

ProjectManager.com

JUNE 27, 2019

Scrum ceremonies are meetings that are unique to scrum teams. Scrum ceremonies ensure that everyone (the scrum master, product owner and development team) is in-sync. A sprint employs four different scrum ceremonies to ensure proper execution: sprint planning, daily scrum, sprint review and sprint retrospective.

SCRUM 294

SCRUM Underperforming Technical Team Development Team Review 2011 294

Scrum.org

FEBRUARY 8, 2021

The Sprint Goal I couldn't remember, as a Dev Team member you gave me time. Hey, Scrum Master, I don't want to miss a single Scrum event this Sprint. Just in time I'm so glad you called me out in the Sprint Review. Hey, Scrum Master, I don't want to miss a single Scrum event this Sprint. Hey, Scrum Master Lyrics.

Development Team Review 172

Development Team Review SCRUM Planning 172

ProjectManager.com

MARCH 25, 2022

Agile project management came about as development teams worked towards getting products to the market faster. The waterfall methodology, which identifies a problem and then plans a solution, forces teams to stick to the requirements and scope of work that was defined at the beginning of the project. Sprint Review.

Agile 370

Agile Software Review Technical Review Development Team Review 370

Scrum.org

SEPTEMBER 19, 2020

It's a key inspect and adapt opportunity for the Development Team, encouraging them check their progress towards the Sprint Goal and adjust their plan accordingly. It's also supposed to be an event for the Development Team and run by the Development Team but as we know in "the real world" it's not always implemented that way!

SCRUM 226

SCRUM Underperforming Technical Team Development Team Review Technical Review 226

Scrum.org

FEBRUARY 24, 2019

"The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint." - The Scrum Guide. The Scrum Guide is markedly ambitious in the standard of professionalism it demands of a team. Review Ready. Code Complete.

Development Team Review 191

Development Team Review Underperforming Technical Team Software Review Technical Review 191

Scrum.org

JUNE 8, 2021

These are the Daily Scrum, Sprint Planning, Sprint Review and the Sprint Retrospective. People new to Scrum tend to worry that with so many scheduled conversations that they or Scrum Team will suffer death by meeting! If the Development Team can take care of the problem themselves, they usually will. Did I miss something?

SCRUM 231

SCRUM Development Team Review Leadership Agile 231

Scrum.org

MARCH 2, 2020

The following list of Scrum stakeholder anti-patterns addresses Scrum events, system-related issues as well as issues of individual players. Scrum Stakeholder Anti-Patterns at Scrum Event Level. Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Sprint Review. The Sprint.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Epicflow Blog

JULY 5, 2024

Reporting and analytics A robust capacity planning tool should generate reports and dashboards with insights into resource availability and capacity, allocation, and utilization, which will help managers track resource performance and assess the efficiency of project work. Top 15 Capacity Planning Tools 1.

2024 101

2024 Planning Development Team Review Consulting 101

Scrum.org

SEPTEMBER 8, 2020

Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives. The ‘where is my report’ mentality : The manager expects to receive reports regularly instead of participating in events, for example, the Sprint Reviews.

Software Review 242

Software Review Agile Underperforming Technical Team Development Team Review 242

Scrum.org

NOVEMBER 11, 2019

In this post we'll have a look at the Sprint Review. The Sprint Review is generally the hardest event to get right. It's where the Scrum Team and their stakeholders meet, thus the event with the largest number of participants. It's also the event in which different people come with a different purpose.

Development Team Review 37

Development Team Review Underperforming Technical Team SCRUM Planning 37

Scrum.org

SEPTEMBER 13, 2021

Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

Scrum.org

NOVEMBER 6, 2023

Scrum’s events, roles, and artifacts give you a framework for how to wrangle the humans — herd the cats, if you will — in order to deliver done, working software. If you’re using Scrum, your goal — your *mission* — is to remember how the role, events, and artifacts of Scrum help you to deliver done, working software. Development Team.

SCRUM 214

SCRUM Software Review Development Team Review Technical Review 214

Scrum.org

FEBRUARY 25, 2020

I looked at how this can work out for your Daily Scrum , and now we've arrived at the last specific event of Scrum: the Sprint Review. A small reminder from the Scrum Guide: “A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. Development Team members spread out.

Development Team Review 173

Development Team Review SCRUM Closing Planning 173

Scrum.org

MAY 5, 2020

Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and Development Team. For example, a poster about Sprint Goals, the Definition of Done, or the Scrum Events. Encourage the team to resolve the impediments together. Things to try….

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Scrum.org

JANUARY 7, 2020

Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? For such an important part of the empirical process made possible by the Scrum Framework, the Sprint Review often receives the least attention in how it is facilitated. In this post, we share the design for a Sprint Review.

Software Review 159

Software Review Development Team Review SCRUM Closing 159

Scrum.org

FEBRUARY 15, 2020

Similarly, Sprint Backlog which is owned by the development team gives the reality of ongoing work every day. There is every possibility that sprint backlog is subject to change as the development team learns more throughout the sprint and it is adapted based on every daily scrum. Sprint Review - 4 hours.

SCRUM 223

SCRUM Development Team Review 2012 Technical Review 223

Scrum.org

JANUARY 10, 2021

Most Scrum Teams that I encounter don’t do refinement of their Product Backlog and try to work on things that they don’t understand correctly. However, if you get to the Sprint Planning event and your backlog is not ready, then you are doing it wrong. You can come up with your Refinement event(s), or refine ad-hoc.

2020 241

2020 Technical Review SCRUM Development Team Review 241

Scrum.org

JULY 5, 2022

During the first year of the pandemic, Scrum adoption more than doubled for software development teams. According to the 15th Annual State of Agile Report, the use of agile approaches for software development grew from 37% in 2020 to 86% in 2021. The Developers create the Sprint Backlog during the Sprint Planning event.

Underperforming Technical Team 218

Underperforming Technical Team SCRUM Software Review Development Team Review 218

Scrum.org

NOVEMBER 7, 2018

In real life, these Product Owners are typically accountable to the value delivered by these multiple teams and rely upon a lot of assistance from the Development Teams in order to deal with the challenge of scale. . Large Scale Scrum and Nexus prefer to have one Product Owner for the entire product with one Product Backlog.

SCRUM 172

SCRUM Development Team Review Technical Review Cadence 172

Scrum.org

NOVEMBER 18, 2020

The concept of a Development Team within a Scrum Team was removed to reduce the potential for dysfunctions between the Product Owner and the Development Team (“us vs. them”) and focus the entire Scrum Team on the same objective[1]. Sprint Review is not a gate to releasing value. .

2017 252

2017 2020 SCRUM 2005 252

Scrum.org

SEPTEMBER 24, 2021

Scrum events actually SAVE time.). When I present the Scrum framework to a new team, I almost always hear someone cry out, “How can we get anything done with so many meetings?! ” The Scrum framework consists of five events (what the uninitiated refer to as meetings), three artifacts, and three roles.

SCRUM 240

SCRUM Software Review Lean Leadership 240

Scrum.org

JULY 21, 2020

That is why we pay the Development Team to accept the responsibility to deliver a ‘done’ Product Increment. Waiting for the end of a sprint and a sprint review means waiting to ship a done project.” Or the Development Team is continuously delivering Increments during the Sprint. The statement is plain wrong.

Software Review 224

Software Review Underperforming Technical Team SCRUM Engineering 224

ProjectManager.com

NOVEMBER 22, 2021

The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. It became a part of agile when Ken Schwaber and Mike Beedle wrote the book “Agile Software Development with Scrum” in 2001. It does require strict scrum roles however.

Technical Review 505

Technical Review Prince2 Lean Manufacturing 505

Scrum.org

MARCH 22, 2021

The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

DECEMBER 25, 2018

Besides these rules, there are also certain guidelines which help the Scrum Teams to make the best possible use of Scrum framework to create maximum Business Impact. For ex: You cannot do Scrum without the 3 Roles - Product Owner, Development Team and Scrum Master. The impact of it would vary based on team context.

SCRUM 172

SCRUM Development Team Review Estimate Budget 172

Scrum.org

AUGUST 30, 2020

The Scrum events each have a time-box and a clear purpose to help us stay focused and make quick decisions while eliminating waste. But of course you can use the Scrum events well or poorly. This challenge can manifest at different levels, both within a team and at a leadership level outside a team.

Underperforming Technical Team 212

Underperforming Technical Team Development Team Review SCRUM Leadership 212

Scrum.org

JUNE 11, 2021

They have to be able to create the right ideas for value and be expert at communicating those ideas to the Development Team. You should have a good understanding of the Scrum Framework, its Roles, Events, Values, the Pillars and Artefacts. A Product Owner is an absolute professional at what they do.

Lean 234

Lean SCRUM Certification Development Team Review 234

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak Development Team meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

JULY 25, 2021

Indicators of a lack of clear accountability on a team might include: The Product Owner has not developed or communicated a Product Goal . The Development team or business stakeholders demand an ROI calculation for ordering the Product Backlog. The Scrum Master does not allow IT managers to attend any Scrum events.

SCRUM 244

SCRUM Development Team Review Agile Estimate 244

Scrum.org

OCTOBER 19, 2020

Daily Scrums are an important part of Scrum, but not all Daily Scrums need to be formal — a Development Team should not have a Daily Scrum for the sake of having it; it serves a different purpose than ticking off a box on a checklist. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum.

SCRUM 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211

Scrum.org

MARCH 18, 2020

Scrum Events . Sprint Planning, Daily Scrum, Sprint Review & Sprint Retrospective . All Scrum events, except for the Sprint, are formal opportunities for inspection and adaptation. Our poster shows these events as green inspect-and-adapt loops. The Sprint . at the point of work” [2]. Scrum Artifacts .

SCRUM 254

SCRUM 2020 2017 Development Team Review 254