Remove 2013 Remove Agile Remove Process Remove Underperforming Technical Team
article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. The bad news, it’s hard to master. Scrum is part of agile software development and teams practicing agile.

SCRUM 335
article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Risk-aware Product Development (a.k.a. Scrum)

Scrum.org

"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.

article thumbnail

Top Project Management Conferences of 2020

ProjectManager.com

It’s not a bad practice, but why save it for once a year? This project management conference covers topics such as the project management framework and its terminology, process groups and the nine knowledge areas of the PMBOK. A software development conference with workshops on the theme of Our Digital Tomorrow. GOTO Chicago.

2020 260
article thumbnail

Is Your Agile Project Healthy?

Project Management Essentials

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. What are the team dynamics?

article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

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.

article thumbnail

On Technical Debt And Code Smells: Surprising insights from scientific studies

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why do software teams?—?despite So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”.