Although Scrum is a well-known framework for agile software development, implementing Scrum alone won’t guarantee success. Software development in an agile setting calls for specialized technical abilities, effective process management, and collaborative skills that help teams produce high-quality solutions in short iterations.

One of my favorite sayings is “Inspection without adaptation is waste”. For continuous improvement it is important not only to identify things that did not go so well but to also change something in the way you are working. If you change nothing, the inspection did not have an impact at all and is a waste of time and energy.

Zum 10. Januar 2021 hat die scrum.org das bisherige Professional Scrum Developer Training (PSD) in Applying Professional Scrum for Software Development (APS-SD) umbenannt.

As of January 10, 2021, Scrum.org has renamed the former Professional Scrum Developer Training (PSD) to Applying Professional Scrum for Software Development (APS-SD). At the same time, the Professional Scrum Foundations (PSF) training has also been renamed to Applying Professional Scrum (APS).

The terms "iterative" and "incremental" are used so frequently and naturally in the context of agile that their meaning is no longer challenged.

A few years ago, I was part of a team that was starting to work together under very difficult circumstances: We had to finish a showcase in the Industry 4.0 area within just six weeks.

Vor kurzem haben die beiden Autoren des Artikels sich einmal mehr mit der Frage beschäftigt, wie sich erfolgreiche und weniger erfolgreiche Teams unterscheiden und was die Erfolgsfaktoren für erfolgreiche Teams sind.

Vor kurzem habe ich mit einem Team die interessante Frage aufgeworfen, ob Softwareentwickler Leidenschaft für das Produkt das sie entwickeln benötigen oder ob Leidenschaft für Technologie wichtiger ist.

Wenn man Scrum auf einen einzigen Begriff reduzieren müsste, welcher wäre das?