Scrum.org

NOVEMBER 24, 2021

Which activities can be fulfilled by others in the team, and what is needed for that? One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). Maarten, who is an experienced Product Owner, added that he spends a lot of time on this with his teams.

2014 222

2014 2008 Technical Review 2019 222

Scrum.org

NOVEMBER 25, 2019

Source : Scrum Guide 2017. No matter the frequency of your retrospectives you should always watch out for the following Sprint Retrospective anti-patterns from the Scrum Team, the Development Team, the Scrum Master, as well as the organization: Sprint Retrospective Anti-Patterns of the Scrum Team.

Underperforming Technical Team 210

Underperforming Technical Team SCRUM Development Team Review Agile 210

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Source : Scrum Guide 2017. To a certain extent, it is also a negotiation between the Product Owner and the Development Team. A serious goal answers the “What are we fighting for?”

Development Team Review 200

Development Team Review Underperforming Technical Team SCRUM Technical Review 200

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. Review and align your roadmap with other internal teams. Presenting your roadmap to get support. This connection helps align teams on a central goal and shows how a product might change and grow over time. An execution phase.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Epicflow Blog

NOVEMBER 24, 2021

Each of them has certain peculiarities, so development teams can choose the one that works best for them. . One more distinctive feature of Agile methodology is its focus on collaboration and self-organizing cross-functional teams. The table below presents their distinctions in more detail. . Flexibility. .

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Software Developers 98

Gunther Verheyen

FEBRUARY 27, 2024

Having no other plans for that time being, I could completely focus on my work as curator: contacting people, collecting ideas for essays, reviewing potential essays, suggesting potential edits, ordering and categorizing them, reviewing the manuscript and the cover. 1986, [link]. (2) 14, 2001: pp. 20, 2004: pp.

SCRUM 71

SCRUM 2004 Software Review 2019 71

Scrum.org

JANUARY 11, 2021

The Sprint Review lost its detailed recipe on how to run the event. Interestingly, the authors also axed other elements of the 2017 edition of the Scrum Guide that I thought less contested, for example, the magnitude of work allocated to Product Backlog refinement and servant-leadership. By the way, it’s free. The Scrum Guide 2020.

SCRUM 131

SCRUM 2020 Development Team Review 2017 131

Leading Answers

NOVEMBER 8, 2020

If the backstage catering table did not contain a bowl of M&Ms, or if it did and there were brown ones present, likely other items in the contract could have also have been missed. If the promotor had missed the M&Ms requirement, likely the whole setup needed to be thoroughly reviewed before testing.

Agile 78

Agile 2020 Development Team Review Software Review 78

Scrum.org

JULY 10, 2018

While working diligently behind feature flags, using elements of Scrum, it wasn’t clear to the stakeholders the value being delivered and how well the teams were progressing towards their end goal. Development teams are structured and empowered by the organisation to organise and manage their own work. Bibliography.

Technical Review 93

Technical Review Development Team Review Engineering 2017 93

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

JUNE 28, 2021

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. In this first presentation, I will be giving an overview of requirements management. So, let’s begin the presentation. Hello, my name is Walter Stinnett.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52

Scrum.org

FEBRUARY 8, 2020

THIS IS A REPOST ARTICLE DETAILING THE KEYNOTE I CO-PRESENTED AT THE LESS CONFERENCE IN 2019. Our Business Lending product is being developed by more than 20 teams spread across 3 sites. Each team contains business, IT and operations skills. This was in late 2017. . Output driven development.

Underperforming Technical Team 159

Underperforming Technical Team Software Review SCRUM Technical Review 159

Scrum.org

MARCH 19, 2023

models: The first experiment compares the Scrum Guide 2017 to the Scrum Guide 2020 The second experiment is designing a Retrospective exercise The third experiment is to help a new Scrum team to design a Definition of Done. Tell me: what is the difference between the Scrum Guide 2017 and the Scrum Guide 2020?

ChatGPT 159

ChatGPT SCRUM Technical Review 2020 159

Scrum.org

FEBRUARY 10, 2022

Deshalb habe ich bereits 2017 eine erste Umfrage zum Net Promoter Score® des Scaled Agile Framework SAFe ® durchgeführt. I have only had one customer that was more or less successful in implementing SAFe, but it was already practicing Scrum for more than five years in their separate development teams.

Lean 187

Lean Software Review 2022 Technical Review 187

Scrum.org

FEBRUARY 7, 2022

Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. I have only had one customer that was more or less successful in implementing SAFe, but it was already practicing Scrum for more than five years in their separate development teams. how to run a proper review).

Lean 156

Lean Software Review 2022 Technical Review 156

International Institute for Learning

SEPTEMBER 20, 2022

For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams. If it takes more than two pizzas to feed (with a slice) the team, the team is likely too big.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52