Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. How much time should they spend with their team or with stakeholders? Which activities can be fulfilled by others in the team, and what is needed for that? Data from our Scrum Team Survey may shed a light on this.

2014 222

2014 2008 Technical Review 2019 222

Epicflow Blog

NOVEMBER 24, 2021

There is no doubt now that Agile is not just a buzzword, but a really working methodology that takes software development to the next level. . How does it differ from the traditional approach to product development? Are there any disadvantages of the Agile methodology? Overview of Traditional SDLC vs Agile Approach.

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Software Developers 98

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 202

Development Team Review Underperforming Technical Team SCRUM Technical Review 202

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. And unfortunately, too many teams treat roadmapping like just another project, leaving it behind to collect dust as they move on and start building software. Why you need a roadmap (even as an agile team). Agile product roadmap example.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

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

Leading Answers

NOVEMBER 8, 2020

When should we be using an agile approach for our project? The agile convert might claim “Always,” just as the predictive enthusiast could scream “Never!” Agile suitability tools are nothing new. We can learn techniques for running traditional, predictive projects and adaptive, agile ones.

Agile 78

Agile 2020 Development Team Review Software Review 78

Scrum.org

JANUARY 11, 2021

You can sign up here for the ‘Food for Agile Thought’ newsletter and join 29k other subscribers. The Sprint Review lost its detailed recipe on how to run the event. The Scrum Team] is a cohesive unit of professionals focused on one objective at a time, the Product Goal. Shall I notify you about articles like this one?

SCRUM 133

SCRUM 2020 Development Team Review 2017 133

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. Self organisation in agile teams. Development teams have the following characteristics: They are self-organising.

Technical Review 92

Technical Review Development Team Review Engineering 2017 92

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. . How to bring all of this together?

Underperforming Technical Team 160

Underperforming Technical Team Software Review SCRUM Technical Review 160

Scrum.org

MARCH 19, 2023

I wanted to determine whether ChatGPT 4 is superior to its predecessor, which left a good impression in recent months; see my previous articles on Scrum, Agile, and ChatGPT. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 45,000-plus other subscribers. ? ? ? ?? Read on and learn what happened.

ChatGPT 158

ChatGPT SCRUM Technical Review 2020 158

Scrum.org

FEBRUARY 10, 2022

Deshalb habe ich bereits 2017 eine erste Umfrage zum Net Promoter Score® des Scaled Agile Framework SAFe ® durchgeführt. Viereinhalb Jahre später habe ich diese Umfrage nun wiederholt: SAFe® hat zwischenzeitlich mehrere Iterationen durchlaufen und mehr agile Praktiker haben Erfahrungen mit diesem Framework gesammelt.

Lean 188

Lean Software Review 2022 Technical Review 188

Scrum.org

FEBRUARY 7, 2022

SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 34,000-plus subscribers. ?? The result back then was -52.

Lean 156

Lean Software Review 2022 Technical Review 156

International Institute for Learning

SEPTEMBER 20, 2022

Regarding the right size of a team, it has been experienced that a good number is around 10. 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.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52