2012 SCRUM Software Underperforming Technical Team 
Scrum.org
DECEMBER 7, 2023
The lecture triggered many thoughts about the relevance of teaching Agile/Scrum. The first paper was a 2012 study on the tensions with remote (off-shoring) teams (Ramesh et al Ambidexterity in Agile Development ISR2012). One might wonder how constructive that has been for learning true Scrum and Agile.
Scrum.org
DECEMBER 8, 2023
So why is so much of software opaque to the business? But, not all debt is bad!” I hear the phrase “but not all debt is bad” a lot, usually coupled with “some level of debt is manageable” and, as a software developer, it makes me cringe. All technical debt is a risk to the product and to your business.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Rebel’s Guide to PM
MAY 11, 2022
However, beyond the bad news we’ve had to deal with since the beginning of this year, these changing circumstances have ushered in a different kind of enthusiasm for making process improvements in how we work together as well. Does Agile project management for marketing really work? It’s certainly not a new idea.
Rebel’s Guide to PM
APRIL 16, 2020
However, beyond the bad news we’ve had to deal with since the beginning of this year, these changing circumstances have ushered in a different kind of enthusiasm for making process improvements in how we work together as well. Agility in marketing has been a growing trend since the publication of the Agile Marketing Manifesto in 2012.
Scrum.org
APRIL 7, 2022
Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime. The need for fluid teams.
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
DECEMBER 23, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why do software teams?—?despite But also a field that has much to say about code quality and how we can be better developers. 2012, Li & Shatnawi, 2007). Why is code quality so often an issue?
Expert insights. Personalized for you.
169 
Let's personalize your content