2013 Agile SCRUM Underperforming Technical Team 
Scrum.org
NOVEMBER 6, 2018
"There's no predictability/commitment in Agile/Scrum". Over the years I've heard my share of these kinds of statements from various levels of executives: "When my guys run a product development release I really want to know what I will get at the end so I can make business plans accordingly". "In Back to the roots.
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?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ProjectManager.com
JANUARY 20, 2020
It’s not a bad practice, but why save it for once a year? A software development conference with workshops on the theme of Our Digital Tomorrow. The conference serves developers, team leads, architects and project managers. Global Scrum Gathering. Agile & Beyond . GOTO Chicago. April 27-29, Chicago, IL.
Digite
MAY 15, 2018
This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.
Project Management Essentials
AUGUST 3, 2019
Experienced agile coaches and practitioners develop a sixth-sense. They can quickly assess the health of an agile project or team just as doctors do with their patients. In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. Outsourced Agile.
Scrum.org
AUGUST 25, 2022
How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.
Scrum.org
MARCH 31, 2020
Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.
Expert insights. Personalized for you.
131 
Let's personalize your content