Scrum.org

MARCH 13, 2020

Product Backlog Refinement is all about a shared understanding between Product Owner and the Development team. During the Sprint the Dev Team has full focus on the Sprint Goal. In Sprint Planning the Dev Team just sits blank at first. We do too little refinement as a team. Who has to be there?

Development Team Review 186

Development Team Review Innovation Planning Process 186

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 127

Development Team Review 2017 SCRUM Estimate 127

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 197

Development Team Review Underperforming Technical Team SCRUM Closing 197

ProjectManager.com

JANUARY 13, 2020

For this post, we’re going to take a deep dive into one of the events in the scrum framework, sprint planning. In order to provide some regularity and minimize the need for meetings, scrum is broken down into events. One of these events is the sprint. A sprint is an iteration in the development cycle of a project.

Planning 247

Planning Development Team Review Software Review SCRUM 247

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 188

SCRUM Software Review Development Team Review Technical Review 188

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 146

Technical Review Development Team Review SCRUM Consulting 146

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 136

Development Team Review SCRUM Closing Planning 136

The IIL Blog

OCTOBER 17, 2023

Agile team A cross-functional group of individuals (e.g., Product Owner, Scrum Master, Development team members) who work collaboratively to deliver value in an Agile project. Backlog A list of tasks, features, or requirements to be addressed by an agile project manager or team and is often associated with Agile methodologies.

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

LiquidPlanner

SEPTEMBER 6, 2018

In certain cases, it’s possible to cling to legacy or home-rolled project management practices even when development teams have moved into some form of Agile development. Attend Agile events in your local area for networking and learning purposes (extra points if you bring your direct manager along).

Agile 755

Agile Executing Development Team Review Technical Review 755

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 180

SCRUM Development Team Review Underperforming Technical Team Technical Review 180

Digite

MAY 15, 2018

In case you haven’t read Yuval’s post, basically, it presents a map of values and practices in Scrum to Kanban language, and encourages Kanban teams to approach Scrum from a practices point of view. This is probably the set of things that, regardless of the name, Scrum and Kanban teams will have the most in common.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

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 180

SCRUM Development Team Review Leadership Agile 180

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 201

SCRUM Underperforming Technical Team Development Team Review 2020 201

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 158

Development Team Review Underperforming Technical Team Software Review Technical Review 158

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 305

Agile Software Review Technical Review Development Team Review 305

Scrum.org

MARCH 20, 2024

The boundaries come from the Scrum Framework (Events, Roles Artifacts) and the organization. how many Scrum teams do we need, who should be on each Scrum team) Artifacts: Where should the artifacts be stored in alignment with organizational policies? The Role of the Leader Leaders are essential to the success of any Scrum team.

SCRUM 161

SCRUM 2020 2024 Development Team Review 161

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 108

Software Review Development Team Review SCRUM Closing 108

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 186

Underperforming Technical Team SCRUM Software Review Development Team Review 186

Scrum.org

FEBRUARY 21, 2023

Additionally, I have a strong background in product discovery, which involves identifying customer needs, validating product ideas, and conducting experiments to inform product development decisions. Comment : I doubt that ChatGPT know the 2020 Scrum Guide as it still refers to the Development Team and ignores the Product Goal.

ChatGPT 152

ChatGPT Development Team Review Technical Review SCRUM 152

Scrum.org

SEPTEMBER 19, 2020

Scrum Events. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. Show, don’t tell. Daily Scrums.

Technical Review 188

Technical Review Software Review Development Team Review Cadence 188

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 213

SCRUM Development Team Review Underperforming Technical Team Technical Review 213

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 239

2020 Technical Review Development Team Review SCRUM 239

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 191

Software Review Agile Underperforming Technical Team Development Team Review 191

Leading Answers

JUNE 22, 2022

Authentic leadership is practiced on mundane things, yet when more significant events occur, the skills and trust of others can be used to overcome significant hurdles. We must also be able to make the team feel capable and develop team members to their fullest potential. Why pay twice for the same opinions?”.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Scrum.org

FEBRUARY 25, 2024

Lack of Stakeholder Engagement : Failure to involve key stakeholders in Scrum events, leading to misaligned expectations​​. Resource Constraints : Not providing Scrum Teams with necessary resources, tools, or training, impeding their ability to deliver value effectively​​.

SCRUM 178

SCRUM ChatGPT Technical Review Development Team Review 178

Leading Answers

NOVEMBER 1, 2020

Since knowledge work is often novel or unprecedented in the organization, it helps to have visual cues for it so people can point to it or examine its position on a Kanban board to determine its status in the development process. This meeting is another scheduled event focused on information sharing.

Agile 135

Agile Planning Underperforming Technical Team Development Team Review 135

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 203

SCRUM Development Team Review Underperforming Technical Team 2011 203

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

AUGUST 29, 2022

Rather, the manager’s role — among other things — is to set the guardrails within which teams can self-manage. The self-management parameters will depend on the organization and the team’s maturity, which is the responsibility of the manager to assess. Processes that used to happen sequentially may be completed simultaneously.

Leadership 198

Leadership Agile SCRUM Development Team Review 198

Scrum.org

NOVEMBER 18, 2020

Foremost, the new Scrum Guide is less prescriptive, eliminating many suggestions such as the Daily Scrum questions, at least one mandatory action item from the Retrospective becoming a part of the Sprint Backlog or the advice on why Sprint cancelations are rare events. The Sprint Review lost its detailed recipe on how to run the event.

2020 182

2020 SCRUM Development Team Review Software Review 182

nTask

AUGUST 22, 2019

They also need to be cross-functional, with all proficiencies required to achieve the project without dependency on team members. The Scrum team is divided as follows: Product Owner. Development Team, and. Help optimize the work value for the Development Team, and. Sprint Review, and. a Scrum Master.

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

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 172

SCRUM Development Team Review Technical Review Consulting 172

Scrum.org

MAY 4, 2020

We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. Do you want to get this article in your inbox?

SCRUM 167

SCRUM Agile Technical Review Development Team Review 167

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 203

SCRUM Software Review Lean Leadership 203

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 225

SCRUM Underperforming Technical Team Development Team Review Technical Review 225

Scrum.org

DECEMBER 7, 2022

Consider a cadence that involves Planning, Reviewing, and Retrospecting with a clear distinction between the team working on the OKR and its stakeholders. . After identifying the few real OKRs, assess who’s needed to work towards each of them. The Scrum framework provides one example of how such a cadence could look.

Cadence 184

Cadence Development Team Review Initiating SCRUM 184

Agilemania

FEBRUARY 16, 2022

Scrum encourages teams to improve by reflecting on their success and losses. . Software development teams use scrum to deliver working software to the customers. We will introduce you to scrum and its artifacts, events, and most importantly, its benefits. Helps the team members in becoming self-managed by coaching them.

SCRUM 98

SCRUM Development Team Review Underperforming Technical Team Software Review 98