Scrum.org

JUNE 24, 2022

When people first look at the Scrum framework, they often see the roles and the events first. They see only the structure of Scrum; who wears the hats and when. But Scrum and the Agile methodologies it builds on are so much more. Scrum is a great example of a motivation framework. And that makes sense.

SCRUM 209

SCRUM 2002 2006 2007 209

Scrum.org

SEPTEMBER 10, 2021

La conversación iba encaminada en si valia la pena convertirse en Scrum Master. La conversación se fue consolidando y me hizo una pregunta que si valía la pena emplear un Scrum Master. La pregunta era, ¿cómo creamos la hoja de ruta de la carrera de un Scrum Master? Realmente vale la pena convertirse en Scrum Master?

SCRUM 199

SCRUM 2011 2021 Agile 199

Scrum.org

JANUARY 15, 2022

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. Let’s take the example of Scrum, one of the widely used Frameworks, and see how one can handle fixed-bid projects. If you consider approaching your contracts using Scrum, You can leverage Sprint. Fixed Budget .

Agile 252

Agile 2001 2011 Software Developers 252

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. You can observe implicit coordination in Scrum teams when you look at how work moves across a Scrum board, or on- and of the Sprint Backlog. This is also why the Scrum framework includes the Definition of Done.

2004 251

2004 2010 2016 2011 251

ProjectManager.com

AUGUST 29, 2023

B – Project Management Terms Backlog Backlog is a term from the Agile methodology Scrum, but is also used across industries to track every single thing that is needed to complete a product in development. Learn how Kanban and Scrum differ in the blog Kanban vs Scrum: Which is Better?

Software Review 418

Software Review Underperforming Technical Team Lean Event Chain 418

Gunther Verheyen

AUGUST 30, 2020

I regularly get inquiries from people reaching out for instructions, assistance, or other forms of guidance to learn about Scrum, pass exams, become a trainer, or advance their career towards “Agile coach” Surprise. 2) I have always been and am still all about Scrum. I am no wizard. And I spent 7 years (seven!)

SCRUM 118

SCRUM 2003 Agile 2010 118

Scrum.org

AUGUST 13, 2019

The first part contains my personal journey in becoming a Scrum Master, the second part includes recommendations for new Scrum Masters. Part 1 — Becoming a Scrum Master. Nine years ago I changed my title from Project Manager into Scrum Master. Do you have any recommendations for my Scrum Master journey?”.

SCRUM 157

SCRUM Certification Telecoms Agile 157

Gunther Verheyen

JANUARY 27, 2021

In October 2003 my life of Scrum started, albeit not with Scrum. My life of Scrum actually started with eXtreme Programming which we then wrapped in Scrum. Fast forward >> In December 2010 I traveled to Zurich (Switzerland) to attend a PSM class (“Professional Scrum Master”) by Ken Schwaber.

SCRUM 110

SCRUM 2012 2010 2011 110

Gunther Verheyen

MAY 20, 2020

Maybe along the road they took a break, read more, gained more experience with Scrum, and demonstrated other forms of patience, persistence, and belief. On a personal note, I want to share that my journey of Scrum started in 2003. It was only by accident in 2010-2011 that I became what I didn’t know I wanted to be.

SCRUM 111

SCRUM 2003 2010 2011 111

Scrum.org

JUNE 17, 2019

Scrum cumplió 21 años en 2016. Desde 2011 ha habido dos grandes cambios en la guía de Scrum , en 2013 y 2016. Se reforzó el énfasis en el Daily Scrum como elemento de planificación -y no solamente sincronización- y también se cambió el nombre de la reunión de grooming a refinenement. Con muchos cambios.

SCRUM 26

SCRUM 2011 2016 2013 26

Scrum.org

OCTOBER 9, 2023

They looked up the date: July 21, 2011. For example: grassroots “requirements refinement” and “Scrum of Scrums” meetings were initiated by the teams. Learn more from David in his upcoming Professional Scrum classes or hire him for private Scrum & Agile training. This article is also published at scrum.works.

Transportation 214

Transportation 2011 SCRUM 2020 214

Scrum.org

APRIL 25, 2022

Die geringe Integration von UX-Praktiken in die Arbeitsweise von Scrum Teams ist für mich ein Anzeichen dafür, dass noch viele Scrum Teams einen niedrigen UX-Reifegrad besitzen. Bei diesen Scrum Teams konnte ich beobachten, dass dort UX eine Fähigkeit ist, die alle Mitglieder im Team beherrschen. . Level 0: Scrum ohne UX.

SCRUM 40

SCRUM Lean 2011 2022 40

Scrum.org

OCTOBER 9, 2023

Por qué Scrum no tiene un evento de planificación de la Meta de Producto ? ¿Qué En las versiones de 2010 y 2011 se referenciaba este evento, pero no se consideraba estándard. Y en la versión de 2013 se afirmaba que Scrum no prescribe ningún evento de planificación superior al Sprint. ¿Que encontrarás en este artículo?​

SCRUM 184

SCRUM 2010 2011 2013 184

Scrum.org

FEBRUARY 10, 2021

Agile Manifesto Poster Scrum just turned 25 with a big celebration last November. Jeff Sutherland (2011) This week marks another big milestone in the agile community, the 20th Anniversary of the Agile Manifesto. The weekend at the snowbird in Utah Feb 11-13, 2001 was exactly 20 years ago. Ron Jeffries (2018). Ward Cunningham (2013).

Agile 209

Agile 2001 2011 2012 209

Gunther Verheyen

DECEMBER 17, 2020

Scrum has been around for a while, they say. The Scrum Guide holds the definition of Scrum, they say. The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? What else happened along the road to the way that Scrum is defined and represented?

2010 144

2010 SCRUM 2004 2002 144

Scrum.org

JANUARY 6, 2022

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. Scrum, agile thinking, modern software development working practices are synonymous with Digital Technology and have evolved out of the fundamentally different characteristics of the opportunity presented by technology.

Underperforming Technical Team 252

Underperforming Technical Team Innovation 2001 2011 252

Scrum.org

DECEMBER 12, 2021

Inzwischen weiß jedes Scrum Team, dass es mit seinen Nutzern sprechen, Ideen frühzeitig testen, Feedback einholen und ihr Produkt oder ihre Dienstleistung kontinuierlich an die aktuelle Problemstellung der Nutzer anpassen muss. Business-Problem-Statement: Scrum Teams sollten konkrete Problemstellungen von Nutzern lösen.

SCRUM 203

SCRUM 2011 203

Scrum.org

OCTOBER 19, 2022

And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.

Agile 225

Agile 2010 2013 2008 225

Scrum.org

DECEMBER 31, 2023

Seit er 2011 die Leitung von Apple übernommen hat, ist der Wert von Apple um 90 % gestiegen. Nach 15 Jahren der Planung begann der Bau 2006 und sollte 2011 fertiggestellt werden. Und es ist unfassbar, was wir mit ihnen erschaffen können, ob es darum geht, Produkte zu erstellen oder Marketing zu betreiben.

2011 194

2011 2006 2020 SCRUM 194

Scrum.org

FEBRUARY 4, 2022

What contexts are Scrum suited to, and which not? What if you end up applying a methodology like Scrum to a context where it isn’t suited, and people leave the company as a result? when everyone is pro-Scrum, or against SAFe or against estimation, or exclusively Scrum Masters? Is scaling always a bad idea?

Agile 218

Agile Underperforming Technical Team Software Review Technical Review 218

Gunther Verheyen

FEBRUARY 26, 2024

I embarked on my Agile journey in 2003 when we wrapped eXtreme Programming in Scrum. Besides having engaged with many teams and organizations I have also created and facilitated many Scrum workshops and classes about various topics for various audiences since then. Warm regards Gunther independent Scrum Caretaker What?

SCRUM 86

SCRUM Certification 2016 2011 86

Scrum.org

FEBRUARY 27, 2022

Es war Weihnachten 2011. Weiter Artikel zu Scrum findest du hier. Zu meinen nächsten Scrum Trainings geht es hier. Wie in jedem Jahr verbrachten die Menschen die Feiertage im Kreis ihrer Familie und ihrer Liebsten und hielten diese Momente auf Fotos fest. Möchtest du mehr erfahren?

2011 207

2011 2015 Innovation SCRUM 207

Scrum.org

JUNE 29, 2019

I now understand more deeply why there is so much sub-optimal Scrum/Kanban out there, and why there is scope for all sorts of agility from crap to phenomenal, and why it is not always helpful to diss "inferior" approaches. The conversations strongly influenced what the reader will see in the coming posts in this blog series. Good to Great.

Leadership 151

Leadership 2019 2011 2018 151

Gunther Verheyen

OCTOBER 25, 2020

After a few years of searching and experimenting, “Scrum” was documented and presented to the general public. Scrum turns 25. I record a few highlights of “My life of Scrum”, a few aspects from the past 17 years of the life of an independent Scrum Caretaker. Later, we add Scrum to our approach.

SCRUM 105

SCRUM 2004 2003 2011 105

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 230

2015 2014 2004 Influencer 230

Scrum.org

APRIL 8, 2021

The Sprint Goal should be discussed each day at the Daily Scrum, it is ambitious but realistic as well as specific and transparent. . Pink, 2011, Drive: The Surprising Truth About What Motivates Us, Riverhead Books). F requently Discussed, A mbitious, S pecific, T ransparent. Table 2 Goal instances comparison.

2007 230

2007 2011 Risk Management 2020 230

Scrum.org

AUGUST 28, 2020

like choosing for Scrum?—?they These norms range from very basic ones, like attending a Daily Scrum every day, to abstract ones like “work together towards a shared goal instead of working on your own tasks” and “delivery small, working bits of product frequently instead of huge chunks occasionally”. Why Is Change Hard?

2012 184

2012 2006 2011 Influencer 184

Digite

MARCH 12, 2018

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. In the usual Scrum process, the P.O. So I will likely implement Kanban (in Jira). What are your best practices here? • One column per person/pair?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. This post is my attempt to do this. The need for fluid teams.

Underperforming Technical Team 202

Underperforming Technical Team 2007 2006 2009 202

Scrum.org

APRIL 16, 2019

The comparison between Kanban and Scrum obviously comes up often when we're talking to teams, especially in the context of Professional Scrum with Kanban. Scrum is quite clear about the topic (Quoting the Scrum Guide ). Scrum Teams are self-organizing and cross-functional. To Team or not to Team? Mixing it up.

2011 161

2011 Initiating SCRUM Software Review 161

Scrum.org

FEBRUARY 22, 2021

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide.

Software Review 194

Software Review Cadence Technical Review SCRUM 194

The IIL Blog

JULY 26, 2023

Over 150,000 exams have been taken globally since 2011 with numbers increasing rapidly year-on-year, and candidates representing a broad range of organizations and industries. IIL’s Agile and Scrum Online Conference is available to stream now through September 4 th ! IIL is an APMG Accredited Training Organization (ATO). Register here.

2010 148

2010 2011 Certification Prince2 148

The IIL Blog

JUNE 28, 2018

The future will be flexible project management models such as those used in Agile and Scrum projects. We have learned from Agile and Scrum that flexible project management approaches are necessary for many projects. This holds true even for those projects that do not require innovation. Geraldi, J. Maylor, H. & & Williams, T.

Innovation 106

Innovation 2008 2010 2011 106

Scrum.org

DECEMBER 23, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. 2011, Politowski, 2020). Code metrics for a part of the code for the Scrum Team Survey as generated by Visual Studio 2019. This post is part of our “in-depth” series. Why is code quality so often an issue? Why do software teams?

Software Review 226

Software Review Technical Review Underperforming Technical Team 2015 226

Gunther Verheyen

MAY 19, 2022

Mijn boek Scrum Wegwijzer ( Een kompas voor de bewuste reiziger ) is de Nederlandse vertaling van mijn Engelstalige “smart travel companion” getiteld Scrum – A Pocket Guide. Scrum Wegwijzer 2e druk nu beschikbaar! Dat werd het Engelstalige Scrum – A Pocket Guide (A Smart Travel Companion). Gelukkig maar.

SCRUM 95

SCRUM 2013 2010 2003 95

Agilemania

DECEMBER 8, 2021

The year 2011 saw the Arab Springs and that sent shock waves throughout the world. SAFe Scrum Master (SSM). SAFe Advanced Scrum Master (SASM). Largest Agile & Scrum Community Run by Agile 30 Group. Agile 30 is a Scrum Alliance user group managed by Agilemania. Why Scaled Agile Framework? Leading SAFe 5.1.

Agile 98

Agile Lean 2011 Consulting 98

Agilemania

APRIL 20, 2021

Scaled Agile Framework (SAFe): SAFe was created by Dean Leffingwell and has been in existence since 2011. Large-Scale Scrum (LeSS): Craig Larman and Bas Vodde created the LeSS framework. It developed by taking Scrum and trying many different experiments to discover what works. depending upon the domain of the Scrum teams.

Agile 93

Agile Telecoms 2011 2013 93